Hacker News Reader

Comment by zxoq | Hacker News Reader

Not on mobile, which is where Facebook wants a browser.

I use Firefox on my Android. It's a little heavy but it's OK. I like it a lot because I'm a desktop Firefox user and it knows how to sync my bookmarks and my saved forms data and my history back and forth. The UI is also much better than Android's built-in browser and it's been making a lot of progress.

I think people are not seeing the forest from the trees here. Firefox has a lot of potential on mobile phones, because Firefox has a lot of desktop users that would want the Firefox on their mobile devices, at least for the Sync functionality.

Also, on mobile WebKit may be the most popular, but there are so many incompatibilities and performance differences between Android's browser, Blackberry's browser, the webkit-powered S60 browser, Chrome, Safari and Mobile Safari that you might as well count those as different engines.

Gecko will NEVER render on a feature phone. The Mozilla team has repeated this statement again and again.

A year ago feature phones were being released with 1GHz processors [1]. I wouldn't say never.

[1] http://www.gsmarena.com/1ghz_s40based_nokia_c3015_pictures_s...

What OS do they run? It's hard to imagine porting to another OS with insanely tiny marketshare and weird APIs. What is the app publishing ecosystem on these phones?

This phone runs Nokia's Series 40, which is running 1.5 billion phones - supposedly the largest mobile operating system. Perhaps this is a bad example though as S40 only runs Java ME & HTML5 apps. Still, I can easily see these feature phones running Firefox within a year. Firefox is, after all, open source.

Firefox on mobile is the new Linux on desktop... It's open source and you can see it being big next year, every year.

Reply on news.ycombinator.com