Are Bad Manufacturer Overlays a Thing of the Past?
summary
This talk examines how manufacturer Android customizations can remove or alter expected APIs (e.g. missing StringUtils, enums failing to parse JSON), quantifies how many users are affected, and proposes a three-step remediation: detect crashes in production, reproduce issues without buying devices, and patch plus notify users. It describes concrete tooling and methods used: Fabric for crash detection, device clouds/manual device farms for reproduction, and Intercom for messaging so teams know which phones, OS versions, and fixes actually restore user sessions.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:00Overlay problems examples
- 7:22Samsung overlays error stats
- 10:10Tools to detect crashes
- 13:24Crash responsibility best practices
- 16:35Operator overlays solutions
- 19:48Update feedback management
- 22:00Bug fixes responsiveness
- 23:04Conclusion
related talks
38mThe State of Mockodile in 2018
48mFramework Fireside Chat
35mWhen Security is not a Developer's Fault
38mBreak your App before Someone Else Does
34mDon't Kill My App: Android survival guide
37mHow to survive on Android and don't get killed
24mModern Android App Security: Protecting Code, Keys, and Data
30mDoes your Android app expose you to excess risk?