Persisting data when writing android applications is something you get to do a lot as an android developer.
While the android sdk offers a variety of ways to persist data, each has it's shortcomings (even the one I am about to propose and have used) Android Data Storage Options
The seemingly most reliable and most used would be the SQlite Database storage option. But as with everything, some of us just would rather prefer to write code than write a single line of SQL query. This is where ORM abstraction layer options come into play.
An ORM (Object Relational Mapping) solution is one which offers a way to persist data with little to no knowledge of SQL Queries while providing a level of abstraction for the developer to interact with the persisted data.
I for one would recommend the Sugar ORM for Android because of its simplicity and ease of setup. I know there a few other ones but I just recently worked with Sugar and I find it pleasing for now, till I discover a "better" one.
A simple introduction and setup guide can be found at Sugar .
I know it would help. :)
I am not recommending a particular method of persisting data. That is best decided by the developer. ;)