Can anyone point to a good source or come up with a brief listing of conceptual android programming DONT's when designing an App?
I dont want my question to be vague, so I'll give dummy examples(which might not make any sense or may be completely incorrect) to explain what kind of answers I am looking for are things like :
Eg: Avoiding these help you design/program robust android apps
- Dont acquire wake locks when waiting for a server response OR Dont have this logic in OnReceive of a broadcast listener...
- Extending IntentService is better than extending Services in blah blah scenario
- Dont create threads inside OnDestroy() for activities... etc etc
I hope you got the point. I know these could be infinite do's and donts but I am looking for the most important basic ones that a beginner/novice should keep in mind so that they good be better android programmers.
Thanks!
EDIT
By Design I mean both the programming(logic) as well as the UI and not the look and feel alone.
Infact more importantly the ones that comes with experience and are not mentioned in books or tutorials because of the nature of these principles/tricks. They might not be absolutely right or wrong but are better or worse. Because they will not teach you a new concept but will help you get rid of a bad programming/design habit.