6 Comments

Summary:

The first beta version of mobile Firefox for Android has been released and is now available in the Android Market. We have taken it for a test drive and while it shows good potential, it may be solving a problem that doesn’t exist on Android.

FF landscape

Firefox has been working on the mobile version of its popular browser, aka Fennec, for quite a while. The first beta version for Android has been released and is now available in the Android Market. We’ve taken it for a test drive, and while it shows potential, it’s not quite ready for prime time.

Mobile Firefox uses the same web page rendering engine found in its desktop version. It uses Firefox Sync to keep bookmarks, tabs and other browsing information in sync with the desktop browsing experience, something desktop Firefox users will appreciate. It also borrows a feature from the Android Dolphin Browser that I like: Bookmarks and preferences are accessed by sliding the screen to the right and left, respectively.

The Firefox app is huge by Android standards, with the installed app occupying a whopping 29.33 MB of memory, and after gentle use, over half again as much in data storage. That may play a role in how long the app takes to start, and how slow it can be at times during use. Firefox can be moved to the SD storage card, which makes the storage easier to handle.

The core function of a web browser is web page rendering, and Firefox needs some work in this area. Pages take a while to appear, and while WebKit-based browsers keep text legible during page display, Firefox does not. Even standard pinch/zoom functions, while performed smoothly, do not keep things legible while they happen. Firefox doesn’t reflow the text as zooming happens, something most Android browsers do very well. It shows potential, but isn’t quite there for daily use.

The browser makes use of add-ons, and Firefox already has a lot of add-ons available to improve the browsing experience. There are ad blockers, Twitter utilities and the like that can be installed to the browser. Adding them can be a clunky experience, something that will surely improve as the browser evolves. I was quite surprised to see that many add-ons aren’t free; they can be quite expensive in fact.

The best way to get a picture of Firefox in action is through images, and I’ve snapped a few. They make it clear that Firefox for Android has a way to go before it’s ready for heavy usage. It’s great to have choice in browsers, and Firefox desktop users will love having a mobile version that syncs bookmarks with their desktop, but as good as most Android browsers are, it might be looking to solve a problem that doesn’t exist. It does bear watching to see how Firefox develops for the mobile platform.

 

Related research from GigaOM Pro (subscription req’d):

  1. Pretty good overview of mobile FireFox James. For now I’m skipping FF just because of it not rendering the pages like the other browsers that are available for Android.

    Share
  2. Agreed, James. Not nearly ready in my view. Tried it out last night but was underwhelmed.

    Share
  3. “It also borrows a feature from the Android Dolphin Browser that I like: Bookmarks and preferences are accessed by sliding the screen to the right and left, respectively.”

    Hey! Mobile Firefox has been doing that since its first Maemo alpha releases in 2008! :)

    With that aside, thanks a bunch for the great review and thoughtful critique.

    Share
  4. Thanks for the hands on review. I use the desktop version and am waiting for the Android, but your review is very much what I expected. I think I am going to wait somewhat longer. Sounds like they are going in the right direction though!

    Share
  5. Thanks for the review …I was eagerly waiting for firefox for Andriod…because I am prone to firefox on PC…

    Share
  6. Every mobile platform already has a WebKit based browser. Even Bada has just gone WebKit.

    Well there is one exception. The only mobile platform without a WebKit browser is Microsoft’s Windows Phone 7, where Microsoft has chased away other browser vendors by denying them access to the native code that its inbuilt IE7 Mobile has access to.

    Mozilla made an announcement some months ago that it would not be developing anything for Windows Phone 7. It’s kind of ironic, as this is the platform that would surely need an alternate browser more than any other, as it has no WebKit alternative. If only Microsoft would allow them access to that native code.

    Share

Comments have been disabled for this post