Apps/Architecture: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
== Architecture ==
= Apps Program Software Architecture =


=== Web Apps Purchase Flow ===
== Program Goals ==


[[Image:Webappspurchaseflow.png|200px200px]]
* 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


Legend
* Provide Users with:
#Client possibly initiates a browserID session
** an open Apps ecosystem that lets them shop at the App store of their choice
##Client goes to the marketplace, and a browserid login is presented
** a means to back up and manage their Apps from multiple Stores across multiple devices
#Client goes to the marketplace
#Client initiates an install off an app
##Navigator.mozApps.install
#App is installed, user opens app
#Twitter app is launched
#Twitter app verifies the receipt that was presented.
#Apps Sync occurs ad-hoc manner, still unsure as to the schedule.


<br>
* Provide App Stores
** a well-documented API and access to our Apps in the Cloud offering


The basics behind open webapps architecture is to allow for HTML5 apps to flourish.  To do that a few things infrastructure pieces need to be in place.
== Architectural Goals ==
# Firefox needs to support navigator.mozApps
# HTML5 App Managmement in case no OWA Extension is installed.
# Store needs to support both the issuing of payment receipts as well as the verification of receipt information
# Apps Need to be able to run from the desktop or in browser.
# The navigator.mozApps is the javascript object that will manage installing / removing apps
# Iframes are used to manage the communication channel between the Application Repo and the Dashboard
# Application Sync is managed through a separate API.


=== Architectural Links ===
* 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


* [http://kix.in/2011/12/15/behind-the-mozilla-apps-developer-preview/ Apps and Architectural Overview]
== Deliverables ==
* [https://tarekziade.wordpress.com/2011/12/14/mozilla-apps-server-side/ Server Architecture]
 
* navigator.mozApps API (owner: anant)
* navigator.mozApps.mgmt API (owner: anant)
* navigator.id API (owner: benadida)
* navigator.mozPay API (owner: andreas)
* App manifest specification (owner: anant)
* App security model (owner: ladamski)

Revision as of 17:33, 14 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 means to back up and manage their Apps from multiple Stores across multiple devices
  • Provide App Stores
    • a well-documented API and access to our Apps in the Cloud offering

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

Deliverables

  • navigator.mozApps API (owner: anant)
  • navigator.mozApps.mgmt API (owner: anant)
  • navigator.id API (owner: benadida)
  • navigator.mozPay API (owner: andreas)
  • App manifest specification (owner: anant)
  • App security model (owner: ladamski)
Retrieved from "https://wiki.mozilla.org/index.php?title=Apps/Architecture&oldid=460845"