Android is 5 years old today: Here's how it all began
crave.cnet.co.uk
crave.cnet.co.uk
http://www.businessweek.com/stories/2005-08-16/google-buys-a...
For a more complete history, there is an article from 2008 that goes back to how it all began, only this time starting from 2003, quoting Andy Rubin in an interview with Business Week before founding Android Inc. that October.
http://www.techradar.com/us/news/phone-and-communications/mo...
This article neglects a large piece of the history of the project. Don't bother reading it.
The thing to remember was that iPhone had just been announced and everything was about to change radically. Even in this 2007-2008 timeframe everything was about the mobile web. Google's intent for Android - as it was explained to us - was to get the rest of the planet that didn't own a PC into a mobile device that they could use to see the web...and see Google's advertising by consequence. There was no App Store yet. Even Apple was trying to get everyone to do their apps in Safari, remember?
A platform able to run on a large number of devices, not perfectly tuned to the hardware as iOS, but very good nonetheless,
Google managed to spot the market opportunity with great timing and went for it with pretty good execution.
This should have really been Microsoft territory, I wonder if the scenario will change somehow with Windows Phone 8 ?
I don't quite buy it though. The place i have seen least enthusiasm for Windows 8 is in the Enterprise.
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 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.
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.
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.
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.
Better than still struggling at 2% after 20 years, with not much chance of improving.
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.
The only remaining question mark in my mind: how much might it eventually sell into the portable PC market? (Beyond the natural cannibalism of mobiles blunting PC sales)
Two things about that:
1. The price of admission to the OS business is to come up with a better kernel than Linux, with better driver support. If that price is higher than the benefit a new kernel will deliver to end-users, it won't happen.
2. The center of gravity in OS innovation is in the managed language runtime and middleware, where Android has done a great job (while Microsoft failed to capitalize on the userland power of the CLR, MSIL, and C# and other CLR languages).