Firefox OS 1.1 Released, Mozilla Prepares For 2nd Round of Device Launches 76
SmartAboutThings writes "Mozilla has officially introduced the first update to its mobile Firefox OS. The very first update to Firefox OS adds some important new features, performance improvements and additional language support. Some of the most important changes include MMS support, Push Notifications API, Contact Management enhancements, Firefox browser downloads, Keyboard improvements and much more. In a separate announcement, Mozilla also said that new launches of Firefox OS smartphones will begin soon with more devices and in more markets around the world."
Re:Didn't know it launched. (Score:3, Insightful)
The answer is simple: It's not ready. I mean, it's probably ready for release as production software, but as a phone OS, it doesn't appear to be ready to be exposed to the majority of the world. For example, 1.1 just got MMS capabilities. Based on just this alone, 1.0 would have just been laughed out of the market.
Their current target, I suspect, are enthusiasts and very, very early adopters. It's the people who don't really care that their phone is missing half of the basic features found on other phones. It's people who are more interested in developing applications (add-ons?) for the OS than for people who want to use the phone.
I expect you'll see them ramp up their marketing efforts as the software becomes more feature-complete. Until then, it's just not ready for end users.
Re:Websites wont render (Score:5, Insightful)
Another issue is we have IE 6 back again in style.
Its name this decade is called webkit. [pcmag.com]. If the web server detects it is a mobile device it outputs Webkit specific (chrome/Safari) CSS that is not W3C compliant.
Complain and the answer is webkit owns 95% of the market so go fsck yourself and buy a droid or iphone like everyone else. Kind of like we do not support Netscape anymore in 2003 even though you used Konsqueror or Firefox .4.
Drives me nuts to see the same developers who praise webkit and use non W3C compliant html5test.com to base their opinions then go out and bash IE 6 and who write code on the mobile end that wont work Windows Phone/Windows 8 either.