Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Communications Mozilla The Internet

Mozilla Is Eyeing Your Phone 107

Slatterz writes "Mozilla is planning to develop a browser for mobile phones by 2010. Mitchell Baker, chairman of the Mozilla Foundation, has been laying out her plans for the organisation over the next two years. Baker also committed to expanding the role of Firefox and building on its market share, while developing new browser technology such as the Aurora project. Mozilla has already stated that it is working on a mobile version of Firefox, but has never set a timeframe for release."
This discussion has been archived. No new comments can be posted.

Mozilla Is Eyeing Your Phone

Comments Filter:
  • 2010? (Score:5, Insightful)

    by rallymatte ( 707679 ) * on Friday September 19, 2008 @03:54AM (#25068387)
    They will be left so far behind.
    Apple's safari is already an amazing browser for mobile phones.
    I'm sure that Google won't take as long as 2010 to come out with a mobile version of Chrome.
    Opera might not be the best browser for mobile phones, but it's pretty decent.
    IMHO I think Mozilla needs to get their mobile browser out a little bit earlier than that. Of course it's a good strategy to not release the software until it's ready, but how far behind are they ready to get?
    • Re:2010? (Score:5, Insightful)

      by Anonymous Coward on Friday September 19, 2008 @04:00AM (#25068413)

      Apple's Safari only comes with the iPod touch and the iPhone and cannot be used with normal phones.
      Google Chrome for phones will take far longer to come as they still have to iron out bugs in their desktop version, which is their main focus, before they will release a mobile version.
      Opera is not very customizable and I for one hate the interface.

      I believe this is a good step by Mozilla and I would far rather have a good version and wait a bit longer than have a buggy version but have it earlier. Anyways, I'm sure they will have beta versions released far earlier than that for early adopters such as you.

      • Re: (Score:1, Informative)

        by beelsebob ( 529313 )

        Apple's Safari only comes with the iPod touch and the iPhone and cannot be used with normal phones.
        Yes, that's right, that's why Nokia's phones all use it. Wait, no, that's not right.

        • Re:2010? (Score:5, Informative)

          by entgod ( 998805 ) on Friday September 19, 2008 @04:14AM (#25068487)

          Apple's Safari only comes with the iPod touch and the iPhone and cannot be used with normal phones. Yes, that's right, that's why Nokia's phones all use it. Wait, no, that's not right.

          You're right, it isn't. The Nokia phones most certainly do not use safari even though nokias browser does utilize webkit, the same rendering engine as safari and chrome. Webkit != safari.

      • Re:2010? (Score:5, Insightful)

        by TheRaven64 ( 641858 ) on Friday September 19, 2008 @04:35AM (#25068593) Journal

        Safari only comes with iPhones, but WebKit is running on Linux (GTK and Qt), Series-60 (Symbian) and even Wince devices. It's pretty hard to find a device that can't run some form of WebKit browser these days, and all of them benefit from the work that other WebKit contributors (Apple, Nokia, Adobe, Google, etc). Mozilla is now saying that WebKit will have two years with no competition in the fastest-growing segment of the market.

        This is exactly the reason why Mozilla lost the first browser war. After Netscape 4 (which wasn't a great product), development was handed over to the Mozilla group. Between Netscape 4.8 (1998) and Mozilla 1.0 (2002) there was a four year gap. By the end of this time, the only people using Netscape / Mozilla were the people with no other options - even a lot of Linux / BSD users had gone to Opera - and it's taken them six years to claw back a 15% share in a market where they used to be ubiquitous. In 2010, every mobile device will come with a web browser (most do already), be it Opera, Pocket IE, or something WebKit based. Mozilla will need to give people a really compelling reason to move to their new browser.

        • Re: (Score:3, Interesting)

          by Yer Mum ( 570034 )
          That'll be sync with their desktop Mozilla browser.
          • Re: (Score:3, Informative)

            by kv9 ( 697238 )

            That'll be sync with their desktop Mozilla browser.

            you mean like Opera already does? WOW! what will they think of next?

            • by Yer Mum ( 570034 )

              As far as I can tell (and I use it fairly regularly), Opera Mobile v8.65 on Symbian doesn't have a sync option with the desktop version.

              (If anyone is curious I mentioned sync because it's one of the projects in Mozilla Labs so it's going to happen... eventually.)

              • by kv9 ( 697238 )
                Opera Mini 4.1 has a big fat sync button right in the first window. it's green too.
                • by Yer Mum ( 570034 )

                  How annoying. You'd have thought they could have managed to put sync in Opera Mobile, which supposedly has more features than Mini.

                  Maybe it'll appear in version 9.5.

        • It's pretty hard to find a device that can't run some form of WebKit browser these days

          Nintendo DS can run community apps with the Games n' Music card by Datel, but it also has only 4 MB of RAM, or 12 MB if you plug the extra stick of RAM that comes with Opera into the GBA slot. Sony's PSP has 32 MB of RAM, but you need to already have a modded PSP in order to mod yours to run community apps.

      • Re:2010? (Score:4, Insightful)

        by Firehed ( 942385 ) on Friday September 19, 2008 @04:45AM (#25068655) Homepage

        It seems to me that a mobile version of Chrome would end up almost easier than the desktop version. Since you can only view one page (or tab, if you will) at a time on a mobile browser, the whole threading issue that actually makes Chrome fairly unique pretty much goes away. Of course there's also the new Javascript engine which will end up being fairly critical on mobile phones, especially as phones and what we expect to do with them advances.

        I always like to see more options available for people, but I don't really see a whole lot of difference on the user's side of things between different mobile browsers provided they all render HTML and CSS the same way (as Gecko and Webkit finally do). It really just comes down to whose affiliate link gets stuck in the google search URL. Aside from just slow rendering in general (which is mostly a hardware limitation), my only real complaint about Safari on the iPhone is a lack of an adblocker, and that's only for the bandwidth savings (if nothing else, it would be nice if it could delay the requests for content that match the filterset.g list until all of the content from the original domain is downloaded just to speed up progressive rendering of the actual content).

        Unlike on my desktop, I really don't care tremendously which browser I'm using on a mobile device, unless one is significantly faster than the other. The UI will mostly be device/OS-dependent, and most extensions and/or plugins are pretty much impossible at least logistically (adblock again really being the only thing that you could implement and would make sense to do). If Mozilla produces a mobile browser then more power to them, but they have to provide a benefit over what's already in place in order to get people to switch and quite frankly I don't see it happening on a handset. I live and die by my Firefox extensions on the desktop, but... we'll see, I guess.

        • Re: (Score:3, Interesting)

          It seems to me that a mobile version of Chrome would end up almost easier than the desktop version. Since you can only view one page (or tab, if you will) at a time on a mobile browser...

          Mozilla's Minimo [mozilla.org] running on my Windows Mobile-based phone already runs with tabbed browsing... Just because we're used to ridiculously high-resolution screens doesn't mean we should forget that early computer screens had lower resolutions than many current phone screens...

          • by zygwin ( 1091281 )

            I think it is the fennec that is Mozilla's mobile browser project.it's available as an alpha for OS2008: Nokia's N800 model supports it.

            Here:http://maemo.org/downloads/product/OS2008/mozilla-fennec/

            and
            https://wiki.mozilla.org/Mobile/FennecVision [mozilla.org]

            • Oh, yep... I should probably have mentioned that... Minimo was the previous attempt at a Mozilla-based mobile browser, and Fennec is the new one.

              Many of the Fennec-related pages on the Mozilla site still occasionally referred to Minimo up until a few months ago when I last checked...

              I'm glad that there's some progress on that front; I look forward to seeing a Windows Mobile release soon... (Or hopefully getting Linux running on my Hermes, and then running Fennec under that... :-) )

          • by cawpin ( 875453 )
            Minimo won't even run on my WM6 Samsung i760. It just gives me a constant stream of crash reports. It didn't run on 6.0 and doesn't run on 6.1.
            • by Idbar ( 1034346 )
              MiniMo runs on my WM5 HTC8125 with no crashes. However, the device is so old, that the memory and processor makes the browsing experience slow and painful sometimes. I removed it because as Skype, the requirements are a bit higher than the 8125 is capable of. I would be able to try them again in a better device.
        • Since you can only view one page (or tab, if you will) at a time on a mobile browser

          You can use three tabs on the PSP's browser.

          • by Firehed ( 942385 )

            Right, and there are 8 tabs on the iPhone. My point was that you're limited to viewing one at a time, unlike on a larger screen where you can just open a second window and have some reference material up while you're typing something out, or whatever. More significantly, any processes that the non-frontmost tab are running can be safely frozen in order to conserve system resources; on a desktop this isn't always an option (think streaming audio/video in the background while you do something useful in fron

        • Re: (Score:3, Funny)

          by foniksonik ( 573572 )

          Regarding multiple windows/tabs... on iPhone you get multiple tabs er windows... there's a little button at the bottom to open or navigate to a different window (with different url)... quite handy.

        • by cyn1c77 ( 928549 )

          If Mozilla produces a mobile browser then more power to them, but they have to provide a benefit over what's already in place in order to get people to switch and quite frankly I don't see it happening on a handset.

          I bet people would switch if Mozilla's mobile browser would efficiently show them all the parts of the internet.

      • Except for Android's browser which will no doubt be renamed and changed a bit to Chrome Mobile or something.
      • Re:2010? (Score:5, Interesting)

        by repvik ( 96666 ) on Friday September 19, 2008 @05:14AM (#25068777)

        Google Chromes V8 engine can compile to x86 and ARM targets. ARM is in the majority of phones. I don't think it'll take Google very long to get Chrome "good enough". Infact, I'm pretty sure they'll release Android with Chrome on the HTC "Dream", to be released in Q4.

    • Re:2010? (Score:5, Informative)

      by tomtomtom777 ( 1148633 ) on Friday September 19, 2008 @04:03AM (#25068437) Homepage

      Actually, they already have been working on a mobile version [mozilla.org] for years. Not much progress though...

      • Re:2010? (Score:4, Insightful)

        by BrokenHalo ( 565198 ) on Friday September 19, 2008 @04:30AM (#25068563)
        Well, they can take their time as far as I'm concerned. I can think of more pleasant and productive ways to spend my time than trying to navigate and strain my eyes reading webpages on those tiny screens.

        I can endure it for a quick email or weather report, but otherwise I'll just wait a little while until I get an opportunity to use a proper computer.
        • Re: (Score:1, Funny)

          by Anonymous Coward

          I look forward to browsing the web not only on a tiny pocket sized screen, but at tens of cents per kilobyte I want some awesome javascript engine so I can watch the animated banner ads.

        • > trying to navigate and strain my eyes reading webpages on those tiny screens.

          Samsung will ( allegedly ) be selling mobiles containing 3M microprojectors by EOY 2008. So throw the webpage onto the wall.

          In 2010, who knows. Perhaps a mobile will dock with a USB3 slot on your laptop or on the side of your 32" monitor?

    • Re:2010? (Score:5, Interesting)

      by SanityInAnarchy ( 655584 ) <ninja@slaphack.com> on Friday September 19, 2008 @04:56AM (#25068707) Journal

      What's more, 2010 means another iteration of Moore's Law.

      Which means, taking the iPhone as a benchmark, we'll have phones with 256 megs of RAM and 1.2 ghz processors.

      It's been awhile since I've touched anything with less than 512 megs on it, but I know I used to run Firefox (before it was called Firefox -- remember Phoenix?) on that little RAM, with plenty of other programs open. Most phones are designed to run exactly one app at once.

      So, extrapolating all of that -- I'd say they could do absolutely no coding, other than developing a skin and ensuring that it compiles for ARM, and still have a usable product.

      But maybe that's your point -- by the time they get their act together, it should be possible to simply put Linux on an iPhone and run the desktop version of Firefox.

      • by BZ ( 40346 )

        There's a fair amount of UI work involved in running well on a small screen like that, though.

      • I have run Mozilla (suite) with as little as 32 MB of RAM for at least a year. Apart from taking a bit longer to start up, it worked fine. Also notice how the recommended minimum amount of RAM is 64 MB.

      • What's more, 2010 means another iteration of Moore's Law.

        Which means, taking the iPhone as a benchmark, we'll have phones with 256 megs of RAM and 1.2 ghz processors

        Or 1/2 the price.

      • by starwed ( 735423 )
        I can tell you this: my phone sure as hell isn't even within 2 generations of the iphone. Not everyone goes for the top of the line...
    • Re:2010? (Score:4, Informative)

      by ozmanjusri ( 601766 ) <.moc.liamtoh. .ta. .bob_eissua.> on Friday September 19, 2008 @05:14AM (#25068781) Journal
      I think Mozilla needs to get their mobile browser out a little bit earlier than that.

      There are versions out already. The browser in my Nokia N800 is Mozilla based.

      • I've also got an N800 running the Mozilla-based browser. It's fabulous!

        The N800 also runs Opera, which is slightly faster than the Mozilla browser, but Mozilla is running all the JavaScript that Opera is discarding. The Mozilla browser supports Flash 9 too. All in all it's a nice piece of work.

        The N800 is 800x480 pixels on a 4.1 inch screen, which is just enough to browse "real" websites in the way they were designed to be browsed. With some phones now approaching this (e.g. the HTC Touch HD is 800x480
      • MicroB s a fantastic browser, but the lack of XUL has a few major downsides: the context menu isn't extension-customizable, most extensions need significant re-writing to work at all, and customization in general is worse than it should be.

        Additionally, I'm pretty sure it uses the older version of Gecko that can't even pass Acid2. I don't know how hard it would be to fix that, though, and for all I know they did in Diablo, but I don't have a n800 at hand to test with.

        On the flip side - it's a browser that r

    • by Joebert ( 946227 )

      but how far behind are they ready to get?

      Far enough behind to see what features people take a liking to on other browsers so they know what to steal, err I mean implement ?

    • "2010" ? Why the hell "2010" ?!?

      There's already MinoMo which is *already running* currently on my Openmoko. Also running on Windows CE and Linux PDAs.

      There was even a recent announcement on /. [slashdot.org] about a soon-to-be-released "Firefox"-branded mobile browser descendant of that previous effort.

      Now what is this 2010 time frame ? Maybe by then they will announce a separate brand of software specially targeting mobile platforms (FireColibri, FireFennec, SeaShrimp or something along these lines with Debian simultaneo

    • by caller9 ( 764851 )

      Actually Google has had a webkit-based mobile browser for Android since an SDK Release last year.
      http://googlesystem.blogspot.com/2007/11/web-as-seen-through-googles-mobile.html [blogspot.com]

      Google's had a browser for mobile for quite a while. I seriously doubt it ever sees daylight on PocketPC/Symbian.

      So is Mozilla aiming to simply beat pocket IE. Not sure about any immediately upcoming version of pocketIE, but unless it is webkit based, I wager it stinks. The current pocket IE (WM6) is just horrible and the reason for

    • FYI Google Android already has a built in browser based on Webkit and has for a long time. I have it running on my phone right now. It's far superior and faster than Opera Mobile.

  • opera mini? (Score:1, Interesting)

    by Anonymous Coward

    I wonder how it will compete with mighty opera mini? Opera uses an online server to cache the images before sending them to you to save you money. Firefox is going to need similar innovation to make a dent

    • Re: (Score:1, Insightful)

      by Anonymous Coward

      It wouldn't be too difficult to install a similar kind of caching/compressing proxy on your own machine (either at home or on a proper server in a datacenter, whatever), and that would not only do what Opera Mini does but it also would do in a private way, win win.

      Oh, that doesn't cater to noobs, I hear you say ? Well, how about "use Mozilla's server by default, but with the freedom to change it if you want" ? Also full of win.

    • Re: (Score:3, Interesting)

      by Firehed ( 942385 )

      How on earth would caching images on an online server save me money? If it very aggressively cached content on the device itself, maybe...

      If you meant compressed, that would be a different story entirely. However, I don't think it likely that too many people without an unlimited data plan would be doing much if any browsing on their phones. Still, the bandwidth savings would be a big plus. If I could cut down on the bandwidth usage significantly at the expense of some jpeg artifacting, I'd be all over i

      • I think the trick was downsampling the images to reduce load times, (with a corresponding saving in data consumption as well)...

        And plenty of people without unlimited data plans surf on their phone.

        • The PSP's browser has an option that enables something similar; it decreases the quality of images to conserve RAM (it only has 64MB).
          • by LukePH ( 1065930 )
            The main feature is the fact the images are resized and compressed on their proxy before you even download it, conserving expensive bandwidth, not just ram. you can change how much they get resized in the settings
            I love the fact that website layouts are preserved, and bigger then my screen size, yet the text is forced only to stretch the width of the screen when zoomed in, so you only have to scroll down to read.
      • by mdwh2 ( 535323 )

        He does indeed mean compression.

        However, I don't think it likely that too many people without an unlimited data plan would be doing much if any browsing on their phones.

        It's not clear to me there is necessarily much of a correlation - I'm on Pay-as-you-go, because I don't do much phone calling or texting, but I still occasionally want to look at a webpage. But not enough that a unlimited data plan would be worth it.

        Most people don't browse on their phone because they still aren't aware it's possible, but it

      • by cciRRus ( 889392 )
        Here's video [youtube.com] on Opera Mini features. They talked about the caching feature.
    • Opera uses an online server to cache the images before sending them to you to save you money. Firefox is going to need similar innovation to make a dent

      I virtually always get over 0.5Mbps from my HSDPA connection, and frequently saturate the 2.1Mbps Bluetooth 2.0 link to my phone, which is more than adequate for browsing without compression. 3G/3.5G networks are rapidly expanding around the world. Proxies were a great idea back in the days of GPRS, but I just don't think it's worth pissing about with them

    • by mdwh2 ( 535323 )

      I agree, though the great thing about Opera Mini is that it's written in Java, meaning that just about any cheap old phone can run it. Whilst most phones these days have built-in browsers, they're often not very good, but Opera Mini means they have a decent web browser. (I'm always amused when I see Iphone-fans say how wonderful it is they can now view "proper web pages", mistakenly thinking that all that was possible before the Iphone was WAP pages...)

  • by m50d ( 797211 )
    when opera mobile is already out there and working fantastically? I very much doubt firefox will get its memory usage down enough to compete.
    • Re: (Score:3, Interesting)

      by badpazzword ( 991691 )

      The desktop versions of mainstream browsers nowadays have memory consumption in roughly the same order of magnitude.

      Also consider that browsing on a as-smart-as-it-can-be device will still be lighter than browsing on a full blown computer.

      You don't even need tabs to get that piece of information you need off the net, log out and move along.

    • Re: (Score:3, Insightful)

      by TheRaven64 ( 641858 )
      Competing with Opera Mobile is easy. Opera costs money. If you want to ship Opera with your device, you need to pay for it. It's not much, but it eats away at your profits. In contrast, a Mozilla browser will be free for device manufacturers to install. The real competitor is WebKit. Device manufacturers (e.g. Nokia) already have this ported to small form-factor devices (I can run a WebKit browser on my phone with a 200MHz ARM chip and 32MB of RAM, although the screen is so small that it's not really
  • by RuBLed ( 995686 ) on Friday September 19, 2008 @04:13AM (#25068485)
    By 2010, there would be mobile phones/devices that would have a larger screen resolution and more processing power (and RAM). As technologies advance, the problem is getting less and less about cramming info on a small screen and more about delivering the same featureset of the desktop variants to a mobile device.

    So I guess beyond 2010, they should just port the desktop code to whatever platform mobile devices run on.

    That is unless we don't try to dream and reinvent the simple web browsing so that it would take all your PC's resources and ask for your firstborn.
  • by Anonymous Coward on Friday September 19, 2008 @04:18AM (#25068513)

    Glad to hear that they are developing the Aurora project. Very interesting piece of software, you can find the home page at http://www.adaptivepath.com/aurora/ [adaptivepath.com]

  • Again? (Score:5, Interesting)

    by David Gerard ( 12369 ) <{ku.oc.draregdivad} {ta} {todhsals}> on Friday September 19, 2008 @04:21AM (#25068523) Homepage

    How many projects to get Mozilla on mobiles have they started so far? Whatever happened to MiniMo?

    I suspect this'll happen when mobiles have enough memory to just run Firefox.

    • Re: (Score:3, Interesting)

      by TheRaven64 ( 641858 )
      The current generation of handhelds come with 4-600MHz ARM chips, and 128MB of RAM. By 2010, we can expect at least 1-2GHz and probably 512MB of RAM. I have a laptop with these specs and it runs Firefox with no problems. It sounds like the 2010 timetable is not to complete a mobile port of Firefox, it's for handhelds to be able to run the current Firefox.
      • Re: (Score:3, Informative)

        by David Gerard ( 12369 )

        Yep. In my experience it's memory that's key - FF3 will run quite snappily on a Pentium II if it's got >=512MB of memory.

        • Nonsense. I run SeaMonkey 1.1 (equivalent to Firefox 2) on 160 MB of RAM fine. The bottleneck is the CPU speed for XUL and JavaScript.

      • A port of Firefox 2 is available for newer ARM based computers running RISC OS.

        One of these RISC OS computers uses a 400MHz Samsung ARM processor with 128Mb of RAM as standard. I think it's fair to say processor power and RAM aren't going to be too big an issue.

  • by Rogerborg ( 306625 ) on Friday September 19, 2008 @04:26AM (#25068551) Homepage
    I hate to pop the Anglocentric bubble, but Access Netfront [access-company.com] and Picsel Browser [picsel.com] have the Far East and Asian markets (carrier and OEMs) stitched up between them. North America and Europe are already fairly small markets in comparison, and the segment of users who can and will install a 3rd party browser is pretty much you, me, and Bob over there.
  • Minimo (Score:2, Interesting)

    by Fatalis ( 892735 )

    The summary is misleading, it should say "Mozilla is planning to develop a[n another] browser for mobile phones by 2010.", because Minimo (Mini Mozilla) has existed for years: http://en.wikipedia.org/wiki/Minimo [wikipedia.org]

    I've even used it on my PPC, but found that it isn't very good, especially compared to Opera Mobile.

  • SCNR (Score:4, Funny)

    by Qbertino ( 265505 ) <moiraNO@SPAMmodparlor.com> on Friday September 19, 2008 @05:49AM (#25068913)

    If Mozilla is eyeing for the phone - doesn't that make it an eyePhone?

    *TA-DUM* *CHRASH* *THUD*

    Thank you, thank you, I'm here all week. Try the fish.

  • Not so far (Score:2, Informative)

    The new mozilla based mobile, based on current mozilla techno + some additions for mobile, is already available in alpha.
    https://wiki.mozilla.org/Fennec [mozilla.org]

    This is like Firefox with the ui completely redone.
    It will also support extensions.
    2010 is just 1.5 year away so having a non beta build for 2010 doesn't seem unrealistic.

    I guess some optimisations made for mobile environnement will benefit everybody (like the optimization done for Firefox)
    (and there's already a tracemonkey javascript for arm so this will be

  • Why would this take 2 years? Can't they put a team on it and crank something out in a month or two? In two years I'll have already discarded three more handsets.
  • If Opera (who makes a fast browser with no visible memory/cpu problems) can't make a mobile browser that doesn't die on "out of memory" on *every* page on my HTC SmartPhone, then what chance does Mozilla (the king of memory leaks and runaway CPU) have? I'd sure love to see a lean, mean, mobile Mozilla, but I have some serious doubts if they can pull it off.

    The latest Opera mobile truly is unusable on my Windows Mobile smart phone (due to the out-of-memory-thing) which was quite disappointing to me. I've y

  • Will it feature the "AwesomeBar"?

    Not interested.

  • by slapout ( 93640 ) on Friday September 19, 2008 @09:22AM (#25070865)

    Has anyone else noticed that every six months Mozilla announces that they're working on a mobile browser?

  • Focus on interface (Score:2, Insightful)

    by shmmeee ( 934743 )
    I've used Nokia's Webkit based browser, Opera Mini and Opera, Pocket IE and the iPhone's Safari browser and one thing is quite obvious to me. You can't replicate all the functionality of today's web without a mouse like device. The iPhone comes closest, but the inability to move just the mouse pointer to hover over things means many menu systems and some Flash games aren't usable. IMHO, solve the mouse problem and you solve mobile browsers. The technical ability to do stuff will come as mobiles catch up
  • After all, it "duplicates functionality"

  • The post that's referenced in the article is available on mozilla's newsgroup and was Mitchell just asking for feedback on our 2010 goals. We're still in the process of fleshing out those goals and we're trying to figure out how mobile plays a role in them.

    Our mobile involvement is something that's going to take a while to get spun up, but it's not something that will take as long as people think it will take here.

    First of all, Mozilla is the only browser solution that has a fully open source browser that'

Some people manage by the book, even though they don't know who wrote the book or even what book.

Working...