Downloaded 173 times
Uploaded byBoris Farber
10 ways to improve your Android app performance
The document provides 10 tips to improve Android apps: 1. Avoid activity leaks by removing references to activities and using event buses instead of static references. 2. Be careful of inner class leaks and use weak references for handlers. 3. Only perform UI work on the UI thread and use libraries for network, images, JSON, and databases. 4. Consider using libraries for common tasks like HTTP requests, image loading, and JSON parsing to avoid reinventing the wheel.
More Related Content
![Dark Side of iOS [SmartDevCon 2013]](https://cdn.slidesharecdn.com/ss_thumbnails/smartdevconpresentation-130913064401-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
![[충격] 당신의 안드로이드 앱이 느린 이유가 있다??!](https://cdn.slidesharecdn.com/ss_thumbnails/consalad-iiiwooseopandroid-performance-190316143236-thumbnail.jpg?width=640&height=640&fit=bounds)
10 ways to improve your Android app performance
- 1. 10 ways toimprove your Android app Boris Farber @borisfarber
- 2. ● Long launchtime ● Janky scrolling ● Unresponsive app Data intensive apps
- 3. IF YOU HAVEA SMALL APP FORGET THESE SLIDES
- 4. 1 - Activityleaks
- 5.
- 6. ● Holding referencesto unused Activity ● Activity holds its layout ⇒ holds all views
- 7. public class LeakActivityextends Activity { // ... @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); NastyManager.getInstance().addListener(this); // ... Listeners leak
- 8. @Override public void onDestroy(){ super.onDestroy(); NastyManager.getInstance().removeListener(this); } Listeners leak + fix remove listener
- 9. ● Activities/fragments etc- they have a life cycle ● Activity will not be GC-ed ● Static references ○ become dangling "pointers" ○ m_staticActivity = staticFragment.getActivity() Static References
- 10.
- 11. 2 - Activityleaks
- 12. Outer class (Activity) Innerclass (Handler)
- 13. public class MainActivityextends Activity { // ... Handler handler; @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); // ... handler = new Handler() { @Override public void handleMessage(Message msg) { } }; // ... This is a leak
- 14.
- 15. private static classMyHandler extends Handler { private final WeakReference<MainActivity> mActivity; // ... public MyHandler(MainActivity activity) { mActivity = new WeakReference<MainActivity>(activity); // ... } @Override public void handleMessage(Message msg) { } // ... } This is a leak + fix
- 16. Outer class (Activity) Innerclass (Handler)
- 17. ● Non staticHandler → Activity leak ● Both classes have a different a different lifetimes Prefer static to non static inner classes
- 18. ● Remove awaystatic references ● Use event bus ● Unregister listeners ● Prefer static inner classes to non static ones Avoid Activity leaks
- 19. ● Do codereviews ● Understand your app structure ● Use tools (MAT ...) ● Print logs on callbacks Avoid Activity leaks
- 20. 3 - UseUI thread only for UI
- 21.
- 22. ● Images ● Networking ●JSON ● Database access Not on UI thread
- 23. ● Images ● Networking ●JSON ● Database access Not on UI thread Use libraries Use Loaders
- 24. 4 - Uselibraries
- 25. ● Already solvethe problem ● Requires specialization (easy to make mistake) ○ Threading ○ Memory ○ Networking ○ Images Use libraries
- 26. ● Don’t losefocus ● Developer your solution for a good reason Use libraries
- 27. ● Volley ● OkHttp ●Retrofit Common libraries - Async Http
- 28. ● Glide ● Picasso ●Fresco ● UIL Common libraries - Image loading
- 29. ● Solves yourproblem ● Plays nicely with your current dependencies ● Dex method count ● Dependencies ● Maintenance ● Runtime permissions Pick 3rd party lib checklist
- 30. 5 - LargeJSONs
- 31. ● Parsing hasa performance effect ● Converted to class with getters and setters JSON
- 32. ● Small JSONs- GSON is the best ● Large JSONs ○ Jackson ○ ig-json-parser ○ GSON + immutables type adapters JSON
- 33. ● Keep UIthread only for UI ● Understand concurrency APIs ● Use libraries (memory, caching, json ...) ● Use loaders Scrolling
- 34. 6 - Systemabuse
- 35. ● Don't callprivate APIs by reflection ● Don't call private native methods (NDK/C level) ● Don't use Runtime.exec ● "adb shell am" to communicate with other process is not something we want to support System abuse
- 36. ● Don't abusethe system ● Know and use APIs System abuse
- 37.
- 38. ● API willbe removed ● Your app will not work ● No way to update APIs and tools Deprecation
- 39. ● There isa compelling reason to move ○ Security ○ Correctness ○ Performance Deprecation
- 40. ● Removed atM (still available as dependency) ● Use HttpURLConnection ○ Simple API ○ Small size ○ Transparent compression ○ Response caching Don’t use Apache Http Connection
- 41. ● Know anduse APIs ● Refactor your dependencies ● Update your dependencies and tools Deprecation
- 42. 8 - Bringyour own gloves
- 43. ● Various versions,devices, OEMs ● APIs and libraries shipped with platform might behave differently ● Async task ... Bring your own gloves
- 44. ● Consider bundlingyour own version ● Check dex limit ● Check code bloat Bring your own gloves
- 45. ● Own wrappedlibrary (SSL/crypto etc') ● Rooted devices ● Your own sensitive data/protocols Security
- 46.
- 47. ● Activities ● Fragments ●Tasks ● Flags ● Add logs on callbacks Understand app components life cycle
- 48. ● Consistent ● Getpeople on board quickly ● Have someone experienced ● Pick your dependencies wisely What can you do
- 49. ● Sleeping mostof the time ● Responsive when “awaken” Design your app
- 50. 10 - Knowyour APK
- 51. ● https://goo.gl/94woV7 ● Executablesbrowser ● Innovation comes from frustration ClassyShark
- 52.
- 53. ● Dex limitnumbers ● Obfuscation ● Package counts ● Why I need the dependency Know your executable
- 54.
- 55.