Apps/Project Plans/Firefox Mobile Apps v1: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Initiative: "Firefox Mobile Apps v1"=
=Initiative: "Firefox Mobile Apps v1"=
This initiative is about Apps running on Gecko runtime. It pushes us again toward our goal of bringing open web apps to all the users of the web. Apps for 300 million desktop users, '''25 million+ Mobile FF users''', and millions of FxOS users.  
This initiative is about Apps running on Gecko runtime. It pushes us again toward our goal of bringing open web apps to all the users of the web. Apps for millions of desktop and Mobile FF users in addition to FxOS users.  


For Developers, "Firefox Mobile Apps v1" will simply provide a gateway to the global audience and momentum of Firefox Mobile. Developers can begin to grow at the rate of deployment of FxOS, pacing with Android, creating apps with all the powerful features that users expect from native apps; empowered with all the benefits of the open web, supported with the structure and services of a traditional marketplace. It's time to bust open the gates, and share with millions of developers the amazing opportunity we see.
For Developers, "Firefox Mobile Apps v1" will simply provide a gateway to the global audience and momentum of Firefox Mobile. Developers can begin to grow at the rate of deployment of FxOS, pacing with Android, creating apps with all the powerful features that users expect from native apps; empowered with all the benefits of the open web, supported with the structure and services of a traditional marketplace. It's time to bust open the gates, and share with millions of developers the amazing opportunity we see.
Line 8: Line 8:
*Mozilla - gecko runtime consistent on all platforms  
*Mozilla - gecko runtime consistent on all platforms  
*End-User - my Apps work on all my devices, pay once  
*End-User - my Apps work on all my devices, pay once  
*Operator - remove control point, keep direct to consumer model
*Operator - remove control points of controlled ecosystems, keep direct to consumer model across all your platforms


==Goals for the "Firefox Mobile Apps 1" initiative==
==Goals for the "Firefox Mobile Apps 1" initiative==
Line 24: Line 24:


# Implement an app (Kitchen Sink) that showcases the  APIs and features supported by the Web Runtime across supported platforms  (FXOS, Android).   
# Implement an app (Kitchen Sink) that showcases the  APIs and features supported by the Web Runtime across supported platforms  (FXOS, Android).   
# Implement must have APIs on Android
# Implement full life cycle support for packaged apps on Android in Nightly.   
# Implement full life cycle support for packaged apps on Android in Nightly.   
## Install
## Launch
## Update
## Uninstall
# Implement the security/permissions model to enable privileged apps on Android in Nightly.   
# Implement the security/permissions model to enable privileged apps on Android in Nightly.   
# Implement must have APIs on Android
## Contacts API
## Push Notification API
## Web Activities
## mozPay API
## Alarm API [stretch]
# User Experience of using Firefox Apps on Android
# User Experience of using Firefox Apps on Android


===Out-of-Scope This Initiative===
===Out-of-Scope This Initiative===
# Payments on Android: very important. Not a part of "minimum viable product"
# E2E payment flow and testing with a provider is out of scope for Q2 and is part of Q3 2013
# Marketplace App on Android out-of-scope: without a "bundling strategy" there is not market momentum. Potential legal conflicts with Googleplay / Android restrictions
# Marketplace App on Android out-of-scope and in backlog for future projects: no direct market momentum / opportunity yet, potential legal conflicts.
# APK work is out of scope of this project delivery. (Long term goal requiring research and multiple teams, including Marketplace)
# The decision to promote Marketplace from Aurora to Beta or GA will not be made as part of this initiative.


