C'mon, man. This is flat out false information.

I appreciate your efforts, but I don't think you understand what 'fragmentation' means.

Each API level brings new functionality, and each new release brings added stability/performance improvements FOR THE ENTIRE PLATFORM. Depending on the app, the developer may choose to target 2.1 because they don't need the features associated with the API level in 2.3 (API level 10). In fact, developers can target 1.6 if they want (API Level 4) if they don't need the classes in higher levels. There are a bunch of apps that do this.

There are also backports. For example, the HC/ICS UI that everyone is so horny about, has been backported as far as Android 2.3 (AFAIK). This means that pretty much everyone has access to ICS apps so long as they don't include API objects exclusive to API Level 14.

It is thus up to the developer to determine what his/her app needs and then release accordingly knowing the market. Were I developing an app tomorrow that didn't need HID Controllers or NFC, I might just develope for the v2.0 API level. But that wouldn't mean my app would run slowly by any stretch.

Android has a HIGH degree of different architectures to support with the OS. This is very different than the single-SKU Apple, or the we-choose-the-hardware-for-you Microsoft strategy. And Android handles the problem of compatibility masterfully given the market. Sure, not every app will be available for you to use in the market if you buy a device, but before you echo the herd with the 'fragmentation' claim based on OS versions numbers, I would first a) understand what you're talking about, and b) get real statistics that demonstrate compatibility across all platforms to find out where devices actually stand.

Yes, ICS was unveiled a week or so ago. But that doesn't mean for an instant that devices released a year ago suddenly stop working with apps, nor does it mean that they will lose relevance in 6 months.