Apps/Overview: Difference between revisions

Jump to navigation Jump to search

Apps/Overview (view source)

Revision as of 18:50, 18 August 2011

103 bytes added ,  18 August 2011
no edit summary
No edit summary
Line 1: Line 1:
= Web Application Architecture =
Web applications are universal applications.  The run on any device.  They use standard technology that works on desktop PCs, smartphones, and tablets.  They can be installed on devices automatically when users authorize their devices, and are personalized so that users keep their preferences and data with them wherever they go.


== Universal Applications ==
== Mozilla-provided products to support Web Applications ==


Web Applications can run on any device.  They use standard technology that works on desktop PCs, smartphones, and tablets.  They can be installed on devices automatically when users authorize their devices, and are personalized so that users keep their preferences and data with them wherever they go.
=== App Storage in the Cloud ===


== Personalized Application Collections ==
Mozilla will implement and host a generic "application cloud" service, which can be freely called by any store, dashboard, or application.  It provides a full implementation of the Application Client API in HTML5, and runs on any modern browser.  This service can run purely locally (with no user login), or can store all of the user's applications on the server, for access across all of a user's devices.  This service is visible to users through an easy-to-use "application dashboard", which always has their applications ready for use.


The user's collection of web applications is part of their personal data.  Web browsers and devices maintain the collection on the user's own hardware.  In the Firefox architecture, the list of installed web applications is part of the user's profile data.
This service will store the user's applications and any receipts needed for proof-of-purchase; at some near point it will also include per-application storage for user data, allowing applications to give users a consistent experience across devices.
 
Mozilla offers an application sync service that makes it quick and easy for users to keep their application collections in sync across their devices.  This synchronization includes all the infrastructure needed to support paid applications, and the list of in-application purchases that the user has made.


