2 ms·
For one I don't think PWAs will, should or can kill all native apps. But I think they could replace a specific subset of native apps that aren't doing anything
by afavour 4y ago
For one I don't think PWAs will, should or can kill all native apps. But I think they could replace a specific subset of native apps that aren't doing anything particularly ambitious in terms of feature set or UI. The article is pretty long but for me there are two core reasons:
- people are used to getting apps from the App/Play Store. It's a very well understood dynamic. Installing from a web page is strange.
- Apple have helped make the above an even bigger problem that it needs to be by making their 'add to Home Screen' option two menus deep with no way to trigger it as a result of user action.
That's about it, really. I know people are coming to this thread to say PWAs fail because the UI is bad or because they're slow or this or that... I don't buy that argument simply because I know of a ton of slow native apps that have poor UI that are successful. Non-power users don't really care all that much if you're offering functionality they want to use (within reason, of course). I would still love to see a web API for something equivalent to UITableView, though.
- kitsunesoba 4y ago> I would still love to see a web API for something equivalent to UITableView, though. If browsers started shipping support for typical UI widgets like that, I would become much more interested in the web as a platform. Bring Your Own Everything is fine for traditional websites but I strongly dislike it for building something complex enough to be considered an "app".