Android developers have been whining about how Google's mobile platform is fragmenting. Get real! Yesterday’s release of Android 2.2 and SDK API 8 will evoke two possible responses from developers:Wow! Twenty new enterprise-oriented features, double the speed for apps, support for Flash and the .Net Framework, better touch reporting, and better voice integration! I can do a lot with that!Oy! Twenty new enterprise-oriented features, double the speed for apps, support for Flash and the .Net Framework, better touch reporting, and better voice integration. What a nightmare to support all this for eight different API levels, with and without Google API support, plus dozens of resolutions and devices with a variety of hardware features, not to mention the two possible UIs and all the national languages! And what about my installed base?[ Keep up on key mobile developments and insights with the Mobile Edge blog and Mobilize newsletter. ]Of course, both responses are correct. But one is a spur to action, and the other is whining about what’s just a fact of life. If you want to write great software for devices, you have to deal with a large variety of hardware and system software. Show me a class of mobile device that has been around for more than a year, and I’ll show you a litany of different device form factors, processors, memory configurations, location sensors, and human interface hardware. Even the iPod Touch/iPhone/iPad family has this, and that’s all coming from Apple.It’s not a problem so much as a sign of a healthy market that so many different devices are coming out for Android. Developers have a choice: Whine about it, or jump in and make something great.This article, “Google Android 2.2: Progress or more platform fragmentation?,” was originally published at InfoWorld.com. Get the first word on what the important tech news really means with the InfoWorld Tech Watch blog. Technology Industry