Android 2.2+ is not that bad, feature-wise. And with the release of several compatibility packages, it's rather easy to make app that run on more than 90% of the available Android devices.
APIs haven't changed that much from 2.2 to 4.0, for the design you can easily implement your own, and with the introduction of Fragments it's even easier to make apps that look good on both phones and tablets for Android than for iOS.
Yes, you can't negate that Android has a fragmentation problem, but it's not as bad as it used to be, or most people would like you to believe.
If you want to use the ActionBar UI style then there is a library that will work on Android 1.6+ using the native one when available else an emulated one.
What he is saying is that you can develop with current APIs fpr 3.0 or 4.0. And still use those to make apps for 2.x. Because many of the newer APIs were made backwards compatible (such as fragments). Android allows you to build a 4.0 tablet optimized app that is also backwards compatible to a 2.2 phone optimized app, while reusing a lot of code and even layout between them.
APIs haven't changed that much from 2.2 to 4.0, for the design you can easily implement your own, and with the introduction of Fragments it's even easier to make apps that look good on both phones and tablets for Android than for iOS.
Yes, you can't negate that Android has a fragmentation problem, but it's not as bad as it used to be, or most people would like you to believe.