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

Please use "Edit with form" above to edit this page.

Status

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

{{#set:Feature name=Add-on SDK: the Missing Pieces

|Feature stage=Draft |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=Investigating as part of post-1.0 planning }}

Team

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	`

{{#set:Feature product manager=David Mason

|Feature feature manager=David Mason/Myk Melez |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

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

`

Non-goals

`

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

`

Accessibility

`

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

` {{#set:Feature open issues and risks=` |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

|Feature users and 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. |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature 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. |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=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. |Feature landing criteria=` }}

Feature details

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

{{#set:Feature priority=P2

|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=` }}