(no title)
theK | 3 months ago
And once you start thinking about it, the same thing goes for a surprisingly large amount of apps.
I feel like in the coming years the facade big A and big G put up in order to push everyone into their distinctive walled garden of apps will crumble in public opinion.
It never was "yeah, it needs to be an app because the web platform doesn't have an API standard for it", geez, apple even forced a single web engine. They could have easily allowed access to their APIs on the browser. It just never was in their corporate interest to do so.
Okay, this devolved into an anti corporate rant without it being my intention to... So, go web!
neilalexander|3 months ago
One is where relatively-static content is the priority, deep-linking is important or essential and the web platform is pretty ideal for those. News articles or blogs or Wikipedia pages or those sorts of things. Things where I might want to be switching between tabs or forgetting about for a while and coming back to later.
The other is where the app is primarily interactive or where the content is a lot more likely to be real-time or ephemeral. Not least because if you're on a low-bandwidth or high-RTT connection, navigating between web pages or having interactivity blocked behind a backlog of XHRs (particularly where caching isn't permitted) is utterly miserable. My experience is that native apps usually continue feeling responsive to input even when the network itself is not responsive but that is often not true with many clickable elements in many web pages.
PWAs might be the middle-ground here but they feel a lot like Electron apps to me: still foreign to all platforms, not responsive in the way that native UI controls are, weird/missing "back" behaviours and still no better support for deep-linking than the average app would have.