Android App Bundle: from start to deployment
summary
Migrating to Android App Bundle requires changing Gradle to produce an .aab (run bundle release), enabling Play App Signing, and updating CI (Fastlane/GitLab, CircleCI/Bitrise examples) to upload with skip_upload_apk; use the bundletool jar to generate device-specific APKs from the AAB and a device spec, or produce a universal APK for QA. Measured wins include ~60% APK size reduction (65 MB → 45 MB example) and terabytes saved at scale; asset packs have per‑pack limits (512 MB fast follow/on‑demand, 2 GB total, max 50 packs).
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker
- 1:19What is Android App Bundle
- 7:29Migrating from APK to AAB
- 11:53Testing AAB with Bundletool
- 22:58CI/CD integration for AAB
- 23:20Asset delivery features
- 31:40Dynamic feature modules
- 37:45Pros and cons of AAB
- 38:08Q&A and conclusion
related talks
44mAndroid App Bundle: from start to deployment
26mTesting Android App Bundle with Appium
53mAndroid App Bundle / Android PacKage: Each Format for Its Task
37mBuild the new, modular Android App Bundle
34mForget everything you know about APKs
34mOptimize your app size with this one trick
03mTop 7 takeaways for Android App Bundles
42mForget everything you know about APKs
