4 ms·

Is it though? A large portion of apps on the mobile app stores are already built using cross-platform technologies like React Native, Ionic or Flutter. In some

Is it though? A large portion of apps on the mobile app stores are already built using cross-platform technologies like React Native, Ionic or Flutter. In some instances it is very easy to tell, in other it's not. You can create quality experiences using cross-platform, you can create awful experiences using native tooling. In many instances, I'd rather have the not totally native app that exists than the absolutely perfectly native app that does not exist. As for PWAs, I am personally all for it. I have so many apps on my phone that don't need to be an app in the first place. Why not make a great PWA experience rather than a mediocre mobile app? In terms of capabilities, PWA are perfectly suitable for the majority of usecases.

szundi 3y ago
Exactly. Pwa is cheap
wkat4242 3y ago
One good thing about PWAs is that they run inside a browser. So if that's a good browser like firefox, you can use addons to limit tracking. Or force dark mode even for apps that don't bother implementing it (eg the Amazon shopping app) with dark reader.
- fiddlerwoaroof 3y ago
  This is exactly what I dislike about PWAs: the move to sandboxing everything in the browser is a big step back because the browser silos everything in a non-composable way.
chrisandchris 3y ago
I understand your point, but it somewhat says that making awesome native apps is not even an option anymore. I use Things (a todo app) daily. It was #1 of Design in the AppStore maybe already 5 years ago. I think it's a perfect example for a beautifully made native app. I really feel how the native behaviour workes so much smoother. I would love for creators to somehow strive more for beautifully made apps instead of the fast profit.
- mzronek 3y ago
  Things is a great example for PWAs, because it does not exist on Android, Linux or Windows. It could be though, if it would be a PWA. It is not and it seems like the developer focused its resources on native software for Apple products.
  - chrisandchris 3y ago
    It could, yes. But the user experience and the amazing level of usability will degrade, and I would move to another product.
    - radlad 3y ago
      And we've come full circle! > But as a web dev community we need to stand firm and build PWAs regardless. If we treat pwas on iOS like we did Internet explorer (i.e. giving it special attention and hack solutions as opposed to just not developing for it) we will lose the fight.
    - joking 3y ago
      Comeon, it’s a todo app, being native provides marginal benefits over its functionality.
      - chrisandchris 3y ago
        Except that it feels smoother (the UI, animations, UX) instead of a web app, and is amazingly fast/reactive?
- brodock 3y ago
  No one wants to invest time and effort to develop for a platform that has a horrible review process. You have to invest multiple people's months worth of work without knowing if that particular snapshot of your app will offend the reviwer. The lack of native apps is the App Store reviews process fault.
  - 3y ago

szundi 3y ago

Exactly. Pwa is cheap

wkat4242 3y ago

One good thing about PWAs is that they run inside a browser. So if that's a good browser like firefox, you can use addons to limit tracking. Or force dark mode even for apps that don't bother implementing it (eg the Amazon shopping app) with dark reader.

fiddlerwoaroof 3y ago
This is exactly what I dislike about PWAs: the move to sandboxing everything in the browser is a big step back because the browser silos everything in a non-composable way.

chrisandchris 3y ago

I understand your point, but it somewhat says that making awesome native apps is not even an option anymore. I use Things (a todo app) daily. It was #1 of Design in the AppStore maybe already 5 years ago. I think it's a perfect example for a beautifully made native app. I really feel how the native behaviour workes so much smoother. I would love for creators to somehow strive more for beautifully made apps instead of the fast profit.

mzronek 3y ago
Things is a great example for PWAs, because it does not exist on Android, Linux or Windows. It could be though, if it would be a PWA. It is not and it seems like the developer focused its resources on native software for Apple products.
- chrisandchris 3y ago
  It could, yes. But the user experience and the amazing level of usability will degrade, and I would move to another product.
  - radlad 3y ago
    And we've come full circle! > But as a web dev community we need to stand firm and build PWAs regardless. If we treat pwas on iOS like we did Internet explorer (i.e. giving it special attention and hack solutions as opposed to just not developing for it) we will lose the fight.
  - joking 3y ago
    Comeon, it’s a todo app, being native provides marginal benefits over its functionality.
    - chrisandchris 3y ago
      Except that it feels smoother (the UI, animations, UX) instead of a web app, and is amazingly fast/reactive?
brodock 3y ago
No one wants to invest time and effort to develop for a platform that has a horrible review process. You have to invest multiple people's months worth of work without knowing if that particular snapshot of your app will offend the reviwer. The lack of native apps is the App Store reviews process fault.
- 3y ago