Post

But pwas are not good for us. We just don't know better.

I am pretty confident we implemented push notifications for a PWA, a few months ago, here in Italy. We used a third party service for easier integration but it shouldn‘t matter, I believe. So the ”not available in the EU” caveat seems inaccurate.

PWAs don't pay app store fees.

100%

Example? I’m not seeing it.

It's *apple.* Why do you expect anything else?

Thank you. Sounds like Apple’s concern was that DMA terms required them to implement the much more permissive Android-style PWA, allowing deep HW access, arbitrary data storage, etc. They reversed course when the EC assured them it would be sufficient to limit PWAs the more secure WebKit engine.

It's been like that for over 10 years. In the PWA I was writing recently, we deliberately descoped any iOS support for the installation process since there's literally nothing we can do programmatically to help users install the app - it has to be manual, the way you described.

Thanks! If you like that, I have a few more; ffmpeg.guru and sql.duckpdf.app they all run on your device in a wasm sandbox so all your files stay yours and you can install them all as PWAs. The sql one is super helpful for modifying massive csv and excel files

PWAs are awesome once you can train your users to install them. I still get about an email every week telling me they can't find my app in the app store though.

I'd love to have a full blow by blow of why it was done that way I honestly think it would be useful as a design guidline, like an anti-pattern to avoid in the process or my favorite: past: click->desired data Now: click->'helpful' landing page-> 'helpful' landing page -> desired data