4 ms·

I've built large, complex and beautiful healthcare apps as a PWA. The only two things I've ever missed from native functionality are: - background geolocation

I've built large, complex and beautiful healthcare apps as a PWA. The only two things I've ever missed from native functionality are: - background geolocation - push notifications on ios The second one was fixed recently. In contrast, from what I've seen 90+ percent of apps I see in the app stores would be better as a web page / PWA.

dangus 3y ago
But the real question is where most of your users live. I’d take a decent wager that most of your users are most familiar with apps and would prefer installing full apps. Doesn’t matter that most apps would be better suited to being a web page or PWA if that’s not where the users are. That’s kind of like saying that PCs are better at gaming than consoles. Yes, that’s true, but that’s not where the majority of users are.
- johnnyanmac 3y ago
  I mean, PWAs aren't made with the goal to maximize User UX. It's a cost saving measure like any other solution that isn't making 2 dedicated native apps for IOS/Android.it won't get as much traffic as a native app, but it's almost "free" to deploy. To use the gaming console example, it's not unlike using an emulator to launch your game on PC (if you could somehow monetize an emulated rom). It's not the ideal experience, but it requires very little extra work.
  - callalex 3y ago
    I find PWAs to have a vastly superior UX. I can trust that they are running in the strongest sandbox my device has to offer. I don’t have to download anything, and I don’t have to update anything. I don’t have to remember any account passwords to install anything, and my ad blockers and password managers just work inside them. I don’t have to worry about arbitrary content policies of Apple or Google, the app can just show me whatever it wants.
- kristiandupont 3y ago
  >But the real question is where most of your users live. Well, they "live" on their phone. I would just put a button on my website to install the app, users would find that easily.

dangus 3y ago

But the real question is where most of your users live. I’d take a decent wager that most of your users are most familiar with apps and would prefer installing full apps. Doesn’t matter that most apps would be better suited to being a web page or PWA if that’s not where the users are. That’s kind of like saying that PCs are better at gaming than consoles. Yes, that’s true, but that’s not where the majority of users are.

johnnyanmac 3y ago
I mean, PWAs aren't made with the goal to maximize User UX. It's a cost saving measure like any other solution that isn't making 2 dedicated native apps for IOS/Android.it won't get as much traffic as a native app, but it's almost "free" to deploy. To use the gaming console example, it's not unlike using an emulator to launch your game on PC (if you could somehow monetize an emulated rom). It's not the ideal experience, but it requires very little extra work.
- callalex 3y ago
  I find PWAs to have a vastly superior UX. I can trust that they are running in the strongest sandbox my device has to offer. I don’t have to download anything, and I don’t have to update anything. I don’t have to remember any account passwords to install anything, and my ad blockers and password managers just work inside them. I don’t have to worry about arbitrary content policies of Apple or Google, the app can just show me whatever it wants.
kristiandupont 3y ago
>But the real question is where most of your users live. Well, they "live" on their phone. I would just put a button on my website to install the app, users would find that easily.