On
Kotlin Dependency Injection with zero setup and zero boilerplate code (by Queatz)
persista
Small kotlin library for persisting _single instances_ of kotlin data classes (by erdo)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
On
Posts with mentions or reviews of On.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-31.
-
Any good examples of manual dependency injection?
Here's a lib I made to use in my Android projects, it's so hard for me to ever use anything else because of how simple it is
persista
Posts with mentions or reviews of persista.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-31.
-
Any good examples of manual dependency injection?
I use manual DI whenever I don't want to force Koin or Dagger on a project, or I want to keep things super simple. This method gives you either single instance or factory, no lazy initialization, and no scoping (you'd have to add the ViewModel scoped stuff) simple app that has it: https://github.com/erdo/persista/tree/main/example-app/src/main/java/foo/bar/example (dependencies constructed here): https://github.com/erdo/persista/blob/main/example-app/src/main/java/foo/bar/example/OG.kt (getting the dependencies into your UI here): https://github.com/erdo/persista/blob/main/example-app/src/main/java/foo/bar/example/ui/wallet/WalletsActivity.kt ``` private val wallet: Wallet = OG[Wallet::class.java] ``` another larger app example: https://github.com/erdo/apollo3-android-sample It looks quite like a ServiceLocator but the difference is these things are not statically referenced and can easily be mocked in tests
-
New Android Dev Sanity Check
If you actually want to serialize your data structures to a json file, I wrote a library to do it here https://github.com/erdo/persista bit it's really just one class, feel free to copy bits of it
-
Do you use SharedPreferences?
I ended up doing something similar to store data classes because I wanted something in pure kotlin ( https://github.com/erdo/persista no encryption though).
-
library to persistently store kotlin data classes
I did a library, it lets you store single instances of kotlin data classes persistently with not much effort / boilerplate https://github.com/erdo/persista
What are some alternatives?
When comparing On and persista you can also consider the following projects:
androidx - Development environment for Android Jetpack extension libraries under the androidx namespace. Synchronized with Android Jetpack's primary development branch on AOSP.
leakcanary - A memory leak detection library for Android.