Mozilla would like to introduce WebAPI with the goal to provide a basic HTML5 phone experience within 3 to 6 months.
The current situation
Where we are today, there’s a clear distinction between the Open Web and native APIs and how things have to be built. As many developers are aware of, we need consistent APIs across web browsers, operating systems and devices to be able to build something for the world, not just a specific device or vendor. We need a way to take the web to the next step.
What is WebAPI?
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.
In the nearest timeframe we are looking into building:
- Dialer: Telephony & Messaging API, Contacts API
- Address Book: Contacts API
- SMS: Telephony & Messaging API, Contacts API
- Camera: Camera API, Filesystem API
- Gallery: Filesystem API (could possibly be FileReader & FileWriter in conjunction)
- Settings: Device Status API, Settings API
- Games: Accelerometer API, Mouse Lock API
- Maps: Geolocation API, Contacts API
We know that there are so many talented people out there with great input, so please contribute through any of these means:
- Keep track of the WebAPI project page.
- The WebAPI mailing list.
- IRC: irc.mozilla.org in the #webapi room.
- Start working by going to bug 67392 and look at the dependent bugs to find the ones that need help.
We are also hiring several full time engineers for working with WebAPI. Read the job description and apply.
About Robert Nyman [Editor emeritus]