ObjectBox Java (Kotlin, Android) VS koin

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

Let's see how we can use Koin to achieve Dependency Injection (DI) and incorporate a third-party iOS Swift SDK in a KMM project. Koin supports KMM development, making it the ideal choice for KMM projects.

Might want to tell koin that : https://insert-koin.io/

New modules allow you to easily build KVision apps with the Ballast opinionated application state management framework. You can see how Ballast (together with Koin) can help you design your application architecture in the new todomvc-ballast example.

I started looking into using Kotlin/JS, and hopefully reusing a bit of code that I have, which is using Dagger and Anvil - which of course are JVM only. So I've been looking for other solutions, namely Koin and Kodein. Koin's multibinding support is... not really amazing (e.g. here, and while Kodein does support multibinding, it doesn't seem to support things like that at the declaration site - everything needs to be specified in a "DI container" (module).

Koin

It's a Koin issue, not compose. Discussed here https://github.com/InsertKoinIO/koin/issues/1079

Now I will finish up saying Hilt is just an opinionated way to dependency injection on Android, but there are simpler frameworks out there such as Koin or Kodein that can help take away a lot of the troubles that can come when you try to make your own framework. Just know that most other frameworks tend to be runtime injection instead of compile time injection like Hilt, which can be helpful to know at compile time if you are missing a dependency in your graph as opposed to runtime when its out in the wild.

I've been using Angular a lot and I like how it works. I'm also a huge fan of koin for kotlin.

for injection, I suggest Koin (https://insert-koin.io/)