6 ms·
Its not honest. PWA has the same functionality as standard web app. You still need to grant permissions like Microphone Access, Camera access. Only differe
by adrr 3y ago
Its not honest. PWA has the same functionality as standard web app. You still need to grant permissions like Microphone Access, Camera access. Only difference is that a PWA has a manifest which defines appearance, splash screens, localization. Here's the starbucks PWA which is one the most popular PWAs.
https://app.starbucks.com/ https://app.starbucks.com/
- _factor 3y agoTry comparing that pwa to the native app and you'll soon find that most navigation ends up with quasi browser bars that obstruct the UI and slow the experience down. Apple surely does this on purpose to prevent PWAs from being useful. Can't let any App store competition arise.
- threeseed 3y ago> You still need to grant permissions like Microphone Access, Camera access "including isolation of storage and enforcement of system prompts to access privacy impacting capabilities on a per-site basis" One scenario is that today there is one instance of WebKit owned by the Home Screen process shared amongst all of the PWA apps which is enforcing that prompt. With third party engines that prompt would appear for the first app invocation but not any subsequent ones. This is only an issue with PWA since for normal apps the browser process is per-app rather than shared. Now they could rewrite the Home Screen execution environment to support one engine per app but their argument is that it's not worth their effort.
- adrr 3y agoYou run the apps in the context of the default browser app. The same way Mac OS does PWAs.