Slashdot Mirror


Mozilla to Develop Mobile Firefox

Kelson writes "Mozilla has announced a new initiative to bring Mozilla to the mobile web, including a fully functional mobile version of Firefox (yes, with extensions). The focus will be part of Mozilla 2, the big revision coming after Gecko 1.9 and Firefox 3. Minimo, the previous attempt to port Mozilla to mobile platforms, is apparently dead, but 'has already provided us with valuable information about how Gecko operates in mobile environments, has helped us reduce footprint, and has given us a platform for initial experimentation in user experience.'"

4 of 152 comments (clear)

  1. By the time.... by CRCulver · · Score: 3, Insightful

    I'll bet that at the sluggish rate Gecko development proceeds, by the time the mobile version appears, mobile devices will have almost the power of today's stationary hardware.

    1. Re:By the time.... by AKAImBatman · · Score: 5, Insightful
      FTFA:

      Getting a no-compromise web experience on devices requires significant memory (>=64MB) as well as significant CPU horsepower. High end devices today are just approaching these requirements and will be commonplace soon For example, the iPhone has 128MB of DRAM and somewhere between a 400 to 600 MHz processor. It is somewhere between 10x-100x slower on scripting benchmarks than a new MacBook Pro and somewhere between 3-5x slower than an old T40 laptop on the same wifi network. But rapid improvements in mobile processors will close this gap within a few years.

      I find this to be a rather shocking statement. The author is claiming that a handheld that meets the minimum requirements for a modern web browser on a desktop OS is not quite sufficient to run an embedded version? If that's really the consensus of the Mozilla developers, then my opinion is that they need to reevaluate how their approaching phone handsets. It is not a desktop platform, nor will you get the best experience by treating a handset as a desktop platform. As Apple and Opera have been showing with their embedded browsers, the interface should be designed around the phone rather than forcing the phone to be designed around the interface.
  2. Re:reduced footprint? by JerkBoB · · Score: 3, Insightful

    Damn, you guys beat me to it.

    I suppose it's obvious, though...

    mjmac@ganymede:~$ ps axwu | grep firefox
    mjmac 13089 0.9 11.3 786244 232776 ? Sl Oct09 16:47 /usr/lib/firefox/firefox-bin

    Isn't firefox supposed to be the lightweight alternative to Mozilla? *cough*

    --
    A host is a host from coast to coast...
    Unless it's down, or slow, or fails to POST!
  3. Re:Why have 23 flavors when you can't do vanilla? by DrXym · · Score: 3, Insightful
    I use Firefox all day, every day sometimes with 20 tabs open. I won't say it never crashes but it manages to last a hell of a lot longer than 3 hours on average. I don't have issues with the memory either considering the number of tabs, session history, cache and so on.

    If memory really bothers people they should turn their settings down and modify their browsing behaviour since Firefox takes the sensible default approach of using whatever memory you have to optimize the user experience.