Performing Due Diligence as Android Developers
summary
A practical checklist for bringing third‑party Android SDKs into production that claims to catch hidden costs before they hit users and build pipelines. It maps a five categories framework: docs and licensing, integration (AAR/Maven, ProGuard, version history), UI customization and localization, security (data collection, PII, encryption, consent), and performance (build impact, APK size, startup, memory, network, battery, UI jank). It shows concrete probes to run, deliverables to request, and ends with two engineering controls: dynamic delivery and avoid tight coupling.
AI-written summary · about
chapters (10)
- 0:00Introduction to due diligence
- 1:33Why due diligence matters
- 4:45Framework for evaluation
- 5:28Documentation review
- 12:10Integration process
- 19:10Customization checks
- 24:30Security considerations
- 28:42Performance impact
- 34:15Final questions to ask
- 35:59Closing and resources
related talks
45mPerforming Due Diligence as Android Developers
41mFirst, Do No Harm
23mSpeed Trap Ahead - Avoiding Costly Security and Privacy Issues in SDK Integration
32mWriting Android Libraries
42mTesting Android Security
47mDefending Your Users
34mDemystifying Android Security
38mAdvanced Techniques for Protecting Android Apps