Apps/Architecture: Difference between revisions
< Apps
Jump to navigation
Jump to search
BillWalker (talk | contribs) No edit summary |
BillWalker (talk | contribs) |
||
| Line 26: | Line 26: | ||
* [https://developer.mozilla.org/en-US/docs/Apps/Apps_JavaScript_API#Management_API_%28navigator.mozApps.mgmt.*%29 navigator.mozApps API] (owner: anant) | * [https://developer.mozilla.org/en-US/docs/Apps/Apps_JavaScript_API#Management_API_%28navigator.mozApps.mgmt.*%29 navigator.mozApps API] (owner: anant) | ||
* [https://developer.mozilla.org/en-US/docs/DOM/navigator.id navigator.id API] (owner: benadida) | * [https://developer.mozilla.org/en-US/docs/DOM/navigator.id navigator.id API] (owner: benadida) | ||
* [https:// | * [https://docs.google.com/document/d/1NLKbHVPQXa9uvDBC3cfgOD7sIrtIxi0qDoXMQrxcCsI/edit navigator.mozPay API] (owner: andreas) | ||
* [http://mozilla.github.com/webapps-spec/ App manifest specification] (owner: anant) | * [http://mozilla.github.com/webapps-spec/ App manifest specification] (owner: anant) | ||
* [https://wiki.mozilla.org/Apps/Security Apps security model] (owner: ladamski) | * [https://wiki.mozilla.org/Apps/Security Apps security model] (owner: ladamski) | ||
Revision as of 00:23, 15 August 2012
Apps Program Software Architecture
Program Goals
- Provide Developers with:
- a consistent App runtime environment that makes their Apps feel like natives, not tourists, on every platform they care about
- a consistent payment infrastructure for Apps available at our Marketplace
- Provide Users with:
- an open Apps ecosystem that lets them shop at the App store of their choice
- a robust App runtime environment that makes Apps feel like natives, not tourists on every device
- a means to back up and manage their Apps from multiple Stores across multiple devices
- Provide App Stores
- a well-documented API for installing and managing Apps
- access to the same cloud-based services for App management that our Marketplace uses
Architectural Goals
- Provide well-designed API's for App installation, App management, and App payments
- Conceal uninteresting platform dependencies while providing access to crucial platform-specific features
- Provide access to multiple payment providers through a single, unified API
Deliverables
- navigator.mozApps API (owner: anant)
- navigator.id API (owner: benadida)
- navigator.mozPay API (owner: andreas)
- App manifest specification (owner: anant)
- Apps security model (owner: ladamski)
- App packaging specification (owner: sicking)
Problematic questions
- How can we help developers cope with the one-app-per-origin restriction?
- How can achieve a consistent Identity sol'n in the face of Firefox OS carrier and operator constraints?
- How can achieve a consistent payments API in the face of Firefox OS carrier and operator constraints?