title: Architecture of Android application with simple database
body: <p>I want to build a fairly simple Android application.
  The basic data model of my app consist on several basic elements with relationships between them.</p>
  
  <p>I want the data to be persistant so I'm thinking about using an sqlite DB.
  I looked at the Android Developer website, and the closest thing that I could find that is relevant to my question is the "NotePad Tutorial" which make use of an sqlite DB to store notes.</p>
  
  <p>I think by now I got the handle on the basics, but I still have some questions though:</p>
  
  <ol>
  <li>In the tutorial they have only one table in the DB. If my application requires a more complicated scheme - should I still use the same method? that is - putting everything inside a subclass of <code>SQLiteOpenHelper</code>? Or is there a more "structured" way to go?</li>
  <li>Should I bother creating classes for all the data elements stored in my DB? I mean this is what I learned that I <strong>should</strong> do, but in the documentation there is no hint about that.</li>
  <li>If I Should create classes - How should I use them correctly? I mean, since the result of the query is a <code>Cursor</code> object, and not a collection of rows, Should/Can I parse that into objects?</li>
  </ol>
  
  <p>Thanks!</p>