Biggest ones for me:
- Password Manager APIs
- Notification channels
- Share Targets (Android supports this, kind of)
- Widgets
- Password Manager APIs
- Notification channels
- Share Targets (Android supports this, kind of)
- Widgets
- Ability to stay in memory for longer due to lower consumption
- Less weirdness with navigation
- More “solid” feel (less layout shifting, “flashes”, etc)
- More good practices on the default/happy path (less UX to have to think about and import libraries for)
> - More “solid” feel (less layout shifting, “flashes”, etc)
These are the result of the frameworks chosen, not PWAs themselves. Flutter PWAs are always going to be slow and weird, but there are some real gems out there that feel and navigate like native apps.
One annoying issue: Android and iOS have different standards for things like scrolling, animations, gestures, and whatnot. Apps like Voyager (https://vger.app/) feel like native on my phone, except that something feels off because of the iOS behaviour.
Implementing native back button behaviour is more annoying, requiring you to hook into the browser navigation mechanism.
I then scrolled again and this time it worked. I then refreshed the page to try again but noticed that the page started already scrolled and I couldn’t get it to properly centered right.
After yet another refresh I was getting the original scrolling issue. I also noticed that when scrolling down the top portion of the screen is a solid white bar which looks out of place.
I say all this not to pick on you but I constantly see web devs talk about how great you can make a PWA but it is constantly all of these little oddities that make the experience feel so subpar compared to a native app.
* Chrome on Android supports that.
navigator.share({ title, text, url: url })