Firefox Mobile Threatens Mobile App Stores, Says Mozilla 278
Barence writes "Mozilla claims that its new Firefox Mobile browser could be the beginning of the end for the hugely popular app stores created by Apple and its ilk. Mozilla claims Firefox Mobile will have the fastest Javascript engine of any mobile browser, and that will allow developers to write apps once for the web, instead of multiple versions for the different mobile platforms. 'As developers get more frustrated with quality assurance, the amount of handsets they have to buy, whether their security updates will get past the iPhone approval process ... I think they'll move to the web,' Mozilla's mobile VP, Jay Sullivan, told PC Pro. 'In the interim period, apps will be very successful. Over time, the web will win because it always does.'"
Deja Vu (Score:5, Informative)
This sounds like Steve Jobs before he announced that the iPhone would be supporting native apps and not just web apps. It already had a pretty fast, capable browser, and there were hardly any apps for it. Within a week of shipping an SDK, there were hundreds.
Re:web-app-web (Score:5, Informative)
Marshmallows are made with gelatin, which is made from meat. (Technically, it's the ground cartilage of food-grade animals)
Vegetarians and vegans won't eat marshmallows because they are basically meat and sugar.
Re:Give me a break, you just made that up. (Score:5, Informative)
Sorry but you are wrong. The iPhone has 17% of the mobile share globally, 50% of the global app usage, and an insane 65% of the mobile HTML request. Unlike you I did the research instead of making shit up. Want the source? Here [macrumors.com]
Sorry, but the MorganStanley slide is talking about 'smartphone' share - and not even market share but _shipment_ share. I am very sure that my current phone along with hundreds of millions of other SonyEricsson or Nokia phones didn't count in their survey, although they've been dealing with GMail or Google Maps just fine years before the iPhone was a glimmer in Steve's eye.
In short: GP is very likely closer to the truth than you are.
Re:Ahem (Score:3, Informative)
You have it backwards. The original way of developing apps for the iPhone was via webapps running in Safari. Then Apple released the native SDK and the world changed forever.
Re:Two things. (Score:3, Informative)
While you seem to have some industry experience, I think you perhaps write off the iPhone a little too easily. I can certainly see some parallels with Apple's Mac strategy in the 80's, but they have done a lot of things right (from a dev point of view), and are seeing success accordingly. 100k apps and rising speaks for itself really.
I agree that the iPhone has a small marketshare of total mobile phones, however the vast majority of mobile applications (where a web app won't do), are targeted towards smartphones. As you can see on this graph [wikipedia.org], the iPhone is currently in third place with around 13% marketshare. Not insignificant, and not bad at all for just over 2 years on the market.
As another poster mentioned, Apple has made it very easy to sell and buy Apps on this device, so most people that own an iPhone will spend money on Apps. Contrast this to Symbian where it takes a pretty dedicated and sometimes technical user to buy and install an application.
So, in the "real world" the iPhone is quite a dominant force already. It may yet prove to be a fad, and the mobile industry does move very fast, but I don't think so. I am personally seeing an increasing amount of consulting requests specifically iPhone related, and interest from corps is sky high.
With regards to your Java point; J2ME is nice (sometimes ;-), and it certainly has the largest install base of any mobile language, but the sad reality is that it is nowhere near "write once, run anywhere". For a cross platform J2ME mobile project, you will usually spend at least 50% of your project time porting and getting things running on devices that all implement it a little differently and have their own quirks. So supporting the majority of smartphones (Symbian, Blackberry, Win Mo and iPhone) will require a lot of specialised code anyway (unless you use a cross platform framework [rhomobile.com], but that has it's own drawbacks).
All iPod Touches and iPhones are essentially the same (barring some hardware differences like processor speed, bluetooth, etc), and an App written for one will almost always run on any other (I have had some obscure issues that crop up between different models, but nothing of significance). This is heaven from a dev's point of view!
If it was surpassed in Japan, why so popular? (Score:5, Informative)
It has only 3-4% percent of the global market share, and technologically already was surpassed when it came to the market in Japan
True that it currently has 3-4% of global market share of all phones - but here you are talking about Java, which does not run on all phones either. So why not speak to the smartphone percentage, which is more like 20%.
As for Japan, if it was surpassed years ago then why is it so popular [bcnranking.jp] there? It's not number one (that's a list updated every week), but it's been in the top ten ever since it was pointed out that it reached number one [cnn.com].
In the real world, not many people care about the App Store or the iPhone.
Except for thirty or forty million users worldwide. By all means feel free to leave them to me.
I'm just stating the facts as I know them from actually being in the market, and keeping up to date, because I need that to make a living.
I think you need to do a better job keeping up. I'm in the market as a full time mobile developer, so my living depends on this too...
when you already have fast Java with accelerated OpenGL, EAX-like audio support, and tons of functions. (Be aware that as much of it is accelerated, Java on mobile phones is vastly faster per raw CPU power, than on desktop VMs.)
You won't find a much bigger Java fan than myself. But the reality is that even if you have some of that on every platform, you have almost no platforms that offer all of that - and the testing required across so many devices makes "reality" that you have to target a handful. Real-world apps are moving in droves to the iPhone/Android, and only the simplest apps or some games are still going to J2ME platforms.
Now if you are including Android in there it's a different matter, but it's really different than J2ME.
All that said... I agree with your conclusion that the mobile browser app market is just not compelling compared to the iPhone or Android - or even J2ME. They'd have to add a ton of stuff just to get close and the native platforms swill simply always be ahead of the game.
Re:Um...how do you figure? (Score:1, Informative)
it should had been .com
(http://www.phonegap.com/)
"More intense tasks" (Score:4, Informative)
Javascript "increasingly more appropriate for more intense tasks."
Yeah, right. I'm getting really tired of web sites that use 100% of the CPU while doing essentially nothing. It's bad enough on a desktop machine. On a phone, that eats the battery.