Lifecycle events in Android. It has been a pain point for Android developers all over the world. It is no brainer that, most of the times the main cause of a memory leak in the codebase is because an invalid state is accessed which is out of sync with the lifecycle of the activity/fragment of the app.

Droidcon Berlin ‘17, Berlin, Germany Abstract As more and more people start building Android Libraries, the whole process of building a better API for developers is getting bloated and everyone is coming up with their own ideas.

DISCLAIMER: If you consider yourself a beginner, intermediate, expert or a ninja in the Android realm, this secret sauce still applies to you. TL;DR: Build Something.

Google Developers Group - Cloud Vancouver, Vancouver, Canada Presentation Event

VanDev: Vancouver’s Software Developers Network, Vancouver, Canada Abstract As more and more people start building Android Libraries, the whole process of building a better API for developers is getting bloated and everyone is coming up with their own ideas.

It all starts when some android developer tries to figure out a solution to a problem he/she is having while building their “Awesome Android App”.

While working on various projects, there have been times when I have had to implement various gesture-based events. Every time I have had to do that I had to write the whole code for getting the SensorManager and getting access to the SensorEvent, plus the extra logic to detect the gesture.

Lets face it we all have been there , trying to fiddle with managing our emulators and dev devices. And at max we would do is try to manually manage it.