-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
user initiated 'uninstall' event #998
Comments
Some related lifecycle events stuff is here too: The "appinstall" event was at least defined as part of Web Manifest, but doesn't interact with a service worker. Also related (manifest + SW integration): Which would associate a PWA with a service worker. That would be the right place to maybe receive any such "uninstall" event. Having said that, last I heard, there was no way for Android today to notify the browser when a PWA's icon is removed from the home screen. I heard rumors that such an OS-level event is coming to a future version of Android, but maybe someone from Google can confirm? |
For reference, "installable web applications". |
Chrome now introduced WebAPKs for Android: But as far as I understand, they don't provide an This is extremely problematic since an user will continue to receive pushes notifications also after uninstalling the WebAPK. An |
I'm looking for clarification of how a user might 'uninstall' a Progressive Web App that has been installed on their home screen.
Use case :
At this point, iinm, all they have is 'remove' to remove the icon from the homescreen. I imagine the user might assume this would also remove the service worker and the associated caches, but I think this is not the case, and so there is little benefit to the user (short of making space on the home screen).
IINM, the only method of removing a service worker is via the chrome://serviceworker-internals page which is clearly not end-user friendly.
It strikes me that it might be possible for the 'remove' action to cause an 'uninstall' event to be fired in the corresponding service worker, and then it is up to the service worker to remove the caches and/or unregister itself, presumably causing it to be removed completely from chrome (akin to the chrome://serviceworker-internals 'unregister' button). This leaves the possibility for the sw to not uninstall itself/etc, which might possibly be desirable - or at least prompt the user before doing so (via the app) - and also sending a message to a server to record that the user has decided to uninstall (useful for the app's authors to know).
On the other hand, all that sounds like it is riddled with problems (not least privacy), so perhaps it should be possible for the user to do a 'hard uninstall' where the service worker and caches are just removed without any events/etc....or a combination.
Is this 'death' part of the PWA life cycle being discussed anywhere? ..or is it all here, which I've yet to dig through.
The text was updated successfully, but these errors were encountered: