~/talk

How to Build Performance-Driven Android Apps

TalkinJapaneseat DroidKaigi 2016 · 2016-02-18..02-19· [android, web-performance]
name:t.egg
links:none on file
slides:none on file

How to build high-performance Android apps by measuring real device behavior: always test power on battery (unplug or simulate via ADB), inspect power_profile.xml in framework-res.apk, and use dumpsys battery with Battery Historian and adb bugreport to get per‑percent drain timelines (example: Nexus 5 camera LED ~540mA ≈ 4 hours on 2300mAh). Find UI jank using GPU rendering profile, dumpsys gfxinfo, and systrace; detect overdraw with Developer Options and HierarchyViewer; and locate memory leaks with LeakCanary or heap analysis tools.

AI-written summary · about

  1. 0:00Introduction
  2. 5:35Performance principles
  3. 7:20Power settings
  4. 12:45Power consumption axes
  5. 17:27Battery history
  6. 21:07Background processing
  7. 23:39UI performance metrics
  8. 26:1360FPS rendering
  9. 29:26Rendering delay causes
  10. 31:51Overdraw detection
  11. 35:21GPU rendering profiling
  12. 39:00Network memory optimization
  13. 41:53Memory leak detection
  14. 44:45CPU optimization tools
  15. 46:32Summary
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.