title: Android Package Structure Best Practice
body: <p>I have a question regarding best practices for application package structure.  </p>
  
  <p>I watched Reto Meier's Google I/O 2011 presentation <a href="http://www.google.com/events/io/2011/sessions/android-protips-advanced-topics-for-expert-android-app-developers.html" rel="noreferrer">"Android Protips: Advanced Topics for Expert Android Developer</a>s" and read his blog post "<a href="http://android-developers.blogspot.com/" rel="noreferrer">A Deep Dive Into Location</a>" and noted his application package structure of:  </p>
  
  <p>com. ... .content_providers<br>
     com. ... .receivers<br>
     com. ... .services<br>
     com. ... .UI
     com. ... .UI.fragments<br>
     com. ... .utils<br>
     com. ... .utils.base  </p>
  
  <p>Is this the preferred structure for packages?  Is there a better structure?</p>