Closed Bug 761048 Opened 12 years ago Closed 12 years ago

Define and Implement Uninstall App End-User Flow


(Firefox for Android Graveyard :: Web Apps (PWAs), defect)

15 Branch
Not set



blocking-kilimanjaro ?


(Reporter: jsmith, Unassigned)



(Whiteboard: [qa-])

We need to come up with an end-user version of the uninstall flow for the web runtime on Android. Currently, there is no explicit way for a user to know how to uninstall an app without knowing that about:apps explicitly exists. Even so, the current uninstall flow won't remove the shortcut from the user's machine if it's been added. We need to determine what the end-user UX flow is for uninstalling an installed web application that is discoverable, feasible, and easy for the user to use.

There's debate right now is right now if it's even possible to remove a shortcut from a user's homescreen. I did see this though that mentioned something about being able to remove shortcuts created by me, but not other existing ones:

Also saw this:
Keywords: uiwanted
Keywords: productwanted
We need better information from the app uninstall process to do this I think. See bug 760708.
Depends on: 760708
Keywords: meta
Definitely a blocker for the first release - we need have a usable uninstall flow, even from about:apps if that's what we are going for now.
Whiteboard: [android-feasibility]
k9o nomination - something needs to be decided here, as uninstall is a basic user flow for apps
blocking-kilimanjaro: --- → ?
No longer blocks: Blocking-FFA-WebRT1+
Shortcut being removed from homescreen is 'uninstall' which is implemented. Will file followup bug for cleanup of profiles by fennec native when user uninstalls it.
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [android-feasibility]
Whiteboard: [qa-]
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.