681544 - figure out UX and flows for adding and removing apps.

Status: RESOLVED INVALID

(Mozilla Labs :: F1, defect, P1)

Description

[Mark Hammond [:markh] [:mhammond]]

Very similar to bug 674121 - that bug talks about adding and removing accounts for already installed apps - this bug is about adding and removing apps themselves.

Shane tells me a requirement for F1 is that even though it will bundle much of the OWA code, it will *not* make any of the OWA UI available - so the "app dashboard" and "about:apps" will not exist.  (That is actually quite good, as some of it doesn't work correctly when bundled anyway ;)

This then leads to the following questions:

* How will our "builtin" apps be treated?  I'm guessing that our builtin apps will be automatically "available", but not automatically installed.  Eg, you will only get the builtin "linkedin" app installed by choosing to use it.

* If the above is true, how will the builtin apps be removed?  How is the UX/flow for app removal different from the UX/flow for logging out of the app?

* How will third-party apps which work with F1 be discovered, installed and uninstalled?

Comment 1

[Bryan Clark (DevTools PM) [:clarkbw]]

f1 is no longer an active project.  delete these messages by searching for: [closing_f1_project_bugs]