Don't forget that Android only had a narrow lead over WebOS until the Droid came out. For most of its first year Android, in the U.S., was relegated to T-Mobile and I believe only 2 models there. It added Sprint in October of that year and in November, Verizon.

Quite interesting considering how shitty android was only a year ago (edit: 2.2). Not surprising however, as there was no better alternative (if you didn't want an iPhone). It's still a nice outcome though, we could've ended up with every manufacturer running their own system.

2.2 was released May 20, 2010, but I agree that 2.2 was awful. If you haven't used Android since Ice Cream Sandwich (4.0 released December 16, 2011), then I highly recommend you give it another chance. The difference between them is massive.

It's not like I dismissed android forever after that. I still own an android phone and don't plant to change OS when I'll be getting a new one.

But it seems I was way off in the version history as I thought that 2.2 was released just last year, thanks for correcting me.

Hopefully Microsoft will stop dragging it's feet with Windows Phone 8. I dred to think of a mobile market with only two decent OS options.

Having only two is great for developers, though, at least as long as native apps are preferred by users.

There's a limit to the number of different platforms one can support, especially if they have their preferred programming languages like Android with Java and Apple with ObjectiveC, Microsoft with C#... and even worse, they all have their own UI metaphors, so just porting the code isn't enough. And of course they all have their own app store with weird rules and specific payment options.

Edit: and then I'm forgetting the OpenGL versus DirectX debacle that we'll also get on mobile if MS gets their way. At least now both big platforms use OpenGL ES. Sometimes I wish that standards actually worked and not everyone tried to invent their own :/

I'm not a fan of artificially limiting choice.

I agree that native development across platforms is a pain, but I think the answer is to make cross-platform development easier, not remove platforms. We're getting there- MonoTouch+MonoDroid+Windows Phone mean that you can iOS, Android and WP with just C#- the front-end UI will need to change each time, but you can save a lot of backend reprogramming. Mono-X might not the answer- maybe JS will spread to native as well, or something like that. But let's at least try before we cut people off.

"There's a limit to the number of different platforms one can support"

I keep hearing that. However, I don't think customers care as long as comparable products from developers who have decided that a platform is part of their market develop products for it. That is, not every ISV can, or should, cover every platform. Some should specialize in only one platform. Some should shoot for market entry on "less crowded" platforms.

I create several apps on iOS, Android, Blackberry, Windows 8, J2ME and Brew. The idea that it is to hard to do this is simply false.

It is NOT in your best interest to lock yourself into 2 platforms who will have increasingly less interest in giving you good terms on your iron-clad developer agreements. I can't believe you'd even think this was a good idea.

Can't find any of your "leavesofcode" links : (

I'm sorry but I've professionally worked in the mobile space for years and the idea that it is easy is simply false. I've done BREW and J2ME you know how hard it was. Devices weren't "spec compliants" but "examples compliants" (only a few basic examples would work). Any non-trivial app targetting J2ME devices required a gigantic QA team and the money needed alone to acquire the various devices to be able to test your app was sufficient to drive most small players out of that market.

It was hard on J2ME / Brew because of fragmentation. Then for a few months/years it was "easy" because one iPhone was the only player in town and ruling the entire app market. No fragmentation. Things were great.

But now fragmentation is here again: various Android versions, various iPhones / iPads / etc. and dealing with all these different devices is a complicated things.

You cannot say that it is "easy" because you shipped a "todo app" (or whatever) on these devices.

There are a lot of companies with succesful mobile apps out there stuggling to solve the fragmentation issue.

Of course you can do it but it's not anywhere near "easy".

So saying "The idea that it is too hard to do is simply false" is quite misleading.

Oh I agree fragmentation within an OS is TERRIBLE. I dont however equate that with multiple OS's. I hope we continue to have at least 3 if not 4 or 5 healthy players in the smartphone mobile space.

In what way are they dragging their feet?

Well, they announced it a long, long time before shipping- not good, when existing phones are not going to run it. No-one is going to buy a WP7 phone now, so they really need to get WP8 out as fast as possible.

I agree. I am hoping MS does a turn around as competition helps everyone.

>Others are still struggling at 2% after 2 years, with not much chance of improving

Better than still struggling at 2% after 20 years, with not much chance of improving.

I'm as big a fan of taking shots at Apple as anyone, but only when it's on topic. This is about mobile. Apple's inability to gain traction on the desktop for decades didn't affect the popularity of their take on the smartphone and tablet.

And it isn't even relevant now. In the PC market Apple needs no large market share to make boatloads of money.

They actually don't in mobile either. The iPhone and iPad market shares could both drop to single digits and they'd still be making more than the Android manufacturers. The fact they have a much more 'competitive' market share is just large boat loads of gravy.