Features/Apps/AppsManagement

From MozillaWiki
Jump to: navigation, search
Please use "Edit with form" above to edit this page.

Status

Apps Management App
Stage Draft
Status In progress
Release target TBD
Health OK
Status note Initial draft from etherpad notes - https://etherpad.mozilla.org/app-management-app-2012-06-22

Team

Product manager `
Directly Responsible Individual `
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

Open issues/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 metrics do we want to measure?
  • What is the plan for acquiring the AppMan App?
    • A: It will be in the Mozilla Marketplace.
  • 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
  • where will the desktop to App Man be hosted? A: Tentively, Thunder is open to hosting it with persona.org
  • who is building it? A: Nick, the intern, is building it. Bill owns making this happen.

Stage 1: Definition

1. 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:

  • 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.
  • App Man is for Android and Desktop

2. Users & 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.
  • 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.

3. Dependencies

  • AITC integration with Identity
  • Moz Apps API integration

4. Requirements

  • Display a list of all apps a user has downloaded/purchased for all devices and platforms (regardless of platform availability)
  • Offer the ability to install an app that is not installed on the device the user is currently on
  • Works offline

Non-goals

  • Require the management experience be mitigated through a browser.
  • App management for B2G

Stage 2: Design

5. Functional specification

Login screen - at URL <put in url here>

    • Privacy Policy opt-in (first time user)
    • Log into AITC

Logged in user List view of Apps:

  • Apps will be listed in a form factor fitting manner.
  • For each app, the following information should be shown: - app icon - app name ** developer name
    • 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

6. User experience design

https://www.dropbox.com/s/sced8f9hfb4av7x/apps-management-v1.pdf

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

  • 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)

Stage 5: Release

10. Landing criteria

`


Feature details

Priority Unprioritized
Rank 999
Theme / Goal `
Roadmap `
Secondary roadmap `
Feature list `
Project Apps
Engineering team `

Team status notes

  status notes
Products ` `
Engineering ` `
Security sec-review-needed
   
     Full Query    
ID Summary Priority Status
787482 SecReview: Apps Management App -- RESOLVED

1 Total; 0 Open (0%); 1 Resolved (100%); 0 Verified (0%);

Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `
The given value "
   
     Full Query    
ID Summary Priority Status
787482 SecReview: Apps Management App -- RESOLVED

1 Total; 0 Open (0%); 1 Resolved (100%); 0 Verified (0%);

" contains strip markers and therefore it cannot be parsed sufficiently.