Hi, Has anyone started cataloging common design patterns that arise when developing Android apps?
For example: It's worked out well for me to create a base class that extends Activity that all of my other activities extend, so I have a central place to put common functionality. When should strings be listed in values/strings.xml and when should they be hard coded? What kind of conventions should be used when giving views ids? Should there not be views in different layouts with the same name? Etc. Cory -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
