title: Android coding best practices/design patterns
body: <p>In a recent question I asked I was directed to this website: <a href="http://developer.android.com/design/index.html" rel="noreferrer">http://developer.android.com/design/index.html</a></p>
  
  <p>Amazing site, but it didn't answer one particular question: What are the best practices/design patterns to apply in the design of an application code-wise?</p>
  
  <p>I did lookups for MVC/MVP, etcetera, and while that yields results, it's only about the actual implementation of said patterns, rather than other available options and such.</p>
  
  <p>I tried decompiling and analyzing various apps Android installs by default, like the Market, but I couldn't really find a structure in Google's code. Does anyone have tips on how to setup Android apps in such a way they are maintainable, extendable, etc. I am aware of the wide meaning of these words and that they are purely subjective to the programmer for that matter, but I can't express it any differently.</p>
  
  <p>One best practice I already encountered is one view per Activity and having lots of Activities in the app for the backstack to work properly, but other than that, I have no clue how to actually setup the Activity itself.</p>