110
Apple Wants To Kill PWAs
(medium.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Feb 2024
110 points (88.2% liked)
Programming
17748 readers
509 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
No, it will kill PWAs. And since Apple dictates what everyone else does, this also automatically means PWAs are dead on Android, too. It'll probably get prevented system-side in the future no matter which browser you use, they'll find a way.
Why would they be dead on Android?
A big benefit is writing the app once and it working everywhere. If it only works on Android, people will just default to the tools tailored to that platform anyway.
But it wouldn't only work on Android. It would also work on Windows and Unix and any other niche operating system that can run a browser (my Blu-ray recorder has a browser in it). There's a whole world outside Apple/Android. This message brought to you by a browser running on Windows...
That's theoretically true, but in practice, the desktop experience (screen size, interaction model, etc.) is sufficiently different that adapting it to mobile to get an app-like experience is not that different from building a separate app.
It's not at all like building a separate app. All the back-end code is identical - all you have to do is make the mobile version not take up as much screen-space, and that's not much work. e.g. on desktop I use icon and text, but on mobile icon only.
Then why do you think most business are already writing a separate Android app rather than just optimising their mobile website?
But "make the mobile version not take up as much screen-space" is not as simple as simply zooming out and just hiding some icon labels. And just the fact that people interact by touch rather than with a mouse and keyboard is already a major adjustment.
Anyway, I'll leave it at this, since I feel like there's not much to gain here for me from the discussion anymore :) Cheers!
I don't think that. I know some businesses who are still writing separate apps, instead of switching to cross-platform. You'll have to ask them why they're doing that. It frustrates me no end when platform-specific bugs come up because they're running different code on each platform, each written by different people.
...makes no difference at all. Whether a user has touched a button, clicked on it, or tabbed to it and pressed enter, the same Button.Clicked event gets triggered.