ObjectBox Java (Kotlin, Android) VS WatermelonDB

When I first attempted to publish to F-Droid, I experienced several pipeline issues. After reading through the pipeline logs in GitLab, I realized that my application's database (ObjectBox) was not entirely FOSS compliant and was causing build failures. The following day was spent migrating my app to Room.

I would focus on Kotlin instead of Java, there's really no point in sticking to Java at this point. And when it comes to databases, some local ones that are pretty easy to get into are Realm and ObjectBox, SQLite can definitely be a bit overwhelming at the beginning.

Not sure what exactly the issue is in your case, but linux-aarch64 is already a supported platform for ObjectBox (with some dependencies on libc versions etc). Maybe raise an issue for https://github.com/objectbox/objectbox-java with your specific error output and some details on your setup?

Just to add to this, there's also Realm and ObjectBox as alternatives.

Adding ObjectBox [0] to the list.

[0] https://objectbox.io/

Obectbox

While - strictly speaking - "database" refers to a systematic collection of data, "Database Management System'', or DBMS, refers to the piece of software that provides an efficient and versatile method of working with data(eg: ObjectBox). However, often the term "database" is also used loosely to refer to a DBMS, and you will find most DBMS only use the term database in their name and communication.

Maybe this? I've been looking at it recently.

https://github.com/objectbox/objectbox-java is an alternative to Room.

Here's the issue

Storing the notes: For storing the notes, we will use the amazing WatermelonDB package which is a popular sqlite wrapper for react-native. Instead of using the default package we will use a fork of this that uses sqlcipher instead of the regular sqlite, allowing us to encrypt the database by passing a secret key.

Because most of the libraries I evaluated (RxDB, WatermelonDB) were entirely JS oriented, by design, none could provide a positive API surface in Native code.

never tried it but there is https://github.com/nozbe/WatermelonDB

As title says, is it a good option? There'll be like 60 webp images not some high quality. Or should I add some local db instead, something like: 1. https://github.com/ammarahm-ed/react-native-mmkv-storage 2. https://github.com/Nozbe/WatermelonDB

Watermelon DB.

Significantly improved performance (a lot of optimizations were done, and state management is more scalable by relying on an actual database)

Watermelondb it gives you an ORM, reactivity (when a records changes it cause UI re-render), and easy syncing with remote server, go with that if you don't know SQL that well.

More info here: https://github.com/Nozbe/WatermelonDB/issues/1254

Or WatermelonDb: https://nozbe.github.io/WatermelonDB/