Features/Jetpack/Add-on SDK: the Missing Pieces

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


Add-on SDK: the Missing Pieces
Stage Draft
Status In progress
Release target `
Health OK
Status note Investigating as part of post-1.0 planning


Product manager David Mason
Directly Responsible Individual David Mason/Myk Melez
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

Open issues/risks


Stage 1: Definition

1. Feature overview

There are several notable missing pieces in the functionality provided by the first stable release of the SDK. This feature addresses those omissions by adding the following set of functionality:

APIs in order of Priority

API Priority Status
Prefs API P1 development
Add-on Tab API P1 design
Places API P2 design
Awesome Bar API P2 design
Add-on Menu P2 design
Sidebar API P3 design
Tab Groups API P3 design

Other work in order of Priority

API Priority Status
minimal XPIs P1 development
packed XPIs P2 planning
addon testing without browser restart P2 design

2. Users & use cases

The target audience is addon developers. The use case is an add-on developer using the Add-on SDK (either directly or via the Add-on Builder) to build an addon.

3. Dependencies


4. Requirements




Stage 2: Design

5. Functional specification


6. User experience design


Stage 3: Planning

7. Implementation plan

Due to the UI mapping nature of supporting Firefox mobile, we will start only with the Preferences API until we have mobile support. Once we have that we should have a better understanding of how UI elements will map from desktop to mobile and be able to handle the remaining features in the Overview section.

8. Reviews

Security review


Privacy review


Localization review




Quality Assurance review


Operations review


Stage 4: Development

9. Implementation

Many of the items listed in the overview will begin in conjunction with our P1 work so developers do not have to devote 100% of their time to just one feature. Therefore, the status of this full-set feature will be in progress until all items are completed or determined to be part of another feature, or no longer needed or wanted.

Stage 5: Release

10. Landing criteria


Feature details

Priority P2
Rank 999
Theme / Goal `
Roadmap Jetpack
Secondary roadmap `
Feature list Jetpack
Project `
Engineering team Jetpack

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `