As this is geared toward website owners who don't have the resources, and/or need, to create a native app, this is pretty good for that use case. It's all about visibility. We'll probably see a...
As this is geared toward website owners who don't have the resources, and/or need, to create a native app, this is pretty good for that use case. It's all about visibility. We'll probably see a lot more web apps in the Play Store, helping boost Google's numbers and potential ad spend on the platform.
We've had Cordova for ages, which is more featureful (aside from the one feature that Chrome PWAs enable, which is session sharing with Chrome) and lets you bridge into Java code easily. But a lot of websites simply don't need those features, so PWA is a neat streamlined approach.
Hope this doesn't result in web developers even further prioritizing Chrome compatibility over other browsers though.
(Meta: Should this maybe be in ~comp since it's more about the development side of things?)
As long as it's not too onerous, I probably might as well. It would probably help with all the people that always ask about an app and are averse to just using the browser (and the existing PWA...
As long as it's not too onerous, I probably might as well. It would probably help with all the people that always ask about an app and are averse to just using the browser (and the existing PWA aspects).
It looks like it involves a bit of work though, so it's not something I can do extremely easily. I'll add an issue to remember to look more into it later.
I'm a big fan of PWAs. I guess this is just a way of extending your reach from your website to the store search. It's certainly cleaner than the annoying "Save this as a webapp for later?"...
I'm a big fan of PWAs. I guess this is just a way of extending your reach from your website to the store search. It's certainly cleaner than the annoying "Save this as a webapp for later?" approach which has been encouraged until now.
As this is geared toward website owners who don't have the resources, and/or need, to create a native app, this is pretty good for that use case. It's all about visibility. We'll probably see a lot more web apps in the Play Store, helping boost Google's numbers and potential ad spend on the platform.
We've had Cordova for ages, which is more featureful (aside from the one feature that Chrome PWAs enable, which is session sharing with Chrome) and lets you bridge into Java code easily. But a lot of websites simply don't need those features, so PWA is a neat streamlined approach.
Hope this doesn't result in web developers even further prioritizing Chrome compatibility over other browsers though.
(Meta: Should this maybe be in ~comp since it's more about the development side of things?)
Any plans to put Tildes up there, OP?
As long as it's not too onerous, I probably might as well. It would probably help with all the people that always ask about an app and are averse to just using the browser (and the existing PWA aspects).
It looks like it involves a bit of work though, so it's not something I can do extremely easily. I'll add an issue to remember to look more into it later.
I'm a big fan of PWAs. I guess this is just a way of extending your reach from your website to the store search. It's certainly cleaner than the annoying "Save this as a webapp for later?" approach which has been encouraged until now.