Integrating SDKs - secrets, strategies, and automated performance testing
summary
Practical checklist for adding Android SDKs: require source or ask for exact bytecode size (rule of thumb 200 kilobytes), count methods and transitive deps, inspect AAR manifest merges and required permissions, demand included ProGuard rules, and verify networking strategy and IDs collected (IMEI, Android ID). Automate updates with the Gradle versions plugin, pin versions instead of wildcards, and run CI profiles that use MonkeyRunner + systrace and meminfo on sample apps to measure cold-start heap, lifecycle callbacks, and upload frequency.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 8:04Building a mobile data strategy
- 12:57Vetting SDKs before integration
- 23:59Testing SDKs after integration
- 30:39Automating SDK performance testing
- 40:11Q&A session
related talks
15mAvoiding Security and Privacy Issues in SDK Integration
32mHow to successfully shift from app development to SDK development
22mBest Practices When Building Mobile SDKs
23mSpeed Trap Ahead - Avoiding Costly Security and Privacy Issues in SDK Integration
53mHow not to fuckup with building SDK and make clients happy
32mBest Practices in SDK Development
27mSDKs & Code Samples, The Cornerstone of API Developer Experience
45mPerforming Due Diligence as Android Developers