505
edits
Apps/Roadmap: Difference between revisions
Undo revision 392082 by Rags (talk)
| Line 1: | Line 1: | ||
<p><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> | <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> | ||
</p> | </p> | ||
<h1> Why is Mozilla doing this? </h1> | <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>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>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>< | </p><p><include image here> | ||
</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>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>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>< | </p><p><include image here> | ||
</p><p>This poses challenges for both developers and users. | </p><p>This poses challenges for both developers and users. | ||
</p><p>Some of the challenges for developers include: | </p><p>Some of the challenges for developers include: | ||
| Line 21: | Line 21: | ||
</li><li> Lack of personalization in the App discovery process. | </li><li> Lack of personalization in the App discovery process. | ||
</li></ul> | </li></ul> | ||
<p><br /> | |||
</p><p><br /> | |||
</p><p><br /> | |||
</p> | |||
<h1> What is Mozilla doing? </h1> | <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. | <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. | ||