Slashdot Mirror


Mozilla OS Looking Grown Up On Its Own Developer Phone

An anonymous reader writes "It's no secret that Mozilla has been working on a mobile OS. Previously codenamed Boot2Gecko, the project focused on a purely HTML5 based system that worked in many ways like current mobile devices. As the project grew into Mozilla OS, the company has laid out a partnership with ZTE that will have real world devices in certain markets early next year. Testing for this OS had previously consisted of a compiled ROM that would be flashed over a handful of Android devices. Now, Mozilla has moved into full fledged product evaluation mode with their own custom developer phone."

72 of 114 comments (clear)

  1. Three cheers for Mozilla by pr0nbot · · Score: 5, Insightful

    I suppose there will be a degree of negativity about boot to gecko, along the lines of "they've already lost" and "they should focus on fixing the browser".

    Personally, I wish them every success. Firefox has been great, and the idea of a phone OS built by a non-profit whose only agenda revolves around standards, privacy, user control, openness and general sanity will be a refreshing change from the likes of Apple, Google, and Microsoft. It actually seems to be happening, too, unlike so many other projects we hear about.

    (But if you want some negativity - given that they're primarily funded by Google, and presumably don't have a massive patent war chest, they'll probably be sunk if they ever get anywhere. Time to donate!)

    1. Re:Three cheers for Mozilla by vagabond_gr · · Score: 4, Informative

      From mozilla.org:

      The Mozilla Foundation is a non-profit organization that promotes openness, innovation and participation on the Internet.

    2. Re:Three cheers for Mozilla by OpenDoors · · Score: 2, Informative

      Mozilla Foundation (non-profit) owns Mozilla Corporation (for-profit) which handles the development of Firefox, Thunderbird, Firefox OS etc.

    3. Re:Three cheers for Mozilla by gl4ss · · Score: 4, Funny

      From mozilla.org:

      The Mozilla Foundation is a non-profit organization that promotes openness, innovation and participation on the Internet.

      riaa is a non-profit too, just saying. they got plenty of employees and are in constant need of money though.

      --
      world was created 5 seconds before this post as it is.
    4. Re:Three cheers for Mozilla by jbolden · · Score: 5, Informative

      Foundation handles the development. Corporation pays people and collects revenue. This is an artifact of tax law in the USA, Mozilla is still run by Foundation which is non profit.

    5. Re:Three cheers for Mozilla by lister+king+of+smeg · · Score: 2

      I hope that is easily expandable via plug-ins much like their browser. Don't want a web app to have access to something just disable that with appblock plus. wan't to kill the comic sans font from apps just install comic sans remover plugin. But since it is all browser based will how will app writers not have costumers simply copy the page source for the HTML (presumably a extended version of five) CSS and JavaScript? And what advantage will this have when all of their apps will be usable by everyone else (being web app runing in a browser) but not vis versa(native apps)? aren't the people already realizing web apps where a bad idea already like facebook saying that it was a bad move and switching back to a native app? they will have to work on some native apps even Google has realized that and is working on running native code on ChromeOS another browser as a OS implementation. How will it do with out flash will Mozilla finally relent and use the pepper api even just as an optional plugin? what about audio and vidio codex on my pc it gets them from vlc on my linux box and windows media player and vlc on my windows box who will provide them on the firefox mobile os since they seem to have funny ideas about what codex should be the standard.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    6. Re:Three cheers for Mozilla by Your.Master · · Score: 1

      Mozilla Foundation is non-profit. Mozilla Corporation is for-profit. The Foundation owns the Corporation. It's a sort of legal workaround as I understand it. I'd say it's closer to the truth that Mozilla is non-profit since the for-profit is owned by the non-profit.

    7. Re:Three cheers for Mozilla by Anonymous Coward · · Score: 1

      It sounds more like a technicality to me.

    8. Re:Three cheers for Mozilla by Anonymous Coward · · Score: 1

      Yup, I've worked for non-profits before and was looking forward to cashing my checks with "famous non-profit name here" on them but for legal/tax reasons they had a little shell company for payroll so it said "xyz staffing" or some crap instead.

    9. Re:Three cheers for Mozilla by loufoque · · Score: 1

      You realize the point of a foundation is to remove taxes?
      The foundation exists because of financial reasons beneficial to mozilla corporation, not to "promote the web" or whatever.

    10. Re:Three cheers for Mozilla by thelukester · · Score: 1

      Sorry buddy, but Reality is not Negativity. There are millions upon millions of iPhones and Android devices running with lower specs than 256 MB memory and a 700 MHz CPU, and they are very usable and responsive, EXCEPT for web browsing! So if Mozilla wants to fix the problem with low end smartphones, they need to fix their browser first.

      Then they can focus on creating a streamlined smartphone OS based on Native apps, not CPU hogging HTML5/CSS. Mozilla is living in a dream world, where they don't grok the real problem with low-end smartphones are battery life and performance. CSS was never intended for GPU acceleration and Javascript requires a heavy VM that sucks away CPU cycles and drains battery life, not to mention 10-100x slower than native.

      Here's an idea, take WebOS or Android,make the GUI fully hardware accelerated, rewrite all the basic apps to run Native code, remove any HTML 5 / VM kruff . Now add your new state of the art Firefox XXXXX for web browsing, and you'd have something that I'd want to run on a low-end smartphone.

    11. Re:Three cheers for Mozilla by AmberBlackCat · · Score: 1

      Or a tax loophole.

    12. Re:Three cheers for Mozilla by Mythmon · · Score: 1

      Do you realize that the foundation came first? The corporation was created later. The IRS said that Mozilla needed to pay taxes, but could not because it was a non-profit. So the corporation was created to handle the money.

    13. Re:Three cheers for Mozilla by loufoque · · Score: 1

      Yes, at first they tried to evade all taxes, but couldn't, which is why they were forced to create a corporation in the end.

    14. Re:Three cheers for Mozilla by lsatenstein · · Score: 1

      I think it is great that Mozilla has done this. Since it is in HTML5, and they are there first, and using the logic available with HTML5, the phone should be free from patent claims coming from the big three.

      --
      Leslie Satenstein Montreal Quebec Canada
  2. Browser Based OS by OpenDoors · · Score: 4, Insightful

    I really doubt that this is good direction. It's the greatest lock-down of all time. Every web-app (Google Docs etc) is behind the greatest DRM of all time, just like Blizzards Diablo 3.

    The only reason this haven't ben discussed on Slashdot before is because it's been Google that has been developing fully browser based OS, and Google fanboys have de-routed every intelligent discussion about the merits of Chrome/Firefox OS.

    Sorry, but in my opinion we must stop this development here and keep our native open and closed source apps. You can't even disassemble browser apps, all you have is the front-end. At least with Windows and MS apps I know they are going to stay around and work when I need them.

    1. Re:Browser Based OS by Anonymous Coward · · Score: 3, Insightful

      HTML5 applications can work offline. They already have interfaces for sandboxed filesystems and built in SQL DBs. Granted, apps that have an online component(most of them probably) don't have to release the source for their server software. That is the case with native apps as well though. I suggest you spare some time to review the HTML5 specs. It's actually a pretty good development platform. You may even like it

    2. Re:Browser Based OS by Celarent+Darii · · Score: 4, Informative

      You can't even disassemble browser apps, all you have is the front-end.

      Say that again? You just look at the source code, the javascript and it's all there. Maybe not like you want it, but there is nothing intrinsic to browser apps that make them a sort of DRM. If it is written in HTML5, you can look at the code if they make it available - in fact in some ways you can do 'Show Source' in a browser easier than many native apps. Even Google Apps you can do 'Show source' in your browser. In a certain way the web is far more open that native apps, which are painfully difficult to disassemble from the binary.

      The only real problem are the requests from the server - true, they don't often release server software source. But often this is mostly connection to some database. While this can be problematic for open source, it is not intrinsically so. Most web apps can also be written to work offline.

    3. Re:Browser Based OS by cmdr_tofu · · Score: 3, Interesting

      Yeah but you cannot review the code that lives on providers cloud of webservers. For instance althouhg you can view the source to google mail's html and javascript in your browser (and even muck with it using the right ff plugins), there is not any practical way for you to deploy your own gmail on your own server.

      A lot of webaps are open source, but if you dont even control the application when its runnign in. I don't know if I have a side, but there is a big shift. For instance with Microsoft office, Microsoft cannot "track you" using their software. Of course I like OpenOffice more than Microsoft, and even though GoogleApps makes collaboration over the Internet a lot easier, it does mean google can track everyone who is using their software. This is definitely something new and a different kind of evil that Microsoft probably never thought of in the early days of poor connectivity.

      An open source alternative to googleApps that anyone can deploy on their own PlugPC (or other device) server could allow us to transition to web-based apps and protect against being ruled by vendors. I kind of see free software as inevitably becoming better than proprietary software over time.

    4. Re:Browser Based OS by Alef · · Score: 1

      Technologically, you don't really have to choose between a locked down cloud and native only apps. It would be perfectly possible to have independent cloud storage services working with web based applications storing data in open and standardized formats, letting you choose where to store your data and which applications to use to work with it. The problem is it's usually not in the interest of individual corporations to open up in this way -- it's easier to develop when you control the whole stack, and it makes it harder for customers to leave.

    5. Re:Browser Based OS by drinkypoo · · Score: 2

      The only reason this haven't ben discussed on Slashdot before is because it's been Google that has been developing fully browser based OS, and Google fanboys have de-routed every intelligent discussion about the merits of Chrome/Firefox OS.

      You, sir, are either a troll or insufficiently familiar with the debate here to make such declarative statements. I have debated at length here on slashdot the lack of merit of having an operating system which boots directly into a browser, and my comments have been relatively well-received. Comment invalidated.

      You can't even disassemble browser apps, all you have is the front-end.

      What does that even mean? It's a lot of nonsense. HTML5 has offline apps. You will be able to browse through these apps, twiddle their sources, et cetera. Indeed, you will have more power to do this than with smartphone apps, which are compiled; you will be able to fiddle with the HTML and JS. You either have no idea what you're talking about or, again, you're some kind of troll.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Browser Based OS by afgam28 · · Score: 2

      Sorry, but in my opinion we must stop this development here and keep our native open and closed source apps. You can't even disassemble browser apps, all you have is the front-end. At least with Windows and MS apps I know they are going to stay around and work when I need them.

      From a technical point of view, there's nothing stopping open source apps from staying open after they've moved onto "the cloud".

      Imagine you bought server time, let's say an EC2 instance from AWS. Then you load it up with a webmail server, a storage server, and an open-source Google Docs-style word processor. You could use this EC2 instance to serve you mail, music and documents from anywhere using any device. And you could do it using 100% open source software.

      This is what open source software could look like in the post PC era, but it's a shame that most open source advocates are so vehemently anti-cloud that they will not help make this possible.

    7. Re:Browser Based OS by AmberBlackCat · · Score: 1

      No, that person is absolutely right. This will happen any time you say something Google doesn't like.

    8. Re:Browser Based OS by Lennie · · Score: 1

      Firefox OS does not depend on the network, the whole system support "View Source" just like any webpage. There is no closed source server component.

      All the server projects Mozilla does have actually are all open source projects, like:

      http://en.wikipedia.org/wiki/Firefox_Sync (bookmarks, history, password syncing)

      https://github.com/mozilla/browserid Project To allow you to login with only an emil address to sites in similair fashion as OpenID/OAuth, SAML , but is probably easier to use for mere mortals and allows for proper privacy and which does not make you dependenant on for example Facebook.

      So you can run their software on your own server.

      Heck, I am running their Sync software on my own server and it works.

      --
      New things are always on the horizon
    9. Re:Browser Based OS by Lennie · · Score: 1

      That is exactly what the Unhosted project is all about:

      http://www.unhosted.org/

      "Unhosted web apps do not harvest user data onto a server. For both users and web developers this has many advantages over the more server-centric web 2.0 architecture that's typically used in web-based Software-as-a-Service (hosted web apps), and in same-origin AJAX apps (so called "one-page apps") that use one tightly coupled backend."

      "Because unhosted web apps don't force the use of their servers on you, you can sync your data yourself, to a place that you trust. Dutch universities already run such a 'remote storage' service, specifically designed to be compatible with unhosted web apps."

      "With your data living outside the app, you can switch back and forth between apps without even exporting and importing. Better than data liberation, this is personal data freedom brought to the web."

      There is even a W3C specification:
      http://www.w3.org/community/unhosted/wiki/RemoteStorage

      --
      New things are always on the horizon
    10. Re:Browser Based OS by drinkypoo · · Score: 1

      No, that person is absolutely right. This will happen any time you say something Google doesn't like.

      Welcome to the world of groupthink, citizen. Unhappy thoughts are double-plus unacceptable to the bore collective.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  3. didn't they already announce something like this? by gl4ss · · Score: 3, Informative

    didn't they already announce something like this?

    http://www.wired.com/gadgetlab/2012/07/mozilla-dumps-boot2gecko-name-firefox-os-tktktk/

    the picture in this article sure as fuck looks like a reflashed android though! pretty full fledged, but that's zte for you..

    --
    world was created 5 seconds before this post as it is.
  4. Re:didn't they already announce something like thi by MichaelSmith · · Score: 1

    my question is: how easy is it to get on good side of FAA (or your country's fly-or-no-fly agency)...?

    It sounds a lot like WebOS to me.

  5. WebOS by dutchwhizzman · · Score: 2

    How is this different in architecture from HP's WebOS?

    --
    I was promised a flying car. Where is my flying car?
    1. Re:WebOS by muon-catalyzed · · Score: 2

      iOS KOed WebOS because native iOS apps crushed and humiliated web apps. FireFoxOS is just another ring entrant to get knocked down.

    2. Re:WebOS by lbenes · · Score: 2

      How is this different in architecture from HP's WebOS?

      In Principle they are the same idea, except WebOS uses the lean webkit engine to render the desktop, while Firefox OS, uses the resource hogging Geko engine.

      As a former Palm Pre Plus and Firefox user, I am a poster child as to why this is a terrible idea. I switched from Firefox to the webkit based Chrome because it was the was so much leaner and faster. I also had to leave my webkit based Pre, for a NATIVE powered iPhone. And while I dearly miss WebOS's beautiful and intuitive UI, I do not miss the dog slow performance one bit.

      Why doesn't Mozilla invest their limited resources on making a lean browser that can compete with Chrome?

    3. Re:WebOS by MSG · · Score: 1

      WebOS's failure in the market had nothing to do with native iOS apps. WebOS and its applications were great, but the implementation was awful. The OS wasn't stable, so the phones weren't reliable.

      For usability, I was disappointed when I moved to an Android phone. However, having my alarms actually ring every time was quite welcome. I couldn't trust WebOS notifications.

  6. nice by gedw99 · · Score: 5, Interesting

    i have been running this on my laptop for curiousity value.

    it works very well, and writing new applications for it is very very easy because its just all web development with html, jsand css.
    makes it very quick and easy.

    also webgl works. Unlike Iphone and android.

    i actually think that this will be big, but take time for people to appreciate it.
    for companies and startups its hell getting android and iphone apps out, but with this is easy peasy.
    the main thing will be that cordova (phone gap) support it, so that people can write in web technologies and still deploy to android, iphone and firefox os easily

    1. Re:nice by Anonymous Coward · · Score: 1

      it is very very easy because its just all web development with html, jsand css.
      makes it very quick and easy

      See, that's the problem with the HTML5-craze. Webdevelopers rejoice because they (think) they can write "apps" with the technology they know, and thus it must be good technology.

      HTML was never meant for apps. Javascript was never meant to be a language for writing full-blown applications. As someone with 10+ years of creating websites, CMS'es and web-based applications I can only conclude that they both suck for writing mobile apps. Also compatibility between these HTML-based platforms (FirefoxOS, Tizen, PhoneGap, W3C widgets, etc etc) is mostly absent.

      I've been dabbling with QtQuick and QML lately on my Nokia N9. I really like it. It's designed from the ground up for writing apps and GUIs in general. For the heavy lifting and more low-level stuff the integration with native C++/Qt is easy. I now feel sorry for people who think that HTML5 is *the* way to create apps. But also Android and Cocoa could learn a trick or 2 from QtQuick.

      FWIW: I haven't had first-hand experience with it, but JavaFX 1.x looked quite powerful too. Seamless databinding, GUI oriented, very expressive language and a native, build-in bridge to Java SE for the power-stuff.

      No doubt there are even better solutions than QtQuick and JavaFX, but my point is that all these HTML5-related platforms are certainly not the best for writing apps.

    2. Re:nice by drinkypoo · · Score: 2

      HTML was never meant for apps.

      Really quite irrelevant.

      Javascript was never meant to be a language for writing full-blown applications.

      Substantially more relevant. However, it should not be a problem for most types of apps people want to run on a cellphone.

      What I don't get is why anyone would want a Web OS notebook, let alone desktop.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:nice by Lennie · · Score: 1

      Actually, HTML5 was specifically created to make "apps".

      Also I believe Firefox OS, PhoneGap, Tizen all use the W3C widgets standard to for defining HTML5-based applications.

      Funny you mention QML, as it clearly derived from HTML.

      --
      New things are always on the horizon
    4. Re:nice by Lennie · · Score: 1

      Why do apps needs servers ? Really HTML5 supports running without servers just fine.

      --
      New things are always on the horizon
  7. Didn't WebOS try this already by goombah99 · · Score: 3, Interesting

    So if everyting is HTML5 then presumably this is going to be like WebOS or apple's Dashboard apps? Didn't Facebook recently retreat from HTML5 to native? Then there's the grim history of javas early promise of write once run everywhere. Has HTML5 grown up so much that it can finally pull it off? or is this more than HTML5

    --
    Some drink at the fountain of knowledge. Others just gargle.
    1. Re:Didn't WebOS try this already by gl4ss · · Score: 2, Interesting

      So if everyting is HTML5 then presumably this is going to be like WebOS or apple's Dashboard apps? Didn't Facebook recently retreat from HTML5 to native? Then there's the grim history of javas early promise of write once run everywhere. Has HTML5 grown up so much that it can finally pull it off? or is this more than HTML5

      nokia scaled back a lot of their webruntime promo too(but on there, the interest from developers was mostly to sidestep binaries signing/certification).

      has html5 finally grown up so much? no, it hasn't. not even on desktop. basically they'll have to invent a bunch of extra api's to match even half of native stuff even on windows phone 7 not to mention craploads to match android.

      just imagine writing a spotify client in pure javascript/html5.

      --
      world was created 5 seconds before this post as it is.
    2. Re:Didn't WebOS try this already by the+plant+doctor · · Score: 4, Insightful

      Yes, Facebook did just retreat from HTML 5. However, the difference there is that they were attempting to support how many different hardwares, screen resolutions, browsers, etc.

      Mozilla here can work with it because they are vertically integrated. They can optimize the apps for their phone alone, not worrying about other phones' screen sizes, resolutions, processors, etc. That's not to say it's not still risky. HTML5 is scarcely grown up, IMO.

    3. Re:Didn't WebOS try this already by Lennie · · Score: 1

      Yes, kind of like Tizen and Windows 8 Metro too.

      Although the difference is, all those platforms do have native applications. Boot2Gecko really is just Linux kernel and some userspace code to talk to hardware (think of: wpa_supplicant) and their browser core:

      https://wiki.mozilla.org/B2G/Architecture

      --
      New things are always on the horizon
    4. Re:Didn't WebOS try this already by burns210 · · Score: 1

      https://wiki.mozilla.org/WebAPI

      Exposing some new APIs via Javascript isn't black magic. Phone, SMS, Camera, WebRTC, WebGL, all Javascript APIs that exist and can be tested today and have been in the works for a year or more. All the hardware access you would want is available in Javascript (for sufficiently authorized apps, obviously).

      Writing a Spotify client as an OpenWebApp in pure-javascript is quite possible today. Preferably using something like Opus for audio, of course.

  8. Usabilty Battery usage? by Anonymous Coward · · Score: 3, Interesting

    From what I've read of B2G/Mozilla OS is that it will be lightweight and be able to run on cheap low-end phones. If it can deliver a smooth, slick interface and/or longer battery life on cheap phones better than equivalent android phones then it could well take market share. The way way we will find out is when they start shipping.

    1. Re:Usabilty Battery usage? by Karlt1 · · Score: 1

      "From what I've read of B2G/Mozilla OS is that it will be lightweight and be able to run on cheap low-unend phones. "

      How is a 700Mhz Arm with 256MB "low-end"? The first iPhone could run a browser and responsive apps on a 400Mhz ARM and 128MB Ram. The first Android devices were similarly low power. Chinese manufacturers like Huwaii are already selling Android phones unsubsidized for less.

      Do you really think you can get more responsive apps running Html+Javascript than native apps?

    2. Re:Usabilty Battery usage? by thelukester · · Score: 1

      From what I've read of B2G/Mozilla OS is that it will be lightweight and be able to run on cheap low-end phones.

      LIGHTWEIGHT?!?, just like their browser Firefox, right? I switched to Chrome for a reason, and that was because Firefox was a bloated CPU, memory sucking pig. The idea of Firefox being the ideal technology for low-end smartphones is laughable.

      The whole idea of using HTML, CCS, and JavaScript as the back end technology for a low-end smartphone is nuts. Even the best HTML rendering engines (Mozilla's Geko is not one of them) are CPU and memory hogs. CSS was never designed for and is nearly impossible to hardware accelerate, and JavaScript is notoriously difficult to optimize and even the best VMs like V8 run orders of magnitude slower then Native code, while the VM itself takes up a massive amount of memory.

      I get that Mozilla wants to put Firefox on a phone. Fine, but first, focus one building a competitive rendering engine. Then you can use this Firefox OS to prototype a easy to use touch UI. But in the end, I want a responsive fast phone, like the iPhone or Galaxy S3, not some dog slow HTML monstrosity.

  9. Anyone used it yet? by mpol · · Score: 1

    Has anyone used this OS yet, and can share some thoughts on it?

    I'm a bit worried that it's a low cost (and probably relative slow) phone, while at the same time HTML5 can be a pretty heavy load.

    I myself am not very fond of Android, and I will not buy anything from Apple or Microsoft. IMO The market can use another platform, especially when it is a portable platform with portable apps.

    --

    Well, don't worry about that. We can get you back before you leave. (Dr. Who)
  10. How is it "negative" to want Firefox improved? by Anonymous Coward · · Score: 1, Insightful

    How is it negative to want Firefox improved, rather than having them waste resources on some half-assed "operating system" for phones?

    Firefox is a product that many millions of people actually use on a daily basis. It's also a product that exhibits poor performance and excessive memory usage. That means it's a perfect candidate for improvement. The need for improvement is clearly there, and there are many people who would benefit from said improvement.

    Yes, it is better now than it was several years ago, but that's mainly because of extreme competition from Chrome. It could still be so much better, however. Its users are still BEGGING for Firefox's performance to be improved, and its memory usage to be reduced. Nobody is begging for yet another a mobile "operating system", especially not one from Mozilla.

    1. Re:How is it "negative" to want Firefox improved? by Anonymous Coward · · Score: 1

      Its users are still BEGGING for Firefox's performance to be improved, and its memory usage to be reduced.

      Firefox is now has lower memory usage than Chrome. Learn to read more than a few troll blogs and STFU because your ignorant. And I'm fucking begging for some mobile OS besides fucking Java and the Apple lock-in and castrate OS. (No, Windows isn't worth mention.) Truthfully I would not use any of the popular mobile OSes if I didn't have a choice.

    2. Re:How is it "negative" to want Firefox improved? by Anonymous Coward · · Score: 1

      Troll much? FF's overall market share hasn't changed that significantly. It's been at about a third for a long ass time. The long tail has gotten shorter and the IE idiots grew up and started using other things. Don't mistake your personal and emotional switch from Firefox to Chrome as a trend. You and your 3 friends don't really make a trend, and 76.32% of statistics from blogs range from fucking stupid to fucking made up.

    3. Re:How is it "negative" to want Firefox improved? by mister_playboy · · Score: 2

      It's also a product that exhibits poor performance and excessive memory usage. That means it's a perfect candidate for improvement.

      As someone who uses FF on a daily basis, I can't help but think these complaints come from people who don't use the software and are repeating old complaints. It's just like PulseAudio.

      I haven't seen memory leakage problems since 3.5 came out, over 3 years ago.

      It's certainly true that something can occasionally misbehave and suck memory/CPU, but that can happen in all browsers and it's usually related to a page with absurd JS or the Flash plugin.

      --
      Do what thou wilt shall be the whole of the Law ::: Love is the law, love under will
  11. Gecko engine on Andoid good idea. by Anonymous Coward · · Score: 1

    Lets see, the whole ecosystem will depend upon android running gecko at a reasonable speed. The weakest link in any js, css based environment will be the web itself. So essentially the core phone apps that do not connect to the net need to be bullet proof speed daemons to make a dent in the market.
    Big question is how well does the core work when the phone is just being used as a phone, camera, audio recorder/player, video recorder/player or office notation device.

    Speaking from my experience with the Windows phone environment where doing anything as simple as taking notes requires a ridiculous number of steps to use the device, Mozilla can become the killa of devices if they concentrate on making access to simple functions like taking notes, saving files, browsing your storage, recording video and voice and the other things that smart phones can do, easy to access. Without having to go through a tonne of screen press steps.

    Hint, create access to simple functions as a browser button that is accessible at any time regardless of the screen app that is current. Then on all apps have a back button to return to the last function. If you hit the back button twice it will return you to the home screen and save any changes that you have made to a file, recording etc automatically. KEEP IT SIMPLE and you will succeed where Microsoft and others are failing miserably.

    Google chrome had the right idea and the time for a desktop/home screen that does it through one interface has arrived. This does not mean that you need to be online to access the cloud for text editing or whatever and if Mozilla does it right where all the others try to send you off to the cloud to do simple things and store things at extra bandwidth cost then Mozilla could succeed big time in the phone OS world. Yes there is a huge market for Palm like devices and sending everything to and accessing the cloud is just too expensive and time consuming for the majority of people who want a smart phone. Microsoft, Apple and Google might find that their cloud centric universe can piss on them sometimes.

    Personally the only thing I use my smart phone for is taking audio notes, video notes, written notes, and photos. Of course telephony is important but the cloud certainly is not! Yes I can facebook or gmail or whatever but that is not what I spend all my time doing and the majority of the myriad of small business smart phone users like myself are in the same boat.

    With RIM about to bite the green weenie, Mozilla has the chance to step into the world of small business in a big way if they play their hand right as NOONE is going to unseat Apple and Google in the consumer smart phone market not even Microshaft.

    1. Re:Gecko engine on Andoid good idea. by Lennie · · Score: 1

      I believe they will first target the South American market. Why ? Because the iOS and Android based devices are very expensive to import.

      If I understand it correctly Mozilla just makes the software and the carrier delivers (produces, locally sources ?) the hardware.

      --
      New things are always on the horizon
  12. Is Marc out there? by Rambo+Tribble · · Score: 1

    "The browser is the OS," ring any bells?

  13. Re:Why So by gaelfx · · Score: 1

    Since when is anthropomorphizing a piece of software named for a ficticious form of fauna insulting?

  14. Re:No market by Anonymous Coward · · Score: 2, Interesting

    You should checkout the fully 3D HTML/JS FPS
    https://developer.mozilla.org/en-US/demos/detail/bananabread

  15. Re:No market by itsme1234 · · Score: 1

    Oops!

    There was a problem starting Bananabread. Please see the Troubleshooting section below for more information.

    Technical Details: WebGL is missing.
    =======
    That much about web based apps that just work.
    Wiki says:
    "Mozilla Firefox - WebGL has been enabled on all platforms that have a capable graphics card with updated drivers since version 4.0"

    Last firefox, ati 5770, what the heck?

  16. Re:No market by thetoadwarrior · · Score: 1

    HTML5 is quite good when someone implements it properly. Not everyone wants Google sticking their nose in everything they do. This is a good alternative.

  17. Re:No market by thetoadwarrior · · Score: 1

    works for me

  18. Re:Very relevant by drinkypoo · · Score: 1

    No, HTML not written for apps is very relevant. HTML provides next to zero ready-made GUI elements, nor layouts.

    Next to zero, but not zero. It does in fact provide ready-made GUI elements, and in fact it's most if not all of what you need to build a functional (if ugly) interface even without CSS.

    This leads to DIVeritis, laden with classes and id's.

    Who cares? You're not meant to edit the HTML directly.

    These are all "stringly typed" at best and thus hard to maintain, harder to debug and refactor.

    These can all be generated programmatically, which can be done by a widget library atop Javascript.

    CSS is also not suited for apps: you cannot copy/paste a widget from somewhere and expect it to render exactly as in the example.

    Your argument is that it makes copy/paste less trivial than other systems in which you might build widgets?

    Sure, with some effort even HTML-based apps can look "native" and good, but from what I've seen from Tizen and FirefoxOS the HTML-code to get there is simply atrocious.

    Who are you, and why should I care about your opinion?

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  19. No Google lock-in by Compaqt · · Score: 1

    IMHO, the best thing about this is you get a nice OS without the Google or Apple lock-in (how stupid is it that you have to create an account in order to use your phone?).

    That, and you don't have to be logged in all the time. It's the same as your desktop: you choose the level of privacy you want.

    --
    I'm not a lawyer, but I play one on the Internet. Blog
    1. Re:No Google lock-in by lbenes · · Score: 1

      IMHO, the best thing about this is you get a nice OS without the Google or Apple lock-in

      How do these inane comments get modded up? My Samsung Galaxy S3 is using the Amazon App Store and my phone's contacts are synced to Yahoo mail. Please explain how Google has "locked me in"? And NO, my phone is not rooted.

      As someone who switched from a browser based Mobile OS, WebOS, to 3GS, and then now Android, I can tell you I will never go back to another laggy HTML based OS. If anything, I'd like to see Android move away from its VM based apps to something like Apple's native apps. Many apps ran better on my 3GS than they do on my much more powerful S3. Mozilla is going the wrong direction on this one. Native > Java > JavaScript

      Why doesn't Mozilla invest their limited resources on making a lean browser that can compete with Chrome instead of a laggy OS that no-one will want.

  20. The Otoro phone ? by Lennie · · Score: 2

    I believe these devices are called "Otoro", because that is what it says on this page:

    "Otoro
            Otoro is a phone being used as a test and development platform as a low-to-midrange smartphone. Most core Firefox OS developers are working on Otoro."

    https://developer.mozilla.org/en-US/docs/Mozilla/Boot_to_Gecko/B2G_build_prerequisites

    --
    New things are always on the horizon
  21. Re:didn't they already announce something like thi by Lennie · · Score: 1

    Yes, the S2 is a one of the development phones of Firefox OS.

    --
    New things are always on the horizon
  22. Re:Very relevant by Lennie · · Score: 1

    "Sure, with some effort even HTML-based apps can look "native" and good, but from what I've seen from Tizen and FirefoxOS the HTML-code to get there is simply atrocious."

    Funny, as this discussion is on a page which discusses Firefox OS. So the HTML-based apps are native to the platform.

    --
    New things are always on the horizon
  23. Re:Gecko. by Lennie · · Score: 1

    Their "catching name" will probably be Firefox OS (or maybe people will be able to buy a "Firefox Phone"). Firefox is a name which many people already know.

    I don't see how that is a bad idea.

    --
    New things are always on the horizon
  24. Re:No market by Lennie · · Score: 1

    Actually Firefox OS does not tarket the high-end phone market, but the lower end.

    HTML5-applications don't need to depend on a server. Anything which will be on the phone by default will certainly not depend on an Internet connection.

    --
    New things are always on the horizon
  25. Re:No market by evilviper · · Score: 1

    You're a moron. This phone has high-end specs, where there are Android phones still selling in the US which are lower-spec than FirefoxOS is targeting, and which are going, non-subsidized, for as low as $40. There is no lower-end than that, and FirefoxOS most certainly will not out-perform Android.

      http://www.virginmobileusa.com/shop/cell-phones/venture-phone/features/

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  26. Re:No market by BZ · · Score: 1

    Does about:support say anything useful about why WebGL is not enabled for you?

  27. Easy Android and iOS compatibility by rfugger · · Score: 1

    The cool thing about developing apps for this phone is that should be fairly simple for Mozilla to provide a compatibility wrapper for Android and iOS, so you get cross-phone app development.

  28. Re:Very relevant by EETech1 · · Score: 1

    Any thoughts on Enyo?
      enyojs.com/showcase/

    Thanks!

  29. Can it succeed? by mr_lizard13 · · Score: 1

    People may buy this product if it is better or at least as good as what's currently on offer. That means offering solid software, solid hardware, and solid services.

    It will be interesting to see if Mozilla can succeed here. They don't have a track record of releasing hits; only the Firefox browser really took off and that's because it was an excellent and better alternative to its competition at the time.

    I just hope for their sake that they don't go with the "it's better because it's open" line. Being open is not what made a bunch of people download Firefox, and it won't make a bunch of people buy a phone.

    --
    "We live in a global world" - Harvey Pitt, former Securities and Exchange Commission Chairman
  30. Re:No market by thelukester · · Score: 1

    Thanks you! You just made my point! My laptop gets 8-15FPS while running this HTML5 web demo in H/W accel. Firefox. When I run the Native version of Cube I get over 100FPS.

    Do you see the problem now? My laptop is much more powerful than that hardware they are targeting, but all of the built in and downloaded apps will be gimped by this HTML "technology".

    For those of you interested, try it out yourself:
    Cube 2: Sauerbraten:
    http://cubeengine.com/files.php4
    Firefox HTML5 Cube 2 port:
    https://developer.mozilla.org/en-US/demos/detail/bananabread