Performing Due Diligence as Android Developers
summary
Claims a repeatable due diligence framework derived from integrations at Tinder and Booking.com and illustrated with code-level POCs that check licensing, installation, init, proguard, deps and annotation processors, plus runtime checks for permissions, localization, accessibility, encryption and PII handling. Concrete steps include backing artifacts in an artifactory, measuring app bundle size, startup, memory, network and battery impact, and forcing vendor answers about tracking. Notes a real vendor with async tasks and messy models as a documented risk and recommends decoupling via interfaces and optional dynamic delivery.
AI-written summary · about
chapters (4)
related talks
37mPerforming Due Diligence as Android Developers
41mFirst, Do No Harm
38mAdvanced Techniques for Protecting Android Apps
39mAndroid App Security Fundamentals
42mTesting Android Security
37mHey, You, Get off My Private Data: Do Apps Respect Your Privacy as They Claim?
24mModern Android App Security: Protecting Code, Keys, and Data
58mAndroid Application Security Testing