Reporting memory leaks in APIs on Android

It’s easy to leak memory in Android as we often hold references to Views and Activities; when developing do you find the LeakCanary popup annoying?

If you are developing an API where your clients must bind and unbind with their observers, then wouldn’t it be better if you could reduce the chance of misuse?

--

--

--

Matt Dolan has been eating doughnuts and developing with Android since the dark days of v1.6.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Android in Depth [Noob Friendly]

Look Deep Into ViewPager2

Exploring the Salesforce Mobile SDK Using Android Studio

Android Tutorial Part 2: Using Apollo library to fetch data from a GraphQL endpoint

Fragment and constructor dependencies

Android Image Slider Application Tutorial using View pager and fragments.

Introducing android common Palettes

Jetpack Compose Drop Shadow Text Effect

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Matthew Dolan

Matthew Dolan

Matt Dolan has been eating doughnuts and developing with Android since the dark days of v1.6.

More from Medium

Integrate Version catalog in Android

10 ideas to improve your Gradle build times [Part III]

Security in Android 12 — For Developers

Exploring Android 13: Programmable Shaders