I always wished for myself and for the larger web community a 'Rock solid web based Open' Mobile Platform. And it is happening fast.
Also let's not forget the big failure of the over hyped Palm WebOS.
Many said - it was too early; not ready for the market. I too agreed then. :)
Lets hope Firefox has good design patterns and moves agile.
Couple of things I wish everyone knows -
1. Are all the System level API's ready? Telephone API, Sensor API's et al. It looks to me, its under prototype and design, what's the current stage?
2. Can this leverage WebGL and all HTML5 features?
Are there any other programming API's?
For 1. and 3., here's the Web API: https://wiki.mozilla.org/WebAPI
Should answer all your questions, I hope
I only wish FirefoxOS devices were around to have been considered for our retarded "give every child a tablet" program that's underway in Turkey, especially given the rumors that Mozilla is shooting for the cheap end of the market. As expected, the tablets for the program are being marketed as a toy.
ed: the above post is not meant to be sarcastic. dirty utopian hippie = optimistic in a good way
I had a WebOS phone and despite loving the beautiful UI and it being ahead of iOS in many ways like notifications and task switching, I dumped it. HTML5 killed the user experience. I need fast, responsive apps that only Android and iOS can deliver.
There's no way I'd ever go back to generic, laggy, HTML5 Apps.
Besides, Mozilla is not trying to tie down anyone to it's platform, because the platform is basically the Web, which is open to everyone. There are many things which distinguish it from other platforms like you can host your "apps", which are nothing more than simple websites, on your own site and not necessarily Mozilla's MarketPlace. Mozilla is working hard to reduce the memory footprint and make the apps responsive and by the time it comes out, I think it's going to have a really good performance.
 - https://bugzilla.mozilla.org/show_bug.cgi?id=797189
You can track the implementation here: https://wiki.mozilla.org/WebAPI
I for one am looking forward to it, though the lack of apps compared to the other two dominant ecosystems will be a problem.
If you want to contribute back, Google has been good about accepting patches into its AOSP project. For patches they won't accept, there's always CyanogenMod.
"JS engines are pretty fast" Good enough for simple text based apps and casual games, yes. Modern 3D games, not by a long shot. Native code, NDK, or Java under HotSpot are the only decent options creating for modern responsive 3D games.
i think that firefox OS will do to the smartphone ecosystem what github did to open source contribution revival. not having to touch the OS guts, and just scripting against some additional APIs is a huge win for simplification to the whole hacking process.
the mozilla-specific stuff will start proprietary like android, but all of their work is submitted for standards adoption and is almost certainly needed in one form or another.
Says the cert is ok, but my firefox complains:
hacks.mozilla.org uses an invalid security certificate.
The certificate is only valid for tbpl.mozilla.org
(Error code: ssl_error_bad_cert_domain)
This is due to TLS SNI, which allows different certs to be returned based on the hostname requested. SNI is supported by all major browsers on all major platforms, with 1 significant exception: WinXP+IE does not support SNI (WinXP+Firefox/Opera/Chrome are all fine for many versions, WinVista/7+IE are both fine). I think certain (older) Android platforms have a problem with this too.
SNI is really awesome because the web hosting company doesn't have to allocate separate IP addresses for multiple sites to have proper SSL support. It makes HTTPS hosting simpler and cheaper. The only significant downside is issues like this, where a user's browser doesn't support it... hence over time, issues like this should shrink.
If you're still on WinXP+IE, you're likely to start running into more and more problems in the next couple years (and not just due to SNI).
Edit: Don't quote me, been a while since studying site certificates.
I even tried
$ openssl s_client -connect hacks.mozilla.org:443
0 s:/serialNumber=I1oZ-yurbFWiPu/xP8HIzW3f9mApQvMv/C=US/ST=California/L=Mountain View/O=Mozilla Corporation/OU=IT/CN=tbpl.mozilla.org
i:/C=US/O=GeoTrust, Inc./CN=GeoTrust SSL CA
1 s:/C=US/O=GeoTrust, Inc./CN=GeoTrust SSL CA
i:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
2 s:/C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
i:/C=US/O=Equifax/OU=Equifax Secure Certificate Authority
subject=/serialNumber=I1oZ-yurbFWiPu/xP8HIzW3f9mApQvMv/C=US/ST=California/L=Mountain View/O=Mozilla Corporation/OU=IT/CN=tbpl.mozilla.org
issuer=/C=US/O=GeoTrust, Inc./CN=GeoTrust SSL CA
WinXP + any version of IE does not support TLS SNI... even though it does support TLSv1.0, it doesn't support the SNI extension. Supported in Vista and 7, though.
Chrome, Firefox, and Opera (on any platform) all support TLSv1.0, with or without SNI.
Works for me, btw.
Since Mozilla actually has the health of the web as their main mission, they have a role catering to markets that others will neglect.
Mozilla should focus on building a competitive browser. At the end of the day, I want a responsive fast phone, like the iPhone or Galaxy S3, not some dog slow HTML5 monstrosity.
My browser runs fine on my current phone, and MozillaOS is even closer to the metal. Both WebGL and "normal" web apps look good, and they've just started. http://www.youtube.com/watch?feature=player_detailpage&v...