> One could argue that Google needed to keep Android development in-house, so that it could keep up with the incredibly fast-paced smartphone marketand that may be true. One could certainly point to MeeGo as a counterexample of sorts, and one that has yet to really produce any tangible results in the form of products for sale.
It's not a counterexample. MeeGo's equivalent to Honeycomb -- the tablet version of its UI -- is its "MeeGo Tablet UX", which it's been demonstrating at conferences repeatedly (although they've thrown it out and started from scratch a couple of times) for the last year, e.g.:
and which.. doesn't have any source available, as you can see looking at http://meego.gitorious.org/, and has never had any source available. So, MeeGo is just as culpable as far as developing in private, and moreover MeeGo's closed-source periods appear to be *longer* than Android's.
Maybe I'm missing something? I'm seeing lots of "Android sucks, I'm switching to MeeGo" posts (on identi.ca, mainly) since the Honeycomb announcement; I don't know whether I'm mistaken about how MeeGo actually works or everyone else is.