Guava as dependency is not terrible but pretty big dependency for mobile project. Maybe a bit too wide, but seems great for some specific applications. MapDB - very popular, written in Kotlin and wide range of functionalities.The only issue: it wasn’t updated since November 2016, but for such small library that might not be a bad sign - possibly it’s so simple that it just works without any fixes. Uses Kryo for serialization, so there is no need for changes in model! Also supports encryption which is always a good thing. WaspDB - not very popular but actually pretty simple, getting-job-done library.There are so many possibilities that we can be pretty selective. If there is some red flag, I just give up on this choice. Some evaluations are very superficial, because testing or reading into every library would be tedious and - to some extent - pointless. Of course this list does not contain ALL possibilities, but should contain most libraries you could ever find looking for NoSQL on Android. And easy to compact to basic data type such as String.īut let’s get to NoSQL libraries. In short - SharedPreferences can be totally used as basic storage, as long as stored data is relatively small. User „mani” from StackOverflow reports that he/she got memory exception when data saved in SharedPrefs exceeded 1428.51 kB which sounds reasonable. And as the whole file is read to memory, it’s memory that might limit you first. BUT in practice - they are saved as XML files, so they are not efficient for bigger values. Theoretically SharedPreferences don’t have a limit - they can contain the longest possible String in Java. When talking about key-value storage, what Android Developer website suggests? SharedPreferences of course! I can’t omit this topic, because it’s actually not a bad idea.
#Android idatabase for android#
Now it’s time to discuss what possibilities there are for Android platform. In the previous post I discussed WHY would you like to use NoSQL database on Android.