Engagement/Developer Engagement/WebAPI Plan: Difference between revisions

=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 [https://wiki.mozilla.org/B2G 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 [https://wiki.mozilla.org/WebAPI WebAPI project page].

[https://wiki.mozilla.org/WebAPI WebAPI]

    Ongoing list of sites using Persona/BrowserID as login system

    Forwarding of possible partnerships to the Persona team and follow-up

    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

    Persona is a simple way to get verified users without having to store their personal data

    Persona keeps the ownership of data in the hand of the end users

    [Ben] YES! More of this.

 

 

 

 

    Within the rest of Mozilla (available at https://intranet.mozilla.org/Engagement/Developer_Engagement/ProjectsAndContacts)