[Eee Pad Transformer Themes and Apps] maxpower47:
Misleading

There are several things mentioned in the article (like every other article decrying the state of HC apps) that are false or misleading:

Of course the iPad has been out for a full year longer, that number was much lower three months after its release (which is approximately how long its been since the Xoom was released). It looks like it was about 10,000 based on a quick googling. That's quite a big difference from 100,000 (like, an order of magnitude).

There is also the question of how they are counting these "Honeycomb-optimized apps". There is no provision in the market, or in the metadata that describes an app to determine if it is "optimized" or not. Unless a developer explicitly denies the app for a certain screen size, a certain device, or requires a feature that the device doesn't have, then it will most likely run. If its just a question of "will it run?" then we have tens (maybe hundreds) of thousands of Honeycomb apps. Beyond that, where can you draw the line to say that an app is "optimized"? This is a subjective question that can't be used as the basis for such an empirical evaluation.

I can offer my own apps (linked in sig) as an anecdotal example. Both worked on day one on Honeycomb, with no changes needed. All the text and graphics were crisp, clean and appropriately sized. They did not look ugly, just not as efficiently designed as they could have. Shortly after HC dropped, I updated them with a minor change to make use of the native Action Bar in HC for menu items. The rest of the UI (mostly list views), while great for a small phone screen, wastes a lot of space on a tablet screen that is several times larger. I'm currently working on refactoring the UI components into fragments, to improve the HC experience. At this point, all the fragments are in, and working, but I have not yet implemented a new activity/layout for HC devices which will make use of the extra screen space to place multiple fragments on the screen at once. At what point is my app then "optimized"? Day one (when it worked)? Once it made use of the action bar (more consistent UI)? When it was refactored into fragments (easier to detect this automatically)? Or when I add separate layouts that make use of a larger screen's real estate (most of us would say this is "optimized", but the point is we don't have any way to tell besides looking at it and making a judgement).

As long as fonts are specified in "sp" (scale independent pixels) units, this happens automatically.

Nope. Having different resources for different screen densities or sizes is well documented and as easy as putting them in specially named folders. This was already done to make apps look good on LDPI, MDPI, and HDPI devices. It does increase the size of the app, but it will have virtually no performance penalty.

Even if this were true, its not the release of ICS developers are waiting on, but the point where adoption is widespread enough that they can safely drop support for previous versions (this wont happen for quite a while, as we've seen from the last several releases of Android).

To the author's credit, they acknowledge this and state that none of the developers they talked to felt this was a roadblock, but I have seen other articles promoting this idea.

This article was one of the more fair and balanced looks at the subject I have seen, but still upholds some myths about Android app development. The fact is, most any app that was built following the Android UI guidelines worked and looked fine without any changes for Honeycomb. Their UI may just not have been the most efficient for a tablet sized screen. In comparison, iPhone apps, using the 2x scaling on the iPad, look pretty terrible. This, combined with faster hardware adoption by consumers, is what prompted developers to port more apps to the iPad quicker than we are seeing for Honeycomb. The fact that my apps looked "good enough" on HC is why I didn't feel like there was much of a rush to put in the work to "optimize" them. Google made the right call by making Android as resolution/density agnostic as possible, as opposed to iOS's initial assumption of a single screen size and resolution. While iOS developers had to scramble to get iPad optimized versions of their apps out quickly, Android developers are able to take their time and (hopefully) do it right. There will be more HC "optimized" apps, as more tablets are sold, and more developers decide its worth their time to invest in it.