r/javascript • u/wprzecho • Feb 01 '19
Google Play Store now open for Progressive Web Apps 😱
https://medium.com/@firt/google-play-store-now-open-for-progressive-web-apps-ec6f3c6ff3cc36
u/Ajedi32 Feb 01 '19
For now this seems like a bit of a hack, as you're essentially just manually replicating what Chrome does when it generates APKs on the fly from PWAs. I'd love to see this get native support from the Play Store, so you can (for example) just paste a URL to publish a PWA instantly.
8
u/fgutz Feb 01 '19
essentially just manually replicating what Chrome does when it generates APKs on the fly from PWAs
Is that was Chrome for Android does when you "Add to home screen"?
6
u/Ajedi32 Feb 01 '19
Yes, that's what I'm referencing.
9
u/Blieque Feb 01 '19
Are you sure it bundles up an APK? I was under the impression it just added a shortcut to Chrome in the app menu, and registered a pseudo-app in the system to separate statistics from regular Chrome processes.
4
u/AwesomeInPerson Feb 01 '19
Yup, and that "pseudo-app" is a valid, bundled apk. Built & signed server-side by the Play Store, not by Chrome, though (afaik).
5
u/Blieque Feb 01 '19
Right, with the new system. The original comment implied the standard "Add to home screen" feature generates an APK. That's what I questioned. Even if the PWA is installed as it's own app separate from Chrome, that doesn't guarantee that an APK is created.
1
u/AwesomeInPerson Feb 02 '19
Right, with the new system. The original comment implied the standard "Add to home screen" feature generates an APK. That's what I questioned.
New system? It's like that for more than a year now.
Tapping the "Add to Homescreen" banner will create & fetch a bundled apk from Google's servers. (called webAPK)Even if the PWA is installed as it's own app separate from Chrome, that doesn't guarantee that an APK is created.
Only if the PWA misses some criteria (no icon, not cached for offline use, etc..) or you're not using Chrome but some other browser (like Edge, Samsung Internet) you will get a normal shortcut on your homescreen, otherwise: APK it is.
3
u/Ajedi32 Feb 01 '19
What's the difference? The "pseudo-app" is a 100% real application as far as Android is concerned. (Provided the site you're adding to your home screen is an actual PWA and not just a website.)
2
u/Blieque Feb 02 '19
The difference is that there's no APK involved, as far as I know.
1
u/Ajedi32 Feb 02 '19
Hmm.... can you install an app without an APK being involved? I know there are apps out there that will extract APKs from installed applications, what happens if you use one of those on an installed PWA?
7
Feb 01 '19
What they are doing is making pwas discoverable via the primary place people look for apps on Android
3
u/fgutz Feb 01 '19
cool. I did not know that. Was wondering how PWAs worked exactly but that makes sense now
68
Feb 01 '19
JavaScript really is taking over.
44
u/morficus Feb 01 '19
It's web technologies they are taking over.
23
u/13steinj Feb 01 '19
Which in the case of PWAs, is mostly JS.
18
u/The_real_bandito Feb 01 '19
Well until Web Assembly comes along and everything changes yet again. I hope that happens even though I strictly code in JS nowadays (Node and Browser)
There are good developers in every language and it just give the web platform more good apps in the end.
9
u/bogas04 Feb 01 '19
It'll be an overkill to write layouts/UI in web assembly. I think it'll be best used by libraries where the overhead of communication is worth the perf benefit, which probably means games, video/image editors and professional apps like that. I expect one to still use basic HTML CSS and JS for content driven websites.
8
u/nomadProgrammer Feb 01 '19
You are right. That's exactly what web assembly was created for. Yet many people think it is for using c++ for what js can perfectly handle.
4
Feb 01 '19
There is an inherent benefit to that, though, which is that it would allow us to break free of JavaScript's inability to make breaking changes to the language. For as much as it gets better, there are still some hideous design decisions that are incurable.
0
Feb 02 '19
[deleted]
2
u/bogas04 Feb 02 '19
Yup I get that but honestly the DOM interactions would always have a huge overhead to not justify compiling to WASM over JS. Look at how good elm works these days and it compiles to JS. And for type safety there are numerous languages available to use (ReasonML, TS, Flow, PureScript to name a few).
PS: I'm speaking about general UI/layouts.
2
u/steeeeeef Feb 01 '19
You can not write a web app without javascript. DOM manipulation will always be a js thing.
4
-1
5
5
-10
u/drabred Feb 01 '19
Oh god no
5
u/bastionShaw Feb 01 '19
Lets hope that WebAssembly takes over or JS is gonna eat the Web Application ecosystem
5
2
u/hutxhy Feb 01 '19
JS is growing rapidly despite popular alternatives like Python. So I don't see WASM changing that trend.
-23
u/YodaLoL Feb 01 '19
For the worse
15
u/seiyria Feb 01 '19
he said, in /r/javascript
2
u/YodaLoL Feb 01 '19
I do full-stack and love JS (TS is even better). The web stack of today is however just not compatible with native. Google are just pushing the PWA narrative so hard because web is their strong point. It does solve a lot of problems, but it's just not native. Quality will suffer greatly.
11
u/seiyria Feb 01 '19
It doesn't matter if it's native. Apps are here for users. That's the point. Native, web, it really doesn't matter. You go with what gets your app done, that your users need/want/like, and you go from there. It just so happens to be easier to make a PWA than a full-blown native app for every platform, so we'll keep investing in the web for that purpose.
3
u/hutxhy Feb 01 '19
The bridge between native and non-native mobile app performance is thinning. React Native keeps getting performance boosts, so does flutter, I don't see why PWAs can't do the same.
2
u/YodaLoL Feb 01 '19
Because web is completely disconnected from native primitives, where as React Native actually has true native bindings. React Native has absolutely nothing to do with web, it just shares the same lifecycle API as React.js. JSX plays a big part too.
1
u/hutxhy Feb 01 '19
Doesn't Chrome's mobile app use the device's internal version of the V8 engine? If so, couldn't they have a mobile V8 version that exposes some web API's to the native layer that could help bridge that gap? I'm probably WAY over simplifying it, but I know our browsers sort of do something similar with our OS.
1
u/ArmoredPancake Feb 01 '19
React native uses platform primitives through bridge, Flutter draws it's own widgets like game engine does, web is bound to it's shitty language and runtime embedded into browser.
22
u/jacquesdancona Feb 01 '19 edited Feb 01 '19
I'm not sure what I should think about Play store PWA's. On one hand, I'm working on a little personal project and I could (relatively easily) publish it in the store, that's cool. But some other guy can do that too, so there will probably be an influx of a lot of fluff apps.
With native apps there's always this barrier of having to invest time or money in making a 'native' app, (although react-native has lowered this barrier a lot).
Edit. My last point doesn't really hold up. We've had Cordova for years.
4
u/spacejack2114 Feb 01 '19
There are about a million new apps added to the store every year. I'm not sure how different it would be if there were 10 million.
3
Feb 01 '19
So....you think you need a barrier to entry that’s marginally better than what you get with PWAs?
0
u/jacquesdancona Feb 01 '19
I get your point. I'm just not sure if pwa apps are a good idea or not and I'm having a hate/love relationship with apple and how strict they are with app admissions. I like the (psychological) barrier of not doing something like online banking on a pwa.
2
Feb 01 '19
Why would a PWA be different from a web page except you can tie into biometric resources on the device.
1
Feb 01 '19
They are a good idea. It broadens the access to applications and standardizes deployment processes. It’s closer to write once run anywhere as is probably possible, where the more end point resources you need to tie into the less platform agnostic you can be in your front end development.
0
Feb 01 '19
[deleted]
12
u/DRdefective Feb 01 '19
Cordova wasn’t as good imo.
4
u/meeeeoooowy Feb 01 '19
It wasn't, but you could EASILY make a web app and push it though the store via Cordova.
1
1
24
u/astral_dragon12 Feb 01 '19
They want to take 30% cut from PWA too???
6
5
u/HomemadeBananas Feb 01 '19
Google and Apple taking 30% seemed ridiculous to me too. Now I’ve dealt with a payment gateway and merchant account, and when you see the fees from the merchant account, transaction fees from the gateway, and refunds from chargebacks and chargeback fees, it’s not so unreasonable. They aren’t making as much as you might think after considering all of that.
1
u/astral_dragon12 Feb 02 '19
I agree that Im pretty sure there are a lot of other fee that I'm not aware of. But 30% seems a little high IMO. When you have other companies like Steam taking 20% I believe and Epic taking even less. And I believe Amazon app store is 10%? Not too sure tho, but the 30% from Apple and Google and seems like because they Monopoly the platforms to me.
0
u/NobleFraud Feb 02 '19
Stream is taking 30 and epic is taking 20
0
u/astral_dragon12 Feb 02 '19
Just looked it up. Stream is 25% and Epic is 12%
2
u/NobleFraud Feb 02 '19
steam takes 30%, then it scales down to 20% as more copies of the game is sold, while yes I was wrong about epic, epic takes 12%
2
u/astral_dragon12 Feb 02 '19
You were right, I misread the article. Steam do take 30%.
But IMO I still think Google 30% is a little high especially when Google is known to not review the app throughly as Apple.
1
u/NobleFraud Feb 02 '19
yeah I agree, google is taking waay too much considering, most of the payment gateway services charge around 3-10%
2
u/moebaca Feb 01 '19
How could they take a cut in my app if it's a subscription based web app and not something you pay for up front? I feel like loads of PWAs would also have this model.
11
1
u/DerNalia Feb 02 '19
You can't charge for PWAs, cause they are all websites
0
u/astral_dragon12 Feb 02 '19
In fact you can. If course you can't enforce it if you want PWA to work as websites since users can just access it through browser. But thats not what PWA is about isn't it? PWA aim to bridge the gap between native app and web. So the developers need to submit their app through the Play Store to get access to the native functionalities and guess who run the play store. Even when subscription based app can get away with it by having user pay in web browser a lot of apps like games cant do that. That's where they can charge their 30%
7
u/bopll Feb 01 '19
Anyone wanna ELI'm a junior dev?
4
u/xXD00MXx Feb 02 '19
OK I'm no expert but I definitely like the idea of PWAs.
So when apps were first released on the Google play store or iOS store, they needed to be programmed natively ( which means they needed to be built in a specific programming language - Java for Android and Objective C for iOS).
However as JavaScript and other web technology got more powerful, people saw they could mimic a lot of that functionality with a simple website. So instead of making a whole app, they build a "wrapper" that could just run the website. A wrapper has the sole purpose of sole running that website (ex Phonegap)
This made development a lot easier cause instead of having many developers working on 2 different platforms u could have the same ones only developing for web and just putting it in the wrapper.
PWAs are the step further. Instead of adding additional software to run the website now your browser can act as your wrapper. And now more and more mobile browsers support PWAs and allow for an add to home button which allows it be stored on your home screen and make it look like a native app.
This provides benefits like smaller app size, automatic updates, and offline support. However in order to use or download the PWA u have to visit the site, so centralization has become a problem.
With Google play store, we now supporting PWAs we solve that problem.
Granted it probably opens up a whole new can of worms but it's definitely gonna me interesting to see how it pans out.
Ik this isn't 100% ELI5 but I hope I did help you understand a bit. Feel free to make any corrections
TDLR: Developers used websites to make making apps easier, then browsers helped them out by removing the app aspect of it and now Google play can properly distribute them.
2
3
u/amateur_programmerOz Feb 02 '19
I wouldn't mind an eli5 either
3
u/xXD00MXx Feb 02 '19
I think I explained the situation, check my comment to the earlier commentor.
2
4
u/moebaca Feb 01 '19
This articles section on Monetization with the Play Store didn't really explain how Google intends to take their cut from a subscription based web app.. if I don't charge an upfront download cost and handle subs through my own mechanisms like stripe, how would Google attempt to get their cut? Is the $25 publishing fee enough for them to be satisfied?
2
u/seanwilson www.checkbot.io Feb 01 '19
If your app is not free to download, there will be no easy way to validate that the user has actually paid for it (at the end, your content is just a URL)
There's no workaround for this? Maybe I'm not understanding the features available but surely if you can talk to the native app you could ask it if the app has been paid for?
3
u/Kenya-West Feb 01 '19
Well, Microsoft Store has done this better. You can access all the APIs available in Windows, and do whatever you want through Windows object. In Android, you can not do anything except pushing poor notifications lol.
1
u/johnne86 Feb 01 '19
Are you referring to UWP apps? It seems as if UWP hasn't really taken off yet at all.
I would like to learn more about those because it seems that MS has a good platform for all that with .NET and Visual Studio, but it does seem as if Electron apps are more popular for making apps for Desktop OS's out of web technologies like HTML/CSS/JS.
0
1
0
u/ajm3232 Feb 02 '19
Honestly, not surprised. GPU libs have been out for a long time, top it off with more hardware API support every year almost and a push for offline wrbsites. Almost forgot to mention Google Firebase making it easy to drop in auth support.
121
u/GloriousBaconPirate Feb 01 '19
Can't really decide if I should be happy or scared.