Apps/Project Plans/Firefox Mobile Apps v1: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
=Initiative: "Firefox Mobile Apps v1"= | =Initiative: "Firefox Mobile Apps v1"= | ||
This initiative is about Apps running on Gecko. 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 300 million desktop users, '''25 million+ Mobile FF users''', and millions of 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 6: | Line 6: | ||
'''Why "Firefox Mobile Apps v1":'''<br> | '''Why "Firefox Mobile Apps v1":'''<br> | ||
*Developers - Apps run on multiple platforms; use the same API's, packaging and privileges. | *Developers - Apps run on multiple platforms; use the same API's, packaging and privileges. | ||
*Mozilla - gecko 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 point, keep direct to consumer model | ||
| Line 12: | Line 12: | ||
==Goals for the "Firefox Mobile Apps 1" initiative== | ==Goals for the "Firefox Mobile Apps 1" initiative== | ||
# Provide working proof of Open Web App principles: the app manifest as security model | # Provide working proof of Open Web App principles: the app manifest as security model | ||
# Provide working examples of groundbreaking web APIs on Gecko | # Provide working examples of groundbreaking web APIs on Gecko runtime | ||
# Provide delivery vehicle for cross-platform apps (Privileged & Packaged apps on Android, Marketplace) | # Provide delivery vehicle for cross-platform apps (Privileged & Packaged apps on Android, Marketplace) | ||
# Provide flexible business model for the delivery of apps by others (Payments) | # Provide flexible business model for the delivery of apps by others (Payments) | ||
| Line 23: | Line 23: | ||
Parity with FFOS | Parity with FFOS | ||
# Implement an app (Kitchen Sink) that showcases the APIs and features supported by the | # 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 | # Implement must have APIs on Android | ||
# Implement support for packaged | # Implement full life cycle support for packaged apps on Android in Nightly. | ||
# | # Implement the security/permissions model to enable privileged apps on Android in Nightly. | ||
# User Experience of using Firefox Apps on Android | # User Experience of using Firefox Apps on Android | ||
Revision as of 17:07, 19 February 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 300 million desktop users, 25 million+ Mobile FF users, and millions of 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 point, keep direct to consumer model
Goals for the "Firefox Mobile Apps 1" initiative
- Provide working proof of Open Web App principles: the app manifest as security model
- Provide working examples of groundbreaking web APIs on Gecko runtime
- Provide delivery vehicle for cross-platform apps (Privileged & Packaged apps on Android, Marketplace)
- Provide flexible business model for the delivery of apps by others (Payments)
Target Audiences
- Nightly, Fennec 26
- Aurora Marketplace
Scope: Minimum Viable Product
Parity with FFOS
- 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 the security/permissions model to enable privileged apps on Android in Nightly.
- User Experience of using Firefox Apps on Android
Out-of-Scope This Initiative
- Payments on Android: very important. Not a part of "minimum viable product"
Duration
March 6, 2013 - September 6, 2013
Communication
| Communication Type | Mechanism | Audience |
|---|---|---|
| Announcements | tbd and tbd lists | all |
| General discussion | tbd list | devs |
| Meetings | meeting time
|
all |
| Meeting summaries | this wiki | all |
Minutes and Progress Reports
| 2012 | |
|---|---|
| |
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 Champions | |
| Key Stakeholders / Champions | |
| Program Management | |
| Product | |
| UX | |
| Engineering | primary devs working on project |
| Other Engineering | subject matter experts contributing to project |
| Accessibility | |
| Localization | |
| Services | |
| Incoming Bug Triage | this may be someone listed elsewhere, the key is to list people who handle triage |
| QA | |
| Security | |
| Privacy | |
| Releng | |
| Marketing | |
| Legal |
Testimonials
- "Three of the four FFOS value propositions talk about open standards and portability. To deliver on them, we need our runtime to work across platforms" - Vishy Krishnamoorthy, Product Manager, Web Runtime
- "Firefox OS will produce an implementation of these new Web standards to free mobile platforms from the encumbrances of the rules and restrictions of existing proprietary platforms."
- "Users and developers aren’t locked in to one platform, so they can access their info and use apps across multiple devices."
- "OEMs and operators will be able to provide content and services across their entire device portfolio, regardless of OS."