Slides for my talk at the Airbnb Android meetup: https://www.airbnb.com/meetups/q2d349kde-android-frameworks-from-airbnb-and-square The Square Register Android app has few crashes. Getting there requires a systematic approach: coding defensively, gathering information, measuring impact and improving architecture. This talk presents our concrete steps towards lowering the crash rate, from the general philosophy to the tools we use, together with real crash examples.

1. Crash Fast
Square’s approach to
Android crashes
Pierre-Yves Ricau / @Piwai

12. Fixing requires reproducing

13. Support
Static info

14. History: high level log

15. Current state

19. Heap
Bitmap

20. Heapdump

21. Dev crash handler

23. WIP: detecting leaks

25. Exception
=
something unexpected
happened

26. Defensive programming

27. Offensive programming

28. Crash fast

30. • Integration tests
• Manual tests
• Internal release
• Beta
• Progressive Rollout

33. • Reproducing => fixing
• Static info + history + state
• Crash Fast
• Progressive rollout

34. Questions?
cash.me/$hit
!
@Piwai