|
|
|
|
|
by ChrisKingWebDev
1951 days ago
|
|
There is a major point missing from the cons list about PWAs. Most people don't know what they are and it's a major pain to install them on iOS. I'm at the point where I want to start monetizing an app I have, but realistically I have to use iOS In App Purchases. If I told the average person on the street that my app is a PWA and they can install it on their home page, they wouldn't know what to do. |
|
So sure, you still end up paying the Apple/Google tax for discovery (and the Apple tax for looking like an app instead of a webpage) but it gets you that discovery you want and you only need to maintain a single codebase.
And example is my app which I packaged up using https://www.pwabuilder.com/. It was just a couple of clicks to publish to the Play Store. It will look as pretty as you make it and most users won't realize that it isn't a "native" app. Honestly the biggest issue is that it doesn't download the app until the first launch. (Although you can use different tooling to include a copy of the site in the app)
https://play.google.com/store/apps/details?id=com.player_one...