MozillaWiki

Engagement/Developer Engagement/WebAPI Plan: Difference between revisions

< Engagement‎ | Developer Engagement
No edit summary
No edit summary
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Product==
<h1>Developer Engagement plan for WebAPI</h1>
[https://wiki.mozilla.org/WebAPI WebAPI]


<h2>Summary</h2>
WebAPI is an effort by Mozilla to bridge together the gap, and have consistent APIs that will work in all web browsers, no matter the operating system. Specification drafts and implementation prototypes will be available, and it will be submitted to W3C for standardization. Security is a very important factor here, and it will be a mix of existing security measurements (e.g. asking the user for permission, like Geolocation) or coming up with new alternatives to ensure this.
WebAPI is an effort by Mozilla to bridge together the gap, and have consistent APIs that will work in all web browsers, no matter the operating system. Specification drafts and implementation prototypes will be available, and it will be submitted to W3C for standardization. Security is a very important factor here, and it will be a mix of existing security measurements (e.g. asking the user for permission, like Geolocation) or coming up with new alternatives to ensure this.


Line 8: Line 8:
For more information and a current list of WebAPIs being worked on, please see the [https://wiki.mozilla.org/WebAPI WebAPI project page].
For more information and a current list of WebAPIs being worked on, please see the [https://wiki.mozilla.org/WebAPI WebAPI project page].


==Target Audience==
<h2>Product</h2>
[https://wiki.mozilla.org/WebAPI WebAPI]
 
<h2>Target Audience</h2>
Web Developers, App Developers, Users
Web Developers, App Developers, Users


<h2>Deliverables</h2>
<ul>
<li>Frequent blog posts for [http://hacks.mozilla.org/category/webapi/ Mozilla Hacks' WebAPI category].</li>
<li>Giving presentations to get people excited about the possibilities.</li>
<li>More MDN documentation.</li>
<li>Code demos like [https://github.com/robnyman/robnyman.github.com/tree/master/battery Camera API] and porting code documentation to MDN.</li>
<li>Inspiring other web browser and mobile vendors to implement support for these APIs.</li>
<li>Seeing more contributors and progress for [https://github.com/andreasgal/gaia Gaia], Mozilla's user interface for Boot to Gecko.</li>
</ul>


==Deliverables==
<h2>Developer messages</h2>
 
<ul>
    Ongoing list of sites using Persona/BrowserID as login system
<li>The Web is the Platform</li>
 
<li>Using the web layer to access everything an app can do</li>
    Forwarding of possible partnerships to the Persona team and follow-up
</ul>
 
    Simple code examples to follow: https://github.com/codepo8/BrowserID-login-with-PHP
 
    Demo app to show the simplicity of BrowserID integration:http://thewebrocks.com/123done/
 
    Presentations and templates: http://icant.co.uk/talks/londonajax/
 
    Implementation guide: http://mozilla.github.com/browserid-field-guide/
 
    [Ben] we should move all documentation to MDN. (already happening)
 
    coordinate with DanCallahan
 
==Developer messages==
 
    Persona is a simple way to get verified users without having to store their personal data
 
    [Ben] not quite, sites still store their personal data...
 
    Persona keeps the ownership of data in the hand of the end users
 
    [Ben] "ownership?" maybe control?
 
    Persona is the simplest way to allow for personalisation of your data
 
==Speaking materials==
 
    Screencasts, reusable slides available at the Grab Bag:https://wiki.mozilla.org/Engagement/Developer_Engagement/Grab_bag
 
==Speaking opportunities==
 
    Developer conferences
 
    JavaScript conferences
 
    Unconferences
 
    Security conferences
 
    [Ben] YES! More of this.
 
==Next steps==
 
    Integration of persona in the best practice documentation for Evangelism reps


==Individuals responsible==
<h2>Speaking materials</h2>
<ul>
<li>[http://www.slideshare.net/robnyman/tag/apis Presentation slides]</li>
<li>Developer conferences</li>
<li>JavaScript conferences </li>
<li>Unconferences</li>
</ul>


    Within DevEngage (available at https://intranet.mozilla.org/Engagement/Developer_Engagement/ProjectsAndContacts)
<h2>Next steps</h2>
<ul>
<li>More blog posts and documentation for a number of WebAPIs.</li>
<li>More speaking opportunities.</li>
</ul>


    Within the rest of Mozilla (available at https://intranet.mozilla.org/Engagement/Developer_Engagement/ProjectsAndContacts)
<h2>Individuals responsible</h2>
Available in the [https://intranet.mozilla.org/Engagement/Developer_Engagement/ProjectsAndContacts Projects and Contacts page].

Latest revision as of 13:58, 29 March 2012

Developer Engagement plan for WebAPI

Summary

WebAPI is an effort by Mozilla to bridge together the gap, and have consistent APIs that will work in all web browsers, no matter the operating system. Specification drafts and implementation prototypes will be available, and it will be submitted to W3C for standardization. Security is a very important factor here, and it will be a mix of existing security measurements (e.g. asking the user for permission, like Geolocation) or coming up with new alternatives to ensure this.

WebAPI also ties in with Mozilla's Boot to Gecko initiative to ensure all phone functionality is being made available through APIs.

For more information and a current list of WebAPIs being worked on, please see the WebAPI project page.

Product

WebAPI

Target Audience

Web Developers, App Developers, Users

Deliverables

  • Frequent blog posts for Mozilla Hacks' WebAPI category.
  • Giving presentations to get people excited about the possibilities.
  • More MDN documentation.
  • Code demos like Camera API and porting code documentation to MDN.
  • Inspiring other web browser and mobile vendors to implement support for these APIs.
  • Seeing more contributors and progress for Gaia, Mozilla's user interface for Boot to Gecko.

Developer messages

  • The Web is the Platform
  • Using the web layer to access everything an app can do

Speaking materials

Next steps

  • More blog posts and documentation for a number of WebAPIs.
  • More speaking opportunities.

Individuals responsible

Available in the Projects and Contacts page.

Retrieved from "https://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/WebAPI_Plan&oldid=413720"