Just over a week ago, I left Barcelona and Mobile World Congress 2014, where Mozilla had a huge third year with Firefox OS.
We announced the $25 Firefox OS smartphone with Spreadtrum Communications, targeting retail channels in emerging markets, and attracting operator interest to boot. This is an upgrade for those channels at about the same price as the feature phones selling there today. (Yes, $25 is the target end-user price.)
We showed the Firefox OS smartphone portfolio growing upward too, with more and higher-end devices from existing and new OEM partners. Peter Bright’s piece for Ars Technica is excellent and has nice pictures of all the new devices.
We also were pleased to relay the good news about official PhoneGap/Cordova support for Firefox OS.
We were above the fold for the third year in a row in Monday’s MWC daily.
(Check out the whole MWC 2014 photo set on MozillaEU’s Flickr.)
As I’ve noted before, our success in attracting partners is due in part to our ability to innovate and standardize the heretofore-missing APIs needed to build fully-capable smartphones and other devices purely from web standards. To uphold tradition, here is another update to my progress reports from last year and from 2012.
First, and not yet a historical curiosity: the still-open tracking bug asking for “New” Web APIs, filed at the dawn of B2G by Andreas Gal.
Next, links for “Really-New” APIs, most making progress in standards bodies:
- DataStore (via the W3C SysApps WG)
- Web Audio
- Promises
- SimplePush (note conformance issues, to be fixed)
- Desktop notification API
- WebNFC, upcoming in Firefox OS 1.4
- Inter-app communication API
- TCP socket API
- WebRTC, including
getUserMedia
support - SPDY Push
Yet more APIs, some new enough that they are not ready for standardization:
- Multiple-SIM support (DSDS)
- FileSystem support (note that the spec is not finished yet)
- Porting more APIs to Web Workers
- Gamepad API in Gecko 28; not yet in Firefox OS
- Network Information API (Firefox OS bug)
- Keyboard API
Finally, the lists of new APIs in Firefox OS 1.1, 1.2, and 1.3:
This is how the web evolves: by implementors championing and testing extensions, with emerging consensus if at all possible, else in a pref-enabled or certified-app sandbox if there’s no better way. We thank colleagues at W3C and elsewhere who are collaborating with us to uplift the Web to include APIs for all the modern mobile device sensors and features. We invite all parties working on similar systems not yet aligned with the emerging standards to join us.
/be
The inter-app communication link is incorrect.
@Josh: Fixed, thanks!
/be
The booth is *amazingly* cool.
Please extend Javascript capabilities to allow built-in type declarations of parameters. To any naysayers, you could always declare type Object if you don’t want a specific type.
Thomas: I worked on ES4. You must have read this thread already, no?
https://esdiscuss.org/topic/optional-strong-typing
See in particular
https://esdiscuss.org/topic/optional-strong-typing#content-12
https://esdiscuss.org/topic/optional-strong-typing#content-16
/be
The SimplePush link is either wrong or extremely unhelpful.
@Caspy7: oops, fixed. Thanks!
/be
Where do things stand with ES6 / Harmony? I was especially looking forward to proper modules & classes… any chance of those being supported across a few browsers within the next couple years?
ES6 is doing well, being implemented by top browsers, finalized as a spec this calendar year. ES7 is proceeding in parallel, with parts implemented in top browsers as well. Check out the talk I gave at Fluent 2014:
https://www.youtube.com/watch?v=aZqhRICne_M
Slides here:
https://www.slideshare.net/BrendanEich/fluent14
/be