canmove, Confirmed users
457
edits
Features/Apps/AppsManagement: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "{{FeatureStatus |Feature name=Apps Management App |Feature stage=Draft |Feature status=In progress |Feature version=TBD |Feature health=OK |Feature status note=Initial draft from...") |
No edit summary |
||
| Line 11: | Line 11: | ||
|Feature open issues and risks=* Is App Management branded more by Apps or more by Identity? | |Feature open issues and risks=* Is App Management branded more by Apps or more by Identity? | ||
* What is the threshold of max apps installed before the performance of the dashboard degrades? Per platform? | * What is the threshold of max apps installed before the performance of the dashboard degrades? Per platform? | ||
* What metrics do we want to measure? | * What metrics do we want to measure? | ||
|Feature overview= | * What is the plan for acquiring the AppMan App? | ||
** A: It will be in the Mozilla Marketplace. | |||
This specification describes the AppMan app, an HTML5-based app for managing a Mozilla Apps user's apps across all marketplaces and devices. | * Are there other forms of discovery of this AppMan? | ||
* Will it's design and funcationality conflict with the design of the new new tab in FF desktop? | |||
* What is the apps management approach for Android? | |||
**A:what can we do on android, 1: | |||
- we could try to offer centralized management for ALL android apps, native or otherwise | |||
- it would be like the many launchers offered on Google Play | |||
** what we can do android, 2: | |||
- build clean management silo only for Mozilla Apps | |||
* Need UX for the log in flow | |||
* Can users reach App Man on non-FF browsers as a web page? See icloud.com | |||
* Need the copy for the privacy policy. | |||
* Missing UX flow for privacy policy opt-in | |||
|Feature overview=This specification describes the AppMan app, an HTML5-based app for managing a Mozilla Apps user's apps across all marketplaces and devices. | |||
Goals: | Goals: | ||
* Give users a consistent experience of manging their Apps across all their devices and across all the App stores and self-publishers they deal with. | * Give users a consistent experience of manging their Apps across all their devices and across all the App stores and self-publishers they deal with. | ||
* Deliver the management experience in a manner that integrates with each device. | * Deliver the management experience in a manner that integrates with each device. | ||
* App Man is for Android and Desktop | * App Man is for Android and Desktop | ||
|Feature users and use cases=* An Android Mozilla Apps user wants to see all his acquired apps in one place. | |Feature users and use cases=* An Android Mozilla Apps user wants to see all his acquired apps in one place. | ||
* A Desktop Mozilla Apps user wants to see all his acquired apps in one place. | * A Desktop Mozilla Apps user wants to see all his acquired apps in one place. | ||
* An Android Mozilla Apps user wants to natively install an acquired app on their device. | * An Android Mozilla Apps user wants to natively install an acquired app on their device. | ||
* A Desktop Mozilla Apps user wants to natively install an acquired app on their desktop. | * A Desktop Mozilla Apps user wants to natively install an acquired app on their desktop. | ||
|Feature dependencies=* AITC integration with Identity | |Feature dependencies=* AITC integration with Identity | ||
* Moz Apps API integration | * Moz Apps API integration | ||
| Line 32: | Line 41: | ||
* Offer the ability to install an app that is not installed on the device the user is currently on | * Offer the ability to install an app that is not installed on the device the user is currently on | ||
* Shall work offline | * Shall work offline | ||
|Feature non-goals=* Require the management experience be mitigated through a browser. | |Feature non-goals=* Require the management experience be mitigated through a browser. | ||
* App management for B2G | * App management for B2G | ||
| Line 46: | Line 54: | ||
** installed inactive button OR install button | ** installed inactive button OR install button | ||
** BUTTON STATES 1. App is installed on current device - show "installed", grayed out, inactive 2. App is not installed on current device, but has been downloaded on this or other device at some point in time - show "install", active button | ** BUTTON STATES 1. App is installed on current device - show "installed", grayed out, inactive 2. App is not installed on current device, but has been downloaded on this or other device at some point in time - show "install", active button | ||
|Feature ux design=https://www.dropbox.com/s/sced8f9hfb4av7x/apps-management-v1.pdf | |||
|Feature implementation notes=* AppMan talks to mozApps API to get list of natively installed apps (requires whitelist) | |||
* AppMan talks to mozApps API to get list of acquired apps (backed by AitC in the background) | |||
* AppMan takes full advantage of AppCache to reduce server load (actually utility during offline is iffy) | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||