Sure there were 'processes', like "Canary it in some cluster and watch the results for a few weeks before turning it loose on the world." but being completely vertically integrated is a unique sort of situation.
Android is much like a more traditional vendor/customer model where they are at a place in the pipeline that has to co-ordinate with other things that are in the pipeline. Except when those 'other things' are hardware it gets really strange.
I was present in meetings in which all the folks at the meeting would nod their heads at some release date which was totally and completely imaginary. It existed so that dereferencing the term 'release date' didn't return 'undefined' :-). I remember my first project there I asked SRE (part of operations) for a date when they would be done with their part. Got that date, operated my part of the project against it, the date arrived and nothing. Two days before the date I had re-confirmed it, and on the date was told, "Well its not quite ready, probably in a couple more weeks." Really? One of the reasons people do 'starter projects' there was to learn this lesson.
The 'tablet' version of Android has been a planning disaster from the moment it was conceived as far as I can tell. Why isn't ChromeOS (basically Android kernel + browser UI) not the tablet version of Android? Android/Tablet vs Android/Phone? AFAICT its because Apple pulled off making iOS work between phones and tablets, and they only pulled that off because they had the iPod Touch for YEARS before they shipped the iPad and kept asking 'what is a non-phone experience like?'
I have no inside knowledge of how the whole 3.x thing went down but if it was like other projects there, rather than get some clear thinkers together in a room and put together a plan and then manage against the risks of that plan, two or maybe three 2 or 3 person 'teams' (friends likely, in their 20% time) probably started working on their vision of how it might work as a tablet, only to be out maneuvered at a review (or not) to have several competing versions going forward which then someone checked in first and everyone else was stuck following that version until someone else checked in something better. Reasoning? Planning? Discussion amongst stakeholders? Probably not so much.
So I would certainly place the underwhelming nature of Android tablets completely at Google's doorstep. Its not like the hardware is less capable than the iPads, in some cases its even more capable.
Its not in Googles DNA (at the moment) to execute against a customer/supplier type of arrangement. Fortunately I think there are some really smart people at Google who understand that, I hope they can prevail against the inevitable corporate anti-bodies that are now doubt even now trying to marginalize them.
I do believe that Android will win here but for the same reason that lava coming out of a volcano 'wins.'
Because native apps are sometimes nice. A tablet that can't play Angry Birds is a hard sell.
Interesting comments about Google's development practices. My impression is that Honeycomb's problems stem from the fact that there was a hard deadline: they wanted to get the Xoom out before the iPad 2. If that's not how Google normally operates, that would explain a lot.
Competing competently in the tablet market is really stretching Google's strengths as a company. I think they can do it eventually, but it's going to be a long learning process.
This.
Also, I've heard that Google developers didn't know the deadline until after the Andy Rubin demo (which was a few month before launch)
Their support has been atrocious, it generally takes 2-3 weeks for a response. When I do get a response they ask for a screenshot despite the fact I've given them the error message verbatim, with error code.
I had to buy x-code4 through the app store because this issue is going on 3 months- still waiting on a refund.
This isn't meant to be an apple bashing post. I'm pissed about these issues, but I don't think it's because Apple doesn't care. I think it's because they are trying to cope with enormous amounts of support tickets and are probably having trouble hiring qualified people to address them. I'm guessing that Google is experiencing a similar problem x10. There's a market demand to get these products out asap, but the infrastructure just isn't ready yet.
Nope: http://gregisdumb.com/2011/02/24/verizon-motorola-xoom-no-lo.... Not even Verizon could get away with screwing their customers that blatantly.
They cost about the same.
Google controls Android 3.0 completely. They very intentionally did not make a source release. Google entered the relationship with Motorola and it damn well had control over who was going to ship a 3.0 device. They knew what they were doing. They HAD to beat the iPad 2 release date at all costs.
So now all we have is a buggy as hell 3.0 OS with no source release and we're still waiting for them to fix stuff. I hope the early release to beat the iPad furthered some other business goal because it didn't further Android as a great Tablet OS.
The flaws I've seen in the device are clear OS and Software issues. So unless your point of view is that it's up to other people to fix Google's fuckups... eh...
I doubt they had to. They chose to, and blundered with the entire world looking at them.
If I were Moto, I would have red-lighted the project some months before deadline, when it was readily apparent that Google wasn't going to deliver a quality stable release on-time.
Competing with the iPhone (and it's carrier exclusivities and high ASP) is one thing, but if you have shoddy product, the iPad is going to wipe the floor with you unless you really offer something unique (ie, eee transformer looks interesting).
Fair enough. Motorola definitely shares blame.
But at the end of the day all that is Android ends at Google's feet. Why play games with holding back the 3.0 source if you don't at least feel you have some responsibility for how Android launches on tablets?
The device has both logos on the back, and they're the same size.
How are you actually arguing with this point? Is it just because this is the internet and fingertips are a renewable resource?
To their credit Google recognized they messed up and are exerting more control but there is no question they share a lot of the blame on the software side here.
Motorola on the other hand messed up with pricing and the late introduction of the wifi only model but I suppose they felt confident after a good showing in CES and good reveiws.
Motorola also got some good exposure and definitely some experience in channels that will be critical in the future.
Apparently, it’s a software issue, but the SD card doesn't work at all. However, this isn’t a Google issue, as other Honeycomb tablets have working SD card slots.
The Android team doesn't seem to give a shit. Ask anyone who has tried to support Android is an Enterprise how bad the Exchange, VPN and 802.1x stacks have been since day one. Business as usual. Their public issue tracker is obviously intended as a space for frustrated users [1] to shout into a bottomless pit of who gives a shit.
I used to be a major Android fan but screw this. If only WebOS was open source...
[1] - Edited to substitute users for customers. Real users are not Google's customers. And the experience shows.