Commonly Overlooked Areas of Security: Revisited
summary
Concrete takeaways include stripping runtime logs via ProGuard/R8 rules but enforcing them in the repo and release checks, switching to Timber plus a no-op release implementation to avoid accidental logging, preferring narrow keep rules or annotations over broad keep-all patterns, treating Android NDK code as a maintenance and CI burden with different testing and build-time costs, and never committing signing keys but using Google Play App Signing and vigilant dependency updates to avoid surprise vulnerabilities.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:28What We'll Cover
- 3:34assumenosideeffects
- 20:56Refactoring with @Keep
- 21:16Refactoring with .pro
- 22:24Organization with .pro
- 25:03NDK Maintainability
- 27:32Build Process / CI
related talks
29mSecuring Android Applications - The not so se…
37mBest practices in app security
47mDefending Your Users
24mModern Android App Security: Protecting Code, Keys, and Data
41mSecure your app, fight the leaks
34mSecuring Android: Tackling Advanced Threats and Enhancing App Security
34mDemystifying Android Security
46mStrengthening Java Apps: Best Practices in Secure Coding for Java Developers