Apps/Architecture

Architecture

Legend

1. Client possibly initiates a browserID session
   1. Client goes to the marketplace, and a browserid login is presented
2. Client goes to the marketplace
3. Client initiates an install off an app
   1. Navigator.mozApps.install
4. App is installed, user opens app
5. Twitter app is launched
6. Twitter app verifies the receipt that was presented.
7. Apps Sync occurs ad-hoc manner, still unsure as to the schedule.

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.

1. Firefox needs to support navigator.mozApps
2. HTML5 App Managmement in case no OWA Extension is installed.
3. Store needs to support both the issuing of payment receipts as well as the verification of receipt information
4. Apps Need to be able to run from the desktop or in browser.
5. The navigator.mozApps is the javascript object that will manage installing / removing apps
6. Iframes are used to manage the communication channel between the Application Repo and the Dashboard
7. Application Sync is managed through a separate API.