The outpour of response we received from our first round of Android Design Guidelines was surprising, but hardly unexpected. When you look at the disparity between the number of Android users in the market compared to number of great design resources to produce apps for them, it’s no wonder designers are hungry for fresh, thorough resources. But Version 1 didn’t really satiate the appetite for Android design assistance as much as it did whet it, and hundreds of designers from around the globe have been writing us asking for the next logical step: Honeycomb.

Honeycomb was arguably one of the biggest landmarks in the tablet landscape since the birth of the iPad. This operating system re-approached the usability of the tablet computer, and made iPad’s screen full of sweeping fields of apps look downright silly.

And yet Honeycomb and the Xoom, the first tablet running the OS, can hardly be declared a success. In fact, Steve Jobs himself put it best when he stood on stage to unveil the iPad 2 and showed the 65,000 apps designed to run on iPad and a whopping 100 for Honeycomb. Honeycomb needs a thriving app community to support it, and designers need to step up to the plate and take on the iPad’s biggest challenger.

The Android Design Guidelines Version 1.1 introduces some of the OS’s unique new features such as the Action Bar and Notification/Status bar along with how to utilize new UI elements like Fragments.

As we said last time, these guidelines are a living document and will continue to evolve as the platform evolves. We hope designers will use this tool to continue to innovate in Android design and help Honeycomb evolve into the enterprise tool it could be. Let us know how we can improve this guide and what resources you’re using to push Android design further.

Download the Android Design Guidelines Version 1.1: Honeycomb

Android Design Guidelines 1.1