leakcanary VS sunflower

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/

Here is full code

https://github.com/android/sunflower?

If you want to open a project in Android Studio, you need its original source code. For instance, go here, then click Code > Download ZIP.

Technically the 2019 version of this repo https://github.com/android/sunflower/tree/5d5dd9e1f0bee1ef506d70aaacf21fe893a9fb83 was significantly less clear than newer versions.

Check out their example of the perfect app https://github.com/android/sunflower

Like looking at Google's android/sunflower app... I see it and it see how they are all divided viewmodel/fragment/workers but what should I be paying attention to when looking at sample apps to learn ?

Lastly, the problem with dig around is, my team is starting a project from scratch so there is nothing to reference. Android at least have some "best practice" example to follow (https://github.com/android/sunflower) Is there something like that for Spring?

After you are quite proficient with the framework, this time you should discover new things. The most trusted source is the samples from Google, for example, Sunflower