I found this article, The Curious Case of Android UI Development, while getting my head around moving from iOS UI development to Android, as I am now doing UI work on the upcoming Alpha release of Serval Batphone. My favourite quote is :
“Though a bit of a well-worn topic, it is worth mentioning the development “culture shock” experienced by those coming from the iPhone world armed with tools like Interface Builder for all its shortcomings to Android-land where we are left with the technological equivalent of sharpened sticks and smooth stones. “
He isn’t wrong. I have come to the conclusion the underlying Android code is easier to work in than iOS (that may be my open source fan girl speaking, Objective C isn’t my favourite after all), but the tools available for UI development, which is my area of interest, are ‘teh suck’. Which is geek speak for they suck. I do like Balsamiq for general wireframing (I use iMockup on my iPad, and love that too. DroidDraw is incredibly dated feeling. If anyone has any other tips, I am open to them!
A couple of good links, btw :
- Ignoring the Android Honeycomb Action Bar Convention (disambiguity.com)
- Android Wireless Application Development (2e) (i-programmer.info)
- Prototyping (geekwarrior.net)