==Duration==
==Duration==
Line 47: Line 58:
{| class="wikitable fullwidth-table"
{| class="wikitable fullwidth-table"
  ! Communication Type !! Mechanism !! Audience
  ! Communication Type !! Mechanism !! Audience
  |-
  |-
  | Announcements || [https://lists.mozilla.org/listinfo/dev-platform tbd] and [https://lists.mozilla.org/listinfo/dev-planning tbd] lists || all
  | General discussion (IRC) || #mobile <br> #FennecFMA || general<br>devs
 
  |-
  |-
  | General discussion || [https://lists.mozilla.org/listinfo/dev-platform tbd] list || devs
  | Regular Meetings
* Product Delivery Leads Weekly (UX, Dev, QA, Product)
** Schedule TBD
** Objective: identify next step and owner for the deliverables in the current sprint, ensure handoffs are made
** Agenda: [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AkUrFYYBXcvAdENjeDdoU1dFZXBmbkFReUU5d2pNUnc#gid=17 Update project tracker]
<br>
* Development Delivery (Triage)
** Thursdays 830 am PST
** Objective: dev team communicates directly on status of dev deliverables / triage bugs (activity as appropriate to project phase)
** Agenda:
*** either [https://wiki.mozilla.org/Mobile/Triage/WebRT Triage bugs]
*** or [https://bugzilla.mozilla.org/showdependencytree.cgi?id=832525&hide_resolved=1 Track project deliverables]
<br>
* Product / Program Leads Review
** Twice Monthly : schedule tbd
** Objective: product and program managers review status
** Agenda:
*** milestone review (template tbd)
*** [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AkUrFYYBXcvAdENjeDdoU1dFZXBmbkFReUU5d2pNUnc#gid=17 Update project tracker]
<br>
* Program Sponsors Review
** Monthly : schedule tbd
** Objective: escalate issues for resolution, celebrate achievements
** Agenda:
*** milestone review & actionable issues (template tbd)
 
  |-
  |-
  | Meetings || meeting time
  | Meeting Logistics
{{conf|conf number}}
* Vidyo: AndroidProduct
* Vidyo: AndroidProduct
* IRC Public: [irc://irc.mozilla.org/ircchannel #openwebapps]
* Audio Dial-In
* IRC Private: [irc://irc.mozilla.org/ircchannel tbd]
** 1-650-903-0800 or + 1-650-215-1282 x92 conf# 99959 (US/INTL)
 
** 1-800-707-2533 (pin 369) conf# 99959 (US toll free)
* Agenda: 
|| Vidyo || Open
|| all
   
  |-
|-
  | Meeting summaries || [[Program Management/ProjectPlanTemplate | this wiki]] || all  
  | Meeting Minutes || [https://etherpad.mozilla.org/android Etherpad] || all  
|}
|}


Line 69: Line 106:
optional - you may want to capture press, blog posts, etc. about the project
optional - you may want to capture press, blog posts, etc. about the project
-->
-->
===Minutes and Progress Reports ===
{| class="wikitable collapsible" style="width: 100%"
! style="background-color: rgb(221, 221, 221);" colspan="2" | 2012
|-
|
* minutes go here
|}


==People==
==People==
list required competencies for people and, once defined, the people working on project. note that not all of these competencies will be required for every project
list required competencies for people and, once defined, the people working on project. note that not all of these competencies will be required for every project
{| class="wikitable fullwidth-table"
{| class="wikitable fullwidth-table"
  | Project Champions ||  
  | Project Sponsors || Rick Fant, Paxton Cooper
|-
| Key Stakeholders / Champions || Karen Rudnitski, Bill Walker, Bill Maggs, Bob Moss, Jonathan Nightengale, Asa Dotzler, Jay Sullivan
  |-  
  |-  
  | Key Stakeholders / Champions ||  
  | Program Management || Caitlin Galimidi, Erin Lancaster
  |-  
  |-  
  | Program Management ||  
  | Product || Vishy Krishnamoorthy
  |-  
  |-  
  | Product ||  
  | UX || Ian Barlow (Advisory: Maria Sandberg, Josh Carpenter)
  |-  
  |-  
  | UX ||  
  | Engineering Lead || Mark Finkle
  |-  
  |-  
  | Engineering || primary devs working on project
  | Engineering Team || Myk Melez, James Hugman, Martyn Haigh, Wes Johnston, Brad Lassey
  |-  
  |-  
  | Other Engineering || subject matter experts contributing to project
  | Engineering Advisory || Brian Smith
  |-  
  |-  
  | Accessibility ||  
  | Incoming Bug Triage || Erin Lancaster
  |-  
  |-  
  | Localization ||  
  | QA || Aaron Train (Contract Resources)
  |-  
  |-  
  | Services ||  
  | Accessibility ||  
  |-  
  |-  
  | Incoming Bug Triage || this may be someone listed elsewhere, the key is to list people who handle triage
  | Localization || Jeff Beatty, Axl Hecht
  |-  
  |-  
  | QA ||  
  | Services || Ryan Tilder
  |-  
  |-  
  | Security ||  
  | Security || Ray Forbes
  |-  
  |-  
  | Privacy ||  
  | Privacy || Alina Hua
  |-  
  |-  
  | Releng ||  
  | RelMan || Alex Keybl
  |-  
  |-  
  | Marketing ||  
  | Marketing || NA
  |-  
  |-  
  | Legal ||  
  | Legal || NA
  |-  
  |-  
|}
|}
== Presentations ==
* [https://wiki.mozilla.org/File:WebRT_mobile_Apps_ReviewV_12.pdf Sponsors Preview]
* [ Kickoff]
<!--
<!--
==Milestones/Iterations/Tasks==
==Milestones/Iterations/Tasks==
Line 132: Line 167:


==References==
==References==
other references, very useful catch all category for existing links and text when cleaning up existing project pages
* [https://wiki.mozilla.org/Mobile/Triage/WebRT Triage Details]
-->
** noming bugs to scope
** prioritizing bugs


== Testimonials ==
== Testimonials ==

Latest revision as of 17:47, 18 April 2013

Initiative: "Firefox Mobile Apps v1"

This initiative is about Apps running on Gecko runtime. It pushes us again toward our goal of bringing open web apps to all the users of the web. Apps for millions of desktop and Mobile FF users in addition to FxOS users.

For Developers, "Firefox Mobile Apps v1" will simply provide a gateway to the global audience and momentum of Firefox Mobile. Developers can begin to grow at the rate of deployment of FxOS, pacing with Android, creating apps with all the powerful features that users expect from native apps; empowered with all the benefits of the open web, supported with the structure and services of a traditional marketplace. It's time to bust open the gates, and share with millions of developers the amazing opportunity we see.

Why "Firefox Mobile Apps v1":

  • Developers - Apps run on multiple platforms; use the same API's, packaging and privileges.
  • Mozilla - gecko runtime consistent on all platforms
  • End-User - my Apps work on all my devices, pay once
  • Operator - remove control points of controlled ecosystems, keep direct to consumer model across all your platforms

Goals for the "Firefox Mobile Apps 1" initiative

  1. Provide working proof of Open Web App principles: the app manifest and app security model
  2. Provide working examples of groundbreaking web APIs on Gecko runtime
  3. Provide delivery vehicle for cross-platform apps (Privileged & Packaged apps on Android, Marketplace)
  4. Provide flexible business model for the delivery of apps by others

Target Audiences

  • Nightly, Fennec 23
  • Aurora Marketplace

Scope: Minimum Viable Product

Parity with FFOS

  1. Implement an app (Kitchen Sink) that showcases the APIs and features supported by the Web Runtime across supported platforms (FXOS, Android).
  2. Implement full life cycle support for packaged apps on Android in Nightly.
    1. Install
    2. Launch
    3. Update
    4. Uninstall
  3. Implement the security/permissions model to enable privileged apps on Android in Nightly.
  4. Implement must have APIs on Android
    1. Contacts API
    2. Push Notification API
    3. Web Activities
    4. mozPay API
    5. Alarm API [stretch]
  5. User Experience of using Firefox Apps on Android

Out-of-Scope This Initiative

  1. E2E payment flow and testing with a provider is out of scope for Q2 and is part of Q3 2013
  2. Marketplace App on Android out-of-scope and in backlog for future projects: no direct market momentum / opportunity yet, potential legal conflicts.
  3. APK work is out of scope of this project delivery. (Long term goal requiring research and multiple teams, including Marketplace)
  4. The decision to promote Marketplace from Aurora to Beta or GA will not be made as part of this initiative.

Duration

March 6, 2013 - September 6, 2013


Communication

Communication Type Mechanism Audience
General discussion (IRC) #mobile
#FennecFMA		 general
devs
Regular Meetings
  • Product Delivery Leads Weekly (UX, Dev, QA, Product)
    • Schedule TBD
    • Objective: identify next step and owner for the deliverables in the current sprint, ensure handoffs are made
    • Agenda: Update project tracker


  • Development Delivery (Triage)
    • Thursdays 830 am PST
    • Objective: dev team communicates directly on status of dev deliverables / triage bugs (activity as appropriate to project phase)
    • Agenda:


  • Product / Program Leads Review
    • Twice Monthly : schedule tbd
    • Objective: product and program managers review status
    • Agenda:


  • Program Sponsors Review
    • Monthly : schedule tbd
    • Objective: escalate issues for resolution, celebrate achievements
    • Agenda:
      • milestone review & actionable issues (template tbd)
Meeting Logistics
  • Vidyo: AndroidProduct
  • Audio Dial-In
    • 1-650-903-0800 or + 1-650-215-1282 x92 conf# 99959 (US/INTL)
    • 1-800-707-2533 (pin 369) conf# 99959 (US toll free)
 Vidyo Open
Meeting Minutes Etherpad all


People

list required competencies for people and, once defined, the people working on project. note that not all of these competencies will be required for every project

Project Sponsors Rick Fant, Paxton Cooper
Key Stakeholders / Champions Karen Rudnitski, Bill Walker, Bill Maggs, Bob Moss, Jonathan Nightengale, Asa Dotzler, Jay Sullivan
Program Management Caitlin Galimidi, Erin Lancaster
Product Vishy Krishnamoorthy
UX Ian Barlow (Advisory: Maria Sandberg, Josh Carpenter)
Engineering Lead Mark Finkle
Engineering Team Myk Melez, James Hugman, Martyn Haigh, Wes Johnston, Brad Lassey
Engineering Advisory Brian Smith
Incoming Bug Triage Erin Lancaster
QA Aaron Train (Contract Resources)
Accessibility
Localization Jeff Beatty, Axl Hecht
Services Ryan Tilder
Security Ray Forbes
Privacy Alina Hua
RelMan Alex Keybl
Marketing NA
Legal NA

Presentations

Retrieved from "https://wiki.mozilla.org/index.php?title=Apps/Project_Plans/Firefox_Mobile_Apps_v1&oldid=647852"