Confirmed users, Bureaucrats and Sysops emeriti
2,974
edits
Apps/Roadmap: Difference between revisions
Jump to navigation
Jump to search
m
Mark as outdated
No edit summary |
m (Mark as outdated) |
||
| (6 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{outdated}} | |||
<section begin="summary" />{{RoadmapSummary | <section begin="summary" />{{RoadmapSummary | ||
|icon=Tempicon.png | |icon=Tempicon.png | ||
| Line 13: | Line 15: | ||
At a high level, an App ecosystem is an end-to-end, integrated combination of hardware, software and services that aims at providing compelling user experiences while severely restricting user and developer choice. A typical App ecosystem looks like this: | At a high level, an App ecosystem is an end-to-end, integrated combination of hardware, software and services that aims at providing compelling user experiences while severely restricting user and developer choice. A typical App ecosystem looks like this: | ||
[[File:Apps-Ecosystem.png]] | |||
At the lowest level, there is some hardware upon which runs a usually proprietary OS / runtime. On top of this runtime exists a store/marketplace which is the exclusive distribution channel for Apps, for tht ecosystem. The provider also offers a suite of compelling services that are also tied pretty closely to this ecosystem. Such services may be both user and developer services. The ecosystem also comes with a suite of compelling default applications, but in addition, provides an attractive array of other Apps that are available within the ecosystem. | At the lowest level, there is some hardware upon which runs a usually proprietary OS / runtime. On top of this runtime exists a store/marketplace which is the exclusive distribution channel for Apps, for tht ecosystem. The provider also offers a suite of compelling services that are also tied pretty closely to this ecosystem. Such services may be both user and developer services. The ecosystem also comes with a suite of compelling default applications, but in addition, provides an attractive array of other Apps that are available within the ecosystem. | ||
Here's a simple representation of how some of the bigger players in the industry are implementing their own versions of an App ecosystem. | Here's a simple representation of how some of the bigger players in the industry are implementing their own versions of an App ecosystem. | ||
[[File:Apps-Ecosystem-Market.png]] | |||
This poses challenges for both developers and users. | This poses challenges for both developers and users. | ||
| Line 35: | Line 37: | ||
== Web Platform == | == Web Platform == | ||
The main goal for our work in this area is to ensure that the Web Platform is an excellent run-time for Apps. This entails, at a high level, building a cross platform Web Runtime (we're calling this WebRT) by: | The main goal for our work in this area is to ensure that the Web Platform is an excellent run-time for Apps. This entails, at a high level, building a cross platform Web Runtime (we're calling this [[Apps/WebRT]]) by: | ||
* Taking existing web rendering engines (Gecko/Webkit) as a base. | * Taking existing web rendering engines (Gecko/Webkit) as a base. | ||
| Line 43: | Line 45: | ||
By basing WebRT off existing web rendering engines, we also automatically get all the awesome work (such as performance improvements) for "free". | By basing WebRT off existing web rendering engines, we also automatically get all the awesome work (such as performance improvements) for "free". | ||
For a detailed description of WebRT and its roadmap, see the WebRT page. | For a detailed description of WebRT and its roadmap, see the [[Apps/WebRT]] page. | ||
== Marketplace == | == Marketplace == | ||
| Line 49: | Line 51: | ||
We are basing a lot of the infrastructure and processes off the existing Add-ons site (addons.mozilla.org) which gives us an incredible advantage in time to market. | We are basing a lot of the infrastructure and processes off the existing Add-ons site (addons.mozilla.org) which gives us an incredible advantage in time to market. | ||
The Marketplace roadmap can be found here. | The Marketplace roadmap can be found [https://wiki.mozilla.org/AMO:Roadmap/2012 here]. | ||
== Services == | == Services == | ||
| Line 65: | Line 67: | ||
* Users will log into their App Dashboard (a cloud based interface to all their Apps) using BrowserID. | * Users will log into their App Dashboard (a cloud based interface to all their Apps) using BrowserID. | ||
More information about digital receipts can be found here. | More information about digital receipts can be found [https://wiki.mozilla.org/Apps/WebApplicationReceipt here]. | ||
=== Payments === | === Payments === | ||
We are providing some fundamental building blocks in both WebRT and the Marketplace, which together, will enable a simplified, 1-click payment experience. Using our payment solution, developers will be able to enable 1-click experiences for common transactions such as buying a premium App, in-app payments, subscriptions and more. Users will have the ability to choose from a variety of payment methods as the year progresses. | We are providing some fundamental building blocks in both WebRT and the Marketplace, which together, will enable a simplified, 1-click payment experience. Using our payment solution, developers will be able to enable 1-click experiences for common transactions such as buying a premium App, in-app payments, subscriptions and more. Users will have the ability to choose from a variety of payment methods as the year progresses. | ||
More details about our Payments solutions and the roadmap can be found in the Marketplace roadmap. | More details about our Payments solutions and the roadmap can be found in the [https://wiki.mozilla.org/AMO:Roadmap/2012 Marketplace roadmap]. | ||
=== App Sync, backup and recovery === | === App Sync, backup and recovery === | ||