Additional distribution points
Status
| Additional distribution points | |
| Stage | Feature Inbox |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Additional distribution points
|Feature stage=Feature Inbox |Feature status=` |Feature version=` |Feature health=OK |Feature status note=` }}
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 | Nate Watson |
{{#set:Feature product manager=`
|Feature feature manager=` |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=Nate Watson }}
Open issues/risks
How much is this going to cost?
Stage 1: Definition
1. Feature overview
Right now, the only distribution points for Firefox Mobile are the Mozilla download servers, Google Play, and Getjar "although I'm unsure if the last one is official or not." These can't reach a large number of Android devices. For example, play won't normally work on Kindle or Nook devices. The idea behind this feature is to allow Firefox to be downloaded from additional distribution points. This is important because there are many users who use devices that don't have Getjar or Play and would prefer not to, or are unable to, get apps from a third party, and these users should be able to use Firefox. The goal distribution points are "as of 9/21/2012": Amazon Appstore, Nook App Store "although it's not feasible to support all devices on this one", and Getjar "if the current version is not official / doesn't include the tablet UX".
2. Users & use cases
The target users are users who have access to these distribution points, but not Google Play, or have some problem with downloading it directly from the Mozilla Servers.
3. Dependencies
Unknown
4. Requirements
1. Registration costs 2. setting up automatic updating for these distribution points. 3. to be filled in
Non-goals
We're not trying to support every Android App store in existence, but just to add an incremental improvement.
Stage 2: Design
5. Functional specification
`
6. User experience design
N/A
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
`
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=How much is this going to cost? |Feature overview=Right now, the only distribution points for Firefox Mobile are the Mozilla download servers, Google Play, and Getjar "although I'm unsure if the last one is official or not." These can't reach a large number of Android devices. For example, play won't normally work on Kindle or Nook devices. The idea behind this feature is to allow Firefox to be downloaded from additional distribution points. This is important because there are many users who use devices that don't have Getjar or Play and would prefer not to, or are unable to, get apps from a third party, and these users should be able to use Firefox. The goal distribution points are "as of 9/21/2012": Amazon Appstore, Nook App Store "although it's not feasible to support all devices on this one", and Getjar "if the current version is not official / doesn't include the tablet UX". |Feature users and use cases=The target users are users who have access to these distribution points, but not Google Play, or have some problem with downloading it directly from the Mozilla Servers. |Feature dependencies=Unknown |Feature requirements=1. Registration costs 2. setting up automatic updating for these distribution points. 3. to be filled in |Feature non-goals=We're not trying to support every Android App store in existence, but just to add an incremental improvement. |Feature functional spec=` |Feature ux design=N/A |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | Unprioritized |
| Rank | 999 |
| Theme / Goal | Discover |
| Roadmap | Firefox Mobile |
| Secondary roadmap | Third Party Services |
| Feature list | Mobile |
| Project | ` |
| Engineering team | ` |
{{#set:Feature priority=Unprioritized
|Feature rank=999 |Feature theme=Discover |Feature roadmap=Firefox Mobile |Feature secondary roadmap=Third Party Services |Feature list=Mobile |Feature project=` |Feature engineering team=` }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}
The list of planned supported distribution points is subject to change.