Although mobile apps do not rely on databases as much as, say, web applications, mobile app developers should still be interested in databases. There are better database solutions for Android apps than a native SQLite library; we’ll nominate ORMs as one of them. In this article, we’re going to take a look at some of the most popular Android ORMs: ORMLite, ActiveAndroid, greenDAO, and Sugar ORM. We’ll also check out our new Vertabelo Mobile ORM.
When developing an application with a SQLite database as a persistent storage, it’s worth it (or necessary, in fact) to know some low-level details like: where the data is stored physically and how we can determine if its structure is really the same as what we expect it to be. Being familiar with these things makes it easier and faster to develop, as well as find and fix bugs. I'll try to explain some of the most frequently asked questions regarding SQLite databases.
In the previous article we wrote a simple Android app allowing the user to manage his ToDo list. We showed how to create an SQLite DB in an automated way and how to do some simple CRUD operations on it. Let’s say that the first version of an application is released and people use it. Now, after some time, we decided to improve the app. Our goal is to add the ability to prioritize the tasks. What do we need to do?
Indisputable fact is that Android, together with iOS, dominates in the mobile devices’ world. This made me think that it may be worth writing a few words about how to create mobile applications for these two mobile platforms. But not the kind of “hello world” applications – there are plenty of tutorials about that. I’d like to focus on the use of local SQLite databases.
I’m gonna show you how to develop a simple web application. From database design to deployment and finally some front end development. Everything will be made in the cloud. There will be no need to install anything on your laptop. Sounds like late night TV commercials? But it’s not :).
Let’s start with the database design.