Apps/Roadmap: Difference between revisions

<p><span class="fck_mw_template"><span class="fck_mw_template">{{RoadmapSummaryfckLR|icon=Tempicon.pngfckLR|pagelocation=Apps/RoadmapfckLR|pagetitle=Apps 2012 RoadmapfckLR|owner=Ragavan SrinivasanfckLR|updated=January 2012fckLR|status=In progressfckLR|description=Mozilla is working on making the Web the premier platform and marketplace for the next generation of Apps. We plan to do this by establishing a user-centric Apps ecosystem that provides freedom, choice and opportunity for users and developers. This document outlines the current strategy and direction for the Mozilla Apps project through 2012.fckLR}}</span></span>

<h1> Why is Mozilla doing this? </h1>

<p>Apps have become the predominant way users interact with content, especially on mobile devices. Most Apps today are built using platform specific tools and languages. They are distributed using tightly controlled and locked down App Stores. They only run on specific device and OS combinations. A few dominant market players have assembled these various pieces into integrated App ecosystems that pose some big challenges for users and developers. Before we dig into the specific problems, let's take a quick look at what constitutes an App ecosystem and who the major players are in the market.

</p><p>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:

</p><p>&lt;img src="/images/c/cf/Apps-Ecosystem.png" _fck_mw_filename="Apps-Ecosystem.png" alt="" /&gt;

</p><p>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.  

</p><p>Here's a simple representation of how some of the bigger players in the industry are implementing their own versions of an App ecosystem.  

</p><p>&lt;img src="/images/c/cf/Apps-Ecosystem.png" _fck_mw_filename="Apps-Ecosystem.png" alt="" /&gt;

</p><p>This poses challenges for both developers and users.  

</p><p>Some of the challenges for developers include:

<ul><li> Increased investment in building, maintaining, distributing and marketing separate Apps for each native platform.

</li><li> Loss of control over key aspects such as customer relationships, update frequencies, technology choices etc.

</li><li> Fragmentation of customer base

<p>Some of the challenges for users include:

<ul><li> Inability to use their Apps in a heterogeneous environment at home/work/school etc.

</li><li> Getting shut out of App experiences due to their device/platform choices.

</li><li> Lack of personalization in the App discovery process.

<h1> What is Mozilla doing? </h1>

<p>Mozilla believes that the web is *the* platform and the entire web should be your marketplace. To this end, we are building products and services across three different threads.

<h2> Web Platform </h2>

<p>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:

<ul><li> Taking existing web rendering engines (Gecko/Webkit) as a base.

</li><li> Adding native OS integration features for things such as installing, launching, managing Apps.

</li><li> Adding additional capabilities such as device APIs, permissioning models, improving offline execution of Apps etc.

</li><li> Integrating services directly into the run-time such as Identity, Sync, Notifications etc.

<p>By basing WebRT off existing web rendering engines, we also automatically get all the awesome work (such as performance improvements) for "free".  

</p><p>For a detailed description of WebRT and its roadmap, see the WebRT page.

<h2> Marketplace </h2>

<p>Mozilla is building a Marketplace for Apps that work across desktops, phones and tablets. Through this Marketplace, developers will be able to distribute and monetize their Apps. Users will be able to get, install and use their Apps across all of their devices, regardless of the underlying device/OS platforms. This Marketplace will also be the single destination where users can find both cross-platform Apps as well as Firefox extensions.

</p><p>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.

</p><p>The Marketplace roadmap can be found here.

<h2> Services </h2>

<p>A few fundamental services sit at the heart of the Apps project that allow us to deliver on key developer and user propositions.

<ul><li> Identity and digital receipts

</li><li> Payments

</li><li> App Sync, backup and recovery

<h3> Identity and digital receipts </h3>

<p>Mozilla's BrowserID project is an easy way to sign into websites. Instead of making up a hard-to-remember username and password for each site, BrowserID lets you use your email address and a single password to sign in to any site that supports it. We are integrating BrowserID with Apps in the following ways:

<ul><li> Users will log into the Marketplace using BrowserID.

</li><li> Every App (free or paid) they install from the Marketplace will include a receipt that is tied to their BrowserID.

</li><li> Users will log into their App Dashboard (a cloud based interface to all their Apps) using BrowserID.

<p>More information about digital receipts can be found here.

<h3> Payments </h3>

<p>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.

</p><p>More details about our Payments solutions and the roadmap can be found in the Marketplace roadmap.

<h3> App Sync, backup and recovery </h3>