3 ms·

To add a few: - Ability to stay in memory for longer due to lower consumption - Less weirdness with navigation - More “solid” feel (less layout shifting, “fl

To add a few: - 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)

jeroenhd 3y ago
> - Less weirdness with navigation > - 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/ https://vger.app/) feel like native on my phone, except that something feels off because of the iOS behaviour.
- jwells89 3y ago
  Might be missing something here, but shouldn’t native scrolling behavior be obtainable by just letting the browser do its thing instead of manually managing it?
  - jeroenhd 3y ago
    Only partially, as far as I understand it. To get the "native" scroll on iOS, you need to add a line or two of CSS (-webkit-overflow-scrolling) here and there. It's harder on the slower frameworks (Flutter etc.) where you're basically running a Javascript browser engine inside your browser, so you need to implement that behaviour manually (which usually means "wrongly"). Implementing native back button behaviour is more annoying, requiring you to hook into the browser navigation mechanism.
candiddevmike 3y ago
Shameless plug: my app Homechart (https://web.homechart.app https://web.homechart.app) doesn't really have those issues (uses Mithril and extremely limited dependencies).
- monocularvision 3y ago
  I just opened the link in Safari on my iPhone. I scrolled down to see the rest of the page but noticed I couldn’t scroll all the way to the bottom. I could see the bottom peek out from behind the address bar but when I let go of the scrolling it would pop back up so I couldn’t scroll fully to the bottom. 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.

jeroenhd 3y ago

> - Less weirdness with navigation > - 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/ https://vger.app/) feel like native on my phone, except that something feels off because of the iOS behaviour.

jwells89 3y ago
Might be missing something here, but shouldn’t native scrolling behavior be obtainable by just letting the browser do its thing instead of manually managing it?
- jeroenhd 3y ago
  Only partially, as far as I understand it. To get the "native" scroll on iOS, you need to add a line or two of CSS (-webkit-overflow-scrolling) here and there. It's harder on the slower frameworks (Flutter etc.) where you're basically running a Javascript browser engine inside your browser, so you need to implement that behaviour manually (which usually means "wrongly"). Implementing native back button behaviour is more annoying, requiring you to hook into the browser navigation mechanism.

candiddevmike 3y ago

Shameless plug: my app Homechart (https://web.homechart.app https://web.homechart.app) doesn't really have those issues (uses Mithril and extremely limited dependencies).

monocularvision 3y ago
I just opened the link in Safari on my iPhone. I scrolled down to see the rest of the page but noticed I couldn’t scroll all the way to the bottom. I could see the bottom peek out from behind the address bar but when I let go of the scrolling it would pop back up so I couldn’t scroll fully to the bottom. 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.