persista VS leakcanary

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

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

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).

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

If your app exposes a LeakCanary Launcher activity, you will be able to quickly access it through the App Details bottom sheet.

Highly recommend you try out Leak Canary https://square.github.io/leakcanary/

First of all, grab the LeakCanary to check if you actually have a leak. Because just the memory increasing might be completely unrelated to your ViewPager.

It's strictly mContext otherwise it won't work as intended.

Knowing when root views are detached, e.g. to detect if they might be leaking (LeakCanary).

https://github.com/square/leakcanary + don't try to over optimise. In the end R8 / proguard / art runtime will do so many change between what you write and what actually is done that you may be loosing time doing something that the tools does for you.

LeakCanary

LeakCanary will help you find memory leaks in your code: https://square.github.io/leakcanary/