Didn't think of it that way, but they would be correct if that was the case. 2.3 and above is easy enough to code for with the compatibility library. 2.2 is mostly okay, unless one wants to use something like the download manager api added in 2.3.
Which has nothing to do with what Meaty said. Target 2.3 and progressively enhance for 4.0 if you need/want to. I see the other comment already pointed this out. Saying it's fragmented is like saying Windows is fragmented because users are on XP, Vista, 7 and 8 in significant numbers. Or OS X is fragmented because there are a block of users that effectively refuse to upgrade. Or his own example of WP... you have to be conscious about what you're targeting.
It's just a silly excuse to try to slander Android and I'm tired of people like meaty using "fragmented" to try to make some sort of "point".
I agree with you of course with your clarification now :).
I just misinterpreted your context to mean you were calling in question how many users were on which OS. Android fragmentation is much overblown by those that have probably never even tried to build an Android app. Especially if one is targeting 2.3+. I generally target 2.2 and above without any issue.
If I do run into issues, it's really because I'm playing around with things that were never intended to be messed with (reflection or things that require root). Neither of those two examples are fair to blame on Android though.
Says Google, with 45% still using 2.3. Also, all my apps outside of ones for root users are still a majority of 2.3 users.
http://developer.android.com/about/dashboards/index.html