Features/Jetpack/Jetpack-Mobile-Simple-Prefs
Status
| Jetpack Mobile - Simple Prefs | |
| Stage | Complete |
| Status | Complete |
| Release target | ` |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Jetpack Mobile - Simple Prefs
|Feature stage=Complete |Feature status=Complete |Feature version=` |Feature health=OK |Feature status note=` }}
Team
| Product manager | Dave Mason |
| Directly Responsible Individual | ` |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Dave Mason
|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=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
As we continue to make sure that the APIs we have work with Firefox Mobile we are following a path that looks at our more popular add-ons to see which features are used most often in their creation. Preferences are essential to our most popular add-ons and should work seamlessly when the developer wishes to port their add-on to Mobile Firefox.
As we already have a simple-prefs API, this feature is to ensure that it works with Mobile Firefox. Our prefs are defined by the developer in JSON and can then be displayed in either XUL or the Native preferences dialog. As the preferences for Firefox itself are being displayed in the Native Android settings tool, it should likely follow that add-ons prefs also appear there. If there are issues with doing so, perhaps XUL or HTML can be considered instead.
2. Users & use cases
The Developer defines the preferences needed for their add-on in their package.json file. Those preferences are then converted upon run-time to a native preferences screen which allows those preferences to appear in the Native settings dialog below the other Firefox Preferences in an Add-on Settings option(with the add-on's name displayed).
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
`
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=` |Feature overview=As we continue to make sure that the APIs we have work with Firefox Mobile we are following a path that looks at our more popular add-ons to see which features are used most often in their creation. Preferences are essential to our most popular add-ons and should work seamlessly when the developer wishes to port their add-on to Mobile Firefox.
As we already have a simple-prefs API, this feature is to ensure that it works with Mobile Firefox. Our prefs are defined by the developer in JSON and can then be displayed in either XUL or the Native preferences dialog. As the preferences for Firefox itself are being displayed in the Native Android settings tool, it should likely follow that add-ons prefs also appear there. If there are issues with doing so, perhaps XUL or HTML can be considered instead. |Feature users and use cases=The Developer defines the preferences needed for their add-on in their package.json file. Those preferences are then converted upon run-time to a native preferences screen which allows those preferences to appear in the Native settings dialog below the other Firefox Preferences in an Add-on Settings option(with the add-on's name displayed). |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |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 | P1 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Jetpack |
| Secondary roadmap | ` |
| Feature list | Jetpack |
| Project | ` |
| Engineering team | Jetpack |
{{#set:Feature priority=P1
|Feature rank=999 |Feature theme=` |Feature roadmap=Jetpack |Feature secondary roadmap=` |Feature list=Jetpack |Feature project=` |Feature engineering team=Jetpack }}
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=` }}