Get and read as much example code as you can. You can find the code used in Android programming books on the publishers' sites:
http://examples.oreilly.com/9780596521509/ http://www.wrox.com/WileyCDA/WroxTitle/Professional-Android-Application-Development.productCd-0470344717,descCd-DOWNLOAD.html http://github.com/commonsguy/cw-android Plus many more than those listed above. Pretty much every book has a code download site. Book authors make an effort to write readable code. But there isn't that much to be done about the fast rate of change in Android. (In fact, one thing you will find is that example code projects are often for earlier SDK versions, and you have to update or re-create the project.) Google doesn't make hardware, so if they want to catch up to iPhone's numbers, they are going to make more software. I don't expect the pace of change to slow down soon. The SDK has gotten more friendly to targeting multiple API versions, and other rough edges, like XML editors, continue to improve - there is some upside to rapid change. I think you are right that Groups is a less-than-ideal format for code questions. Stackoverflow and O'Reilly Answers have a more structured format for questions and answers. -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
