LOL catz...


The rumors suggest that you're supposition was correct. If 3.1 is to include phones, then it implies that 3.1 is a more polished release, as Android was supposed to be platform agnostic from the start (eg. dalvik, display density). It seemed as though 3.0 was rushed to market, and even Andy Rubin commented that they cut corners to make the release -- hence no releasing the source.

The speed at which android is iterating, I suspect we'll be hearing something at Google IO, which is around the corner, I might add. I expect that Google has been going full-steam on polishing 3.0 and that the 3.1 release will be quite significant.

I think the original iteration speed served the project better than the intentionally slowed iteration speed. It seems as if the Android project has problems setting an appropriate timeline for their goals -- Honeycomb should have been functional upon release. The shorter release schedule allowed them to release as quick as things were complete.


Ditto. In fact, for so many of these 'apps' that rely on cloud-services (I don't care who hates that word), I would rather see a competent web app. HTML5 can't get here soon enough.

That begs the question: how compliant is Android's stock browser when it comes to HTML5 tech and standards like webGL?