Features/Jetpack/Jetpack-Mobile-Add-on-Tab: Difference between revisions
(Created page with "{{FeatureStatus |Feature name=Jetpack Mobile - Add-on Tab |Feature stage=Draft |Feature status=In progress |Feature health=OK }} {{FeatureTeam |Feature product manager=Dave Mason...") |
No edit summary |
||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=Jetpack Mobile - Add-on Tab | |Feature name=Jetpack Mobile - Add-on Tab | ||
|Feature stage= | |Feature stage=Landed | ||
|Feature status= | |Feature status=Complete | ||
|Feature version=SDK 1.6 | |||
|Feature health=OK | |Feature health=OK | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature product manager=Dave Mason | |Feature product manager=Dave Mason | ||
|Feature feature manager=Irakli Gozalishvili | |||
|Feature lead engineer=Irakli Gozalishvili | |||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
Revision as of 16:07, 6 April 2012
Status
| Jetpack Mobile - Add-on Tab | |
| Stage | Landed |
| Status | Complete |
| Release target | SDK 1.6 |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Jetpack Mobile - Add-on Tab
|Feature stage=Landed |Feature status=Complete |Feature version=SDK 1.6 |Feature health=OK |Feature status note=` }}
Team
| Product manager | Dave Mason |
| Directly Responsible Individual | Irakli Gozalishvili |
| Lead engineer | Irakli Gozalishvili |
| 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=Irakli Gozalishvili |Feature lead engineer=Irakli Gozalishvili |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
This feature should make the desktop version of Add-on Tab API work in mobile. The add-on tab API gives add-on developers the opportunity to have their add-on create a new tab with a reduced-chrome view and the ability to add html content to the tab. The mobile version should give developers the opportunity for their add-on to create a new standard tab that displays the html content within. There is no need for reduced chrome in the mobile version.
2. Users & use cases
The developer will use the Add-on Tab call within their add-on. When triggered in code, a new tab will open on the device and display content presented by the developer. This content can contain HTML.
3. Dependencies
Add-on Tab API (currently being worked on at time of this writing)
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=This feature should make the desktop version of Add-on Tab API work in mobile. The add-on tab API gives add-on developers the opportunity to have their add-on create a new tab with a reduced-chrome view and the ability to add html content to the tab. The mobile version should give developers the opportunity for their add-on to create a new standard tab that displays the html content within. There is no need for reduced chrome in the mobile version. |Feature users and use cases=The developer will use the Add-on Tab call within their add-on. When triggered in code, a new tab will open on the device and display content presented by the developer. This content can contain HTML. |Feature dependencies=Add-on Tab API (currently being worked on at time of this writing) |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=` }}