Engagement/Developer Engagement/AppsPlan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Blanked the page)
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
<h1>Developer Engagement Plan for the Mozilla Apps Initiative </h1>
 
<h2>[ Goals]</h2>
<ul>
<li>Support Apps Business Development in securing 100 premier apps for the App Store Beta </li>
<li>Broad Reach Activities that result in 1000 apps in process during the beta timeline.</li>
<li>Increase broad industry awareness of Mozilla as a leader in Standards Based Development Technology.</li>
</ul>
<hr /><br />
<p>Mozilla Apps Developer Engagement Mission <br />
<br />
One of the great potential values of standards based applications is the
potential ubiquity of deployment options from a single code base. <br />
<br />
Using Mozilla app infrastructure, apps can deploy across platforms from a single code base.<br />
<br />
Each of <span id="OBJ_PREFIX_DWT2712_com_zimbra_date" class="Object">today</span>’s
developer community segments has a different set of learning needs and pain
points.<br />
<br />
Current Phone and Tablet Developers<br />
<br />
- Android &#160;Developers<br />
- iOS<br />
- Google Apps and Others<br />
<br />
Existing “Apps” developers all have a common set of pain points.<br />
<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Each potential consumer audience is isolated to a different App Store
and each App Store represents a specific device platform. Therefore reaching the
widest possible set of customers means using multiple development technologies
and languages and deploying to multiple stores. Or using some even less standard
proprietary tool, cross platform compiler, etc. and trying to build you app once
but get great results on multiple platforms.) <br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Apps Developers are at the mercy of the App stores than the sell in.
App listing placement, search optimization, etc. - in fat the whole findability
process is different in the different stores.<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Each App Store customer base has different buying and usage patterns so
effective monetization strategies differ based on app specific market segment. &#160;<br />
<br />
Web Developers<br />
<br />
&#160;&#160; &#160; ♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Server Side Web Developers<br />
<br />
Web developers who work in PHP, Python, Ruby etc are used to writing HTML etc,
but there are many new technologies to be learned (Workers, Sockets, Etc.) Also,
many of them have not previously worked with client / server interactions (AJAX)
<br />
<br />
In addition, they have not previously had to think about their web apps
including an off-line experience. Therefore HTML5 and “Web Run Time” specific
guidance should be usefully to them.<br />
<br />
&#160;&#160; &#160; ♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;HTML/JS Developers<br />
<br />
Some developers have been writing HTML/JavaScript code and server-side
interactions. These developers are a bit ahead of the curve but all of the HTML5
and off-line technologies will be new to them as well.<br />
<br />
&#160;&#160; &#160; ♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Microsoft Web Developers<br />
<br />
Conventional ASP.NET developers have not had to learn much about Web Application
Technologies and, relative to Apps building efforts will need a great deal of
foundational learning to come up to speed.<br />
<br />
<br />
Desktop Developers<br />
<br />
♦&#160;&#160;&#160;&#160;&#160; Windows <br />
♦&#160;&#160;&#160;&#160;&#160; Mac<br />
♦&#160; &#160; &#160; Linux<br />
<br />
Though much of the apparent interest in “Apps” development is focused on mobile
devices Standards Based Application development has interesting prospects for
the desktop as well. <br />
&#160;<br />
Developing an application that runs on the desktop is traditionally been a
compromise.<br />
<br />
You could:<br />
<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Choose to support only one desktop platform and ignore the other
potential markets.<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Develop the same application 2 or 3 times, once on each platform that
you want to support. <br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Develop your application in Java and test across multiple OSes. (Though
most developers find this to be an arduous process that often yields sub-optimal
results.)<br />
<br />
Some of the broad developer guidance that Mozilla needs to provide.<br />
<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Application Architectures for HTML5 Applications <br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Sometimes Connected Patterns and Practices<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Advanced Engineering Practices<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Multi Platform and Form Factor User Experiences<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Hardware Access<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Performance<br />
<br />
Planned Developer Engagement Activities:<br />
<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Web Apps Weekly Podcast <br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Series of Event’s in a Box<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Apps Patterns &amp; Practices Tutorial Series<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Post Beta Apps Developer Conference Tour<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;<br />
Proposed:<br />
&#160;<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Games Specific Tutorial Series<br />
♦&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;BrowserID Tutorial Series<br />
♦ &#160; &#160;&#160; &#160; 1-3 reference applications representing unique application scenarios.<br />
♦ &#160;&#160; &#160; &#160; Several “Event in a Box” on HTML5 apps for use by Mozillians
Everywhere.<br />
<br />
<br />
Engagement Goals&#160;: <br />
<br />
♦&#160;&#160;&#160;&#160;&#160;&#160; To inform the developer community at large in regards to Mozilla’s
industry leadership as an HTML5 innovator.<br />
♦ &#160;&#160;&#160;&#160;&#160; To fill a gap in broad developer understanding as to what can actually
be done with HTML5 and how HTML5 drastically changes web development.<br />
♦&#160;&#160;&#160;&#160;&#160;&#160; Catalyze a vibrant development ecosystem for building and monetizing
HTML5 Apps<br />
<br />
</p>
<hr /><br />
<p>All Developer Engagement folks are starting to seed interest in the Apps ecosystem in anticipation of the developer preview.
</p>
<hr />
<h2>[ Team Activities ]</h2>
<table width="100%" border="1" style="border-collapse:collapse">
  <tr><td width="10%">Date</td><td width="90%">Activity</td></tr>
  <tr><td>Ongoing</td><td>Apps specific blogging at MisfitGeek.com</td></tr>
  <tr><td>TBD</td><td>Weekly Apps Newsletter starting with the Dev Preview Release</td></tr>
  <tr><td>Week of 11/28/2011</td><td>Apps World Conference - Panel on the challenges of multi platform apps development</td></tr>
  <tr><td>12/05/2011</td><td>Contingent documentation resource begins.</td></tr>
  <tr><td>Week of 12/05/2011</td><td>Launching “Apps” Focused Developer Podcast at www.DevRadio.com</td></tr>
  <tr><td>Week of 12/05/2011</td><td>Launch article series on Standards based Application Architectures</td></tr>
  <tr><td>Week of 12/12/2011</td><td>On site in MV to deliver feedback and planning data to engineering and PM (gathered from discussions with some 35 profiled potential store contributors) </td></tr>
  <tr><td>02/04-05/2012</td><td>FOSDEM</td></tr>
</table>

Latest revision as of 23:27, 1 February 2012

Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Engagement/Developer_Engagement/AppsPlan&oldid=393225"