Please log in to watch this conference skillscast.
In this talk, Kumar Rangarajan covers the various aspects of an Android apps performance, including what causes power consumption issues for an app and what are the best practices to help reduce it, best practices for bandwidth management, memory management, and much more! Also covered are the tools out there that can help, including Little Eye.
Do you know the #1 reason why customers uninstall apps? It's when they are frustrated with its performance.
If your app is functionally deficient, it just gets relegated to the background and you still have a chance to update your app and figure out a way to get him or her back. But research has shown that if users find their app behaving badly by draining power, crashing often, consuming too much bandwidth or just slowing down the system, they will uninstall it in a blink and you have lost them for life!
If developers had a good sense of how their app was behaving internally, as they have on how it behaves externally, many of these frustrations could be avoided.
YOU MAY ALSO LIKE:
- How to instantly Analyze your apps performance before release (SkillsCast recorded in October 2013)
- Fast Track to Android Architecture (in London on 21st - 23rd October 2019)
- Real World Kotlin Development Workshop (in London on 22nd - 23rd October 2019)
- droidcon London 2019 (in London on 24th - 25th October 2019)
- iOSCon 2020 - The conference for iOS and Swift Developers (in London on 19th - 20th March 2020)
- Clean Architecture using BLoC & Voyager: DI & the Widget Router (in London on 21st October 2019)
- The Sonic Contender (in London on 28th October 2019)
- Cleaning the Big Picture: Creating Maintainable Mobile Games in Haskell (SkillsCast recorded in October 2019)
- Design to code. Meet Supernova. (SkillsCast recorded in September 2019)
Understanding the What and How of Android App Performance
Kumar Rangarajan is the co-founder & chief ion @ little eye labs, a Bangalore based startup. He has over 17 years experience in the industry and most of it was spent in building developer tools.