Read More:
Read More:
* [https://developer.mozilla.org/en/OpenWebApps Web Client Application API]
* [https://developer.mozilla.org/en/OpenWebApps Web Client Application API]
* Application Dashboard - link needed
* App Cloud Service - need link
* Application Sync Service - link needed


== Authenticated Applications ==
=== User Identity Service ===


Applications can optionally be "authenticated," which means that the application is stored on the user's devices with a targeted identity.  The BrowserID system allows the application to verify this identity at startup.  When the application is copied to another device, the identity flows with it, allowing the user to launch the application and get back to their cloud-based state with no per-application login step required.
Mozilla has proposed a decentralized identity system that allows applications to verify a user's identity.  Mozilla will host HTML5-based APIs for browsers that do not have native support for this system, and will provide robust and scalable identity verification services for domains that do not participate directly in the system.


Read More:
Read More:
* [http://identity.mozilla.com BrowserID]
* [http://identity.mozilla.com BrowserID]
* Browser ID Directed Identity Assertion - link needed


== Paid Applications and In-App Purchases ==
=== Firefox: The Best Browser Runtime for Applications ===
 
Firefox will provide the best browser-based runtime for applications.  It will have the richest set of APIs, the best user experience of navigating and running applications, and the safest and easiest-to-use user controls.  It communicates with the application cloud to keep the user's application choices and data always up-to-date.
 
Mobile Firefox allows web applications to run full screen, with rich user interactions (touch, orientation, motion) and access to device APIs.  Desktop Firefox is fast and efficient, and allows applications to run in tabs (full or pinned), windows, or full screen.  All Firefox runtimes have a robust but easy-to-use permission system that makes it easy to provide rich APIs to trusted applications, or applications from a trusted source, while safely viewing untrusted content.
 
Read More:
* [https://wiki.mozilla.org/WebAPI Mozilla's WebAPI project]
* [http://people.mozilla.com/~faaborg/files/projects/apps/discovery-i2.png Web Apps on Firefox Home Tab]
* [http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/4b8892e0d277b14b/1c1ff493776249b9?lnk=raot#1c1ff493776249b9 dev-platform thread on advanced permissions]
* UI mockup of application permissions - need link


The Open Web Applications system supports paid applications ranging from free-and-self-published to paid, web-store distribution.  Applications can be sold by multiple stores, or sold directly by the publisher.  Paid applications are built on top the Authenticated Application system.
=== Firefox: The Best Runtime for Native Applications ===


When a user purchases an application from a store, the store synthesizes a Web Application Receipt with a purchase type of <tt>application</tt> and installs the application with the receipt in the <tt>appReceipt</tt> property of the application's installData.  The application later retrieves this receipt and verifies it, proving that the receipt came from a trusted store.  The application may then verifies the identity embedded in the receipt using BrowserID; when the application is launched through the <tt>launch</tt> method of Web Application Client API, a BrowserID Directed Identity Assertion is enabled to allow the application to verify the receipt's embedded user identity without a popup.  The application is free to use cookies, usernames, or other techniques for creating a user session, but is encouraged to user BrowserID to remove the need for a login screen.
The capabilities provided by a web browser can also be separated and turned into a standalone application.  These applications can interact with operating systems in a more "native" way; for example, they can have their own icon in a task bar or dock, act as a target for document-opening requests, and be copied between devices with a drag-and-drop to a file server.


When a user performs an in-application purchase, the store synthesizes a Web Application Receipt with a purchase type of <tt>application-payment</tt> and adds the receipt to the <tt>purchaseReceipts</tt> property of the application's installData.  The application may retrieve this list later and verify the receipts contained in the list; this data can be used to enable features on the server or the client as the application sees fit.
The Mozilla platform can support this both by running a "no-label" version of the user's installed Firefox (as in WebRunner), or by creating a custom executable for a target operating system (as in Chromeless).  The creation of native runtimes for web applications could be performed on the client, or on the server.  Custom executables can be distributed through native application stores or offered directly for download by developers.


Note that security concerns require that receipt verification be performed on a server under the developer's control; the web platform does not, and likely will never, support hardware-locked application licensing.  For more discussion of how offline verification be handled, see Offline Verification of Purchased Apps.
On Android, we can provide a more "native"-seeming experience through rich browser-based APIs; where appropriate, however, we can create or interact with native executables.


Read More:
Read More:
* [[Apps/WebApplicationReceipt|Web Application Receipt]]
* [http://www.salsitasoft.com/webrunner/ WebRunner]
* Offline Verification of Purchased Apps - link needed
* [http://mozillalabs.com/chromeless/ Chromeless]
 
=== The Mozilla Application Marketplace: The Most Complete, Trusted Directory of Web Apps ===


== Application Activities ==
Mozilla operates an Application Marketplace, which is a safe, fast, fun place for users to find web applications, and for developers to reach their customers.  It is a reference implementation for a web application store, which developers can download and set up on their own domains.  It is implemented as a web application, and is easily reachable from the Firefox browser or from any other web browser on mobile or desktop.  It understands the characteristics of major web browser platforms and helps users configure their devices to get the best experience.


Applications can expose "Activities," which are an application-to-application communication system.  This system allows an application (or website) to request access to a user's preferred service, and for a message to flow between the application and the service.
The Marketplace is a payment processor, providing a place for developers to list their applications and for users to purchase them.  It also supports in-app purchasing (by itself being an application), allowing developers to offer digital goods to their users after install.  The Marketplace also allows developers to list applications that are free, or that are sold by the developer on their own site.


Use cases for this feature include link sharing, contact lists, personal profile data, payment processing, travel planning, and media preferences.
The Marketplace understands the complexity of delivering web applications to multiple platforms.  It provides a features-and-capabilities system that shows users apps that can run on their platform, and suggests available platforms for the user's device if a more capable platform could provide a better experience.


Read More:
Read More:
* [https://github.com/mozilla/openwebapps/blob/master/docs/ACTIVITIES.md Activities specification] (in-progress)
* Application Marketplace - link needed
* [http://dev.chromium.org/developers/design-documents/webintentsapi Web Intents] (related work by Google Chrome team; conversations with this team are ongoing)
* Mozilla Marketplace App - link needed


= Running Web Applications in a Browser =
== Standardization and API Development to Support Applications ==


Web browsers can run applications in a tab, a window, or full-screen.  The tab can be a traditional tab or a pinned tab that is always present in every browser window.
Mozilla provides APIs, and works with other browser vendors to define standards, that enhance the web application ecosystem


Web browsers can provide different default permissions to web applications, allowing them to access data and device capabilities that are not allowed to websites be default.  They can, optionally, provide greater capabilities to web applications that were installed from a trusted source (which assumes that a review and revocation system is in place).
=== Well-defined application metadata ===


In the Firefox architecture, web applications can run in tabs, pinned tabs, or full screen.  The Firefox permissions mechanism will be enhanced to provide more capabilities to web applications, subject to the user's control.
Mozilla is working with other vendors to define standard application metadata, to allow applications to describe themselves to browser runtimes.


Read More:
Read More:
* [http://people.mozilla.com/~faaborg/files/projects/apps/discovery-i2.png Web Apps on Firefox Home Tab]
* [https://developer.mozilla.org/en/OpenWebApps/The_Manifest Application Manifests]
* [http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/4b8892e0d277b14b/1c1ff493776249b9?lnk=raot#1c1ff493776249b9 dev-platform thread on advanced permissions]
 
* UI mockup of application permissions - need link
=== Client-side APIs for web applications ===


= Running Web Applications Natively =
Mozilla has proposed, and hosts an HTML5 implementation of, an application storage API.


The capabilities provided by a web browser can also be separated and turned into a standalone application. These applications can interact with operating systems in a more "native" way; for example, they can have their own icon in a task bar or dock, act as a target for document-opening requests, and be copied between devices with a drag-and-drop to a file server.
Read More:
* [https://developer.mozilla.org/en/OpenWebApps Web Client Application API]


The Mozilla platform can support this both in a "custom invocation of Firefox" mode (as the WebRunner project does today), or through statically linking the XULRunner libraries with an executable (as the [http://mozillalabs.com/chromeless/ Chromeless] project does).  The creation of native runtimes for web applications could be performed on the client, or on the server.
=== Decentralized identity ===


The PhoneGap project provides this capability for many smartphone platforms.
Mozilla has proposed, and hosts an HTML5 implementation of, a decentralized identity verification system.


Read More:
Read More:
* [http://www.salsitasoft.com/webrunner/ WebRunner]
* [http://identity.mozilla.com BrowserID]
* [http://mozillalabs.com/chromeless/ Chromeless]
 
=== Web Application Receipts ===
 
Mozilla proposes a standard web application receipt format, to allow proof-of-purchase claims to travel from stores to applications using user-centric storage.  This allows users to log into a new device and receive all their applications, including paid content, with no additional steps required.


= The Mozilla Application Marketplace =
Read More:
* [[Apps/WebApplicationReceipt|Web Application Receipt]]


The Application Marketplace is a web site, operated by Mozilla, that provides a safe, fast, fun place for users to find web applications, and for developers to reach their customers.  It is a reference implementation for a web application store, which developers can download and set up on their own domains.
=== Web Application Activities ===


The Marketplace supports both paid applications and in-app purchasing.  The in-app purchase function is supported by the Mozilla Marketplace application, which implements the In-App Purchase activity.
Applications can expose "Activities," which are an application-to-application communication system.  This system allows an application (or website) to request access to a user's preferred service, and for a message to flow between the application and the service.


The Marketplace understands the complexity of delivering web applications to multiple platforms.  It provides a features-and-capabilities system that shows users apps that can run on their platform, and suggests available platforms for the user's device if a more capable platform could provide a better experience.
Use cases for this feature include link sharing, social graphs or contact lists, personal profile data, payment processing, travel planning, and media preferences.


Read More:
Read More:
* Application Marketplace - link needed
* [https://github.com/mozilla/openwebapps/blob/master/docs/ACTIVITIES.md Activities specification] (in-progress)
* Mozilla Marketplace App - link needed
* [http://dev.chromium.org/developers/design-documents/webintentsapi Web Intents] (related work by Google Chrome team; conversations with this team are ongoing)
Mhanson
348

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/341232"

Navigation menu