Engagement/Developer Engagement/WebAPI Plan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 2: Line 2:


<h2>Summary</h2>
<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.


<p>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 [https://wiki.mozilla.org/B2G Boot to Gecko initiative] to ensure all phone functionality is being made available through APIs.
</p>
 
<p>WebAPI also ties in with Mozilla's <a href="https://wiki.mozilla.org/B2G">Boot to Gecko initiative</a> to ensure all phone functionality is being made available through APIs.
</p>
 
<p>For more information and a current list of WebAPIs being worked on, please see the <a href="https://wiki.mozilla.org/WebAPI">WebAPI project page</a>.
</p>


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


<h2>Product</h2>
<h2>Product</h2>
<p><a href="https://wiki.mozilla.org/WebAPI">WebAPI</a>
[https://wiki.mozilla.org/WebAPI WebAPI]
</p>
 


<h2>Target Audience</h2>
<h2>Target Audience</h2>
<p>Web Developers, App Developers, Users
Web Developers, App Developers, Users
</p>
 


<h2>Deliverables</h2>
<h2>Deliverables</h2>
Ongoing list of sites using Persona/BrowserID as login system
<ul>
 
<li>Frequent blog posts for [http://hacks.mozilla.org/category/webapi/ Mozilla Hacks' WebAPI category].</li>
Forwarding of possible partnerships to the Persona team and follow-up
<li>Giving presentations to get people excited about the possibilities.</li>
 
<li>More MDN documentation.</li>
Simple code examples to follow: https://github.com/codepo8/BrowserID-login-with-PHP
<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>
Demo app to show the simplicity of BrowserID integration:http://thewebrocks.com/123done/
<li>Seeing more contributors and progress for [https://github.com/andreasgal/gaia Gaia], Mozilla's user interface for Boot to Gecko.</li>
 
</ul>
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
 


<h2>Developer messages</h2>
<h2>Developer messages</h2>
Persona is a simple way to get verified users without having to store their personal data
<ul>
[Ben] not quite, sites still store their personal data...
<li>The Web is the Platform</li>
Persona keeps the ownership of data in the hand of the end users
<li>Using the web layer to access everything an app can do</li>
[Ben] "ownership?" maybe control?
</ul>
Persona is the simplest way to allow for personalisation of your data
 


<h2>Speaking materials</h2>
<h2>Speaking materials</h2>
Screencasts, reusable slides available at the Grab Bag:https://wiki.mozilla.ment/Grab_bag
<ul>
 
<li>[http://www.slideshare.net/robnyman/tag/apis Presentation slides]</li>
Developer conferences
<li>Developer conferences</li>
 
<li>JavaScript conferences </li>
JavaScript conferences  
<li>Unconferences</li>
 
</ul>
Unconferences
 
Security conferences
 
[Ben] YES! More of this.


<h2>Next steps</h2>
<h2>Next steps</h2>
 
<ul>
Integration of persona in the best practice documentation for Evangelism reps
<li>More blog posts and documentation for a number of WebAPIs.</li>
 
<li>More speaking opportunities.</li>
</ul>


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

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.allizom.org/index.php?title=Engagement/Developer_Engagement/WebAPI_Plan&oldid=413720"