Apps/Architecture: Difference between revisions
< Apps
Jump to navigation
Jump to search
BillWalker (talk | contribs) |
BillWalker (talk | contribs) No edit summary |
||
| Line 25: | Line 25: | ||
{| | {| | ||
! Category | |||
! Description | |||
| | ! Architect | ||
| | ! Tech Lead | ||
|App Management | |- | ||
| rowspan=2 | App Management | |||
|[https://developer.mozilla.org/en-US/docs/Apps/Apps_JavaScript_API#Management_API_%28 navigator.mozApps.mgmt] | |[https://developer.mozilla.org/en-US/docs/Apps/Apps_JavaScript_API#Management_API_%28 navigator.mozApps.mgmt] | ||
|anant | |||
|- | |||
|[http://mozilla.github.com/webapps-spec/ App manifest specification] | |||
|anant | |anant | ||
|- | |- | ||
|Identity | |Identity | ||
|[https://developer.mozilla.org/en-US/docs/DOM/navigator.id navigator.id API] | |[https://developer.mozilla.org/en-US/docs/DOM/navigator.id navigator.id API] | ||
|benadida | |||
|benadida | |benadida | ||
|- | |- | ||
| Line 40: | Line 45: | ||
|[https://docs.google.com/document/d/1NLKbHVPQXa9uvDBC3cfgOD7sIrtIxi0qDoXMQrxcCsI/edit navigator.mozPay API] | |[https://docs.google.com/document/d/1NLKbHVPQXa9uvDBC3cfgOD7sIrtIxi0qDoXMQrxcCsI/edit navigator.mozPay API] | ||
|andreas | |andreas | ||
|- | |- | ||
|Security Model | |Security Model | ||
|[https://wiki.mozilla.org/Apps/Security Apps security model] | |[https://wiki.mozilla.org/Apps/Security Apps security model] | ||
|ladamski | |ladamski | ||
|sicking | |||
|- | |- | ||
|Packaging | |Packaging | ||
|[https://wiki.mozilla.org/Apps/PackagingProposal App packaging specification] | |[https://wiki.mozilla.org/Apps/PackagingProposal App packaging specification] | ||
|sicking | |||
|sicking | |sicking | ||
|- | |- | ||
|Cloud services | |Cloud services | ||
|[http://docs.services.mozilla.com/aitc/lifeofanapp.html Apps in the Cloud design] | |[http://docs.services.mozilla.com/aitc/lifeofanapp.html Apps in the Cloud design] | ||
|anant | |||
|anant | |anant | ||
|- | |- | ||
| | | rowspan=3 | Runtime | ||
| | |Web Runtime (WebRT) for Android | ||
|not sure | |not sure | ||
|mfinkle | |||
|- | |- | ||
|Web Runtime (WebRT) for Mac OS, Windows, Linux | |||
|Web Runtime (WebRT) for | |||
|not sure | |not sure | ||
|myk | |||
|- | |- | ||
| | |[https://wiki.mozilla.org/Gaia/System/Apps Apps support on Firefox OS] | ||
|not sure | |not sure | ||
|cjones | |||
|} | |} | ||
Revision as of 21:15, 16 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
| Category | Description | Architect | Tech Lead |
|---|---|---|---|
| App Management | navigator.mozApps.mgmt | anant | |
| App manifest specification | anant | ||
| Identity | navigator.id API | benadida | benadida |
| Payment | navigator.mozPay API | andreas | |
| Security Model | Apps security model | ladamski | sicking |
| Packaging | App packaging specification | sicking | sicking |
| Cloud services | Apps in the Cloud design | anant | anant |
| Runtime | Web Runtime (WebRT) for Android | not sure | mfinkle |
| Web Runtime (WebRT) for Mac OS, Windows, Linux | not sure | myk | |
| Apps support on Firefox OS | not sure | cjones |
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?