4 ms·
You're being unrealistic. The app not opening in a standalone window is a major change to the intended experience, and makes what can be, and was in a lot of ca
by meibo 3y ago
You're being unrealistic. The app not opening in a standalone window is a major change to the intended experience, and makes what can be, and was in a lot of cases, an experience equal to that of a native app no better than a web page from the early 10s.
- anakaine 3y agoVery much this. Apples move here is a very clear attempt to break UX via affecting UI in a negative fashion, and also takes away a key function that is to be expected of some apps (push notifications). This is very obviously and rather transparently a move to preserve their income stream via the walled garden that is the app store. This move additionally hurts developers. Developing a PWA is far simpler from a multi platform perspective since you're effectively building a responsive full screen website, and instead if you wish to preserve the full screen experience of your users on Apple devices you will.now need to pursue something which compiles to native code - meaning not your PWA. You've at least doubled your overhead development costs in most circumstances.
- jauntywundrkind 3y agoI find opening in a standalone app to be a far worse experience than a web page. PWAs seem like such a downgrade to me: no url bar, no forward/back, no bookmarks, usually no tabs or maybe limited tabs, extension buttons & awesome bar are gone... PWAs recreate a modality that offers less. I would rather have the affordances of a user ahent available. As a user, I wish my user agent would let me un-standalone PWAs & bring them back to the web. Especially as we start to create permissions like Direct Sockets which are gated on PWAs.
- DavideNL 3y agoYes, it's the usual "nudging" - annoy people slightly, but enough, to direct them in Apple's beneficial direction.