Apps/Architecture: Difference between revisions

| rowspan=3 style="background:#DDDDDD" | App Definition

| rowspan=3 style="background:#DDDDDD" width="50%" |An App is described by its Manifest. The manifest contains user-facing metadata, including descriptions and icons. The manifest also enumerates the protected API's to which the App requests access. This information is used by the App Security Model to control access to privileged API's at run time.  

|-

|[https://wiki.mozilla.org/Apps/PackagingProposal App packaging specification]

| style="background:#DDDDDD" | Many services in the Apps ecosystem require user authentication (e.g., the Marketplace itself, many of the Apps, the Cloud-based services). We can offer our users a much better overall experience if we (1) build a coherent Identity solution into all our services and (2) encourage App developers to do the same.  

|[https://developer.mozilla.org/en-US/docs/DOM/navigator.id navigator.id API]

|-

|Marketplace

| rowspan=3 style="background:#DDDDDD" |Payment

| rowspan=3 style="background:#DDDDDD" |We will offer our developers (1) a centralized way to price and manage paid Apps, including integration with multiple billing providers, as needed; (2) a unified Javascipt DOM API to facilitate In-app payments from Users for digital goods within Apps. We will offer users (1) a unified, trustworthy experience of purchasing and seeking refunds for paid Apps; (2) a consistent, trustworthy experience of making In-App payments  

|-

|[https://wiki.mozilla.org/Apps/WebApplicationReceipt App receipt specification]

| rowspan=3 style="background:#DDDDDD" | Runtime

| rowspan=3 style="background:#DDDDDD" | We will provide a Web Runtime for Apps that makes HTML5-based Apps feel exactly like native applications on every device. This includes access to privileged device API's (i. e., geolocation, contacts, SMS) and native OS features (menus, drag-and-drop).

|-

|-

|}