# android-app-bundle

The Android App Bundle is a publishing format and signed binary file that organizes an Android app's compiled code and resources into modules for generating optimized APKs.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## How to Build and Publish a Native Android App in 2026: From Jetpack Compose to the Google Play Store

DevFeed: [How to Build and Publish a Native Android App in 2026: From Jetpack Compose to the Google Play Store](<https://devfeed.tech/articles/how-to-build-and-publish-a-native-android-app-in-2026-from-jetpack-compose-to-the-google-play-store-90318.md>)

Original publisher: [Read original article](<https://www.freecodecamp.org/news/build-publish-native-android-app-from-jetpack-compose-to-google-play-store-handbook/>)

Author: Nikheel Vishwas Savant

Published: 2026-10-19T13:14:15Z

Content type: tutorial

Language: en

Sources: [Free Code Camp](<https://devfeed.tech/sources/freecodecamp-programming-tutorials-python-javascript-git-more.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>), [android-app-bundle](<https://devfeed.tech/topics/android-app-bundle.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-bundle](<https://devfeed.tech/tags/android-app-bundle.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [app](<https://devfeed.tech/tags/app.md>), [app-development](<https://devfeed.tech/tags/app-development.md>), [build](<https://devfeed.tech/tags/build.md>), [compose](<https://devfeed.tech/tags/compose.md>), [google-play](<https://devfeed.tech/tags/google-play.md>), [handbook](<https://devfeed.tech/tags/handbook.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>)

### AI overview

A step-by-step handbook builds a notes app with Kotlin and Jetpack Compose, covering app architecture, local storage, UI state, navigation, and composable testing. It then explains release signing, Android App Bundles, Google Play setup, testing requirements, and publishing.

### Source excerpt

Most Android tutorials stop at "it runs on the emulator." But getting an app from a blank project to a listing that real people can install from Google Play involves a second half that's rarely discus

## Koko, KMP Starter Kit -- Part 3: Publishing: Your App in the Stores

DevFeed: [Koko, KMP Starter Kit -- Part 3: Publishing: Your App in the Stores](<https://devfeed.tech/articles/koko-kmp-starter-kit-part-3-publishing-your-app-in-the-stores-22948.md>)

Original publisher: [Read original article](<https://proandroiddev.com/kmp-starter-kit-part-3-publishing-your-app-in-the-stores-fd64d3629c02?source=rss----c72404660798---4>)

Author: Mirzamehdi Karimov

Published: 2026-09-14T04:48:22Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [appstores](<https://devfeed.tech/topics/appstores.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [android-app-bundle](<https://devfeed.tech/topics/android-app-bundle.md>), [software-development](<https://devfeed.tech/topics/software-development.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [account](<https://devfeed.tech/tags/account.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-assistant](<https://devfeed.tech/tags/ai-coding-assistant.md>), [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [backend](<https://devfeed.tech/tags/backend.md>), [beta](<https://devfeed.tech/tags/beta.md>), [business](<https://devfeed.tech/tags/business.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [data](<https://devfeed.tech/tags/data.md>), [development](<https://devfeed.tech/tags/development.md>), [email](<https://devfeed.tech/tags/email.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [github](<https://devfeed.tech/tags/github.md>), [google](<https://devfeed.tech/tags/google.md>), [google-play](<https://devfeed.tech/tags/google-play.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [publishing](<https://devfeed.tech/tags/publishing.md>)

### AI overview

Publishing requires developer accounts, store assets and forms, signing, and configured app metadata. Google Play costs $25 once; Apple costs $99 yearly, and account verification can take days. Individual Google Play accounts must run a closed test with at least 12 testers for 14 days before applying for production access; company accounts skip that rule but need a registered business and D-U-N-S number. Set permanent app IDs, working privacy and terms URLs, and a support email; remove direct AI provider keys that would be embedded in the app and point to a deployed backend. The kit provides scripts for readiness checks, icons, version updates, signed Android builds, and store screenshots. GitHub Actions can build and upload Android and iOS releases from tags; iOS builds and signing run on GitHub-hosted Macs, with Fastlane match managing certificates. The first Google Play upload must be manual, and later uploads can use the workflow. Missing repository secrets may leave features using placeholder values. After upload, Android individual accounts complete testing and seek production access; iOS builds go through TestFlight and App Store review.

### Source excerpt

Part 3 of 4: the third phase of the KMP contest starter kit. What to check when publishing, what the stores ask for, and how to publish both apps from GitHub without having a Mac. New here? Part 1 introduces the kit and gets your app running on your machine. Part 2 connects it to Firebase, sign in and a backend. You've finished the development part of your app, tested it, and it works. Screens done, data saved, maybe some services connected from part 2. Now comes the publishing part, and it can look complicated at first. But publishing is mostly a checklist, and the kit ships the checklist as a script: ./MobileApp/scripts/check_env.sh --phase publishing Or ask your AI coding assistant "is my app ready to publish?" and it runs this instead of guessing. It checks the things people forget: are the privacy policy and terms URLs real pages instead of placeholders? Is the contact email still support@example.com? Is your AI feature still calling providers directly with a key that would ship inside the binary? Each warning points at the fix. The rest of this post goes through the phase in order. A few steps involve waiting, so it's better to read it once first and start those early. Store accounts You need a developer account with each store. Google Play: $25, once. Apple: $99 per year. Start both today. Apple or Google can take days to verify a new account. Google Play has a testing rule: if you register as an individual (not a company), you can't publish to production until your app has run a closed test with at least 12 testers for 14 days, and then you apply for production access. Company accounts skip this, but need a registered business with a D-U-N-S number. For most first apps: register as an individual, collect 12 friends' emails now, and use those two weeks as your beta. App id and configuration Two things become permanent in this phase. The app id. Google Play ties your package name to the app on the first upload, and Apple ties the bundle id to the store record.

## Elevating app quality: Reducing memory usage and improving device migration

DevFeed: [Elevating app quality: Reducing memory usage and improving device migration](<https://devfeed.tech/articles/elevating-app-quality-reducing-memory-usage-and-improving-device-migration-88692.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/elevating-app-quality-reducing-memory-usage-and-improving-device-migration>)

Author: Raghavendra Hareesh Pottamsetty

Published: 2026-08-26T00:00:00Z

Content type: news

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Google Play](<https://devfeed.tech/topics/google-play.md>), [mobile-app-performance](<https://devfeed.tech/topics/mobile-app-performance.md>), [android-app-bundle](<https://devfeed.tech/topics/android-app-bundle.md>), [R8](<https://devfeed.tech/topics/r8.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-vitals](<https://devfeed.tech/tags/android-vitals.md>), [app-quality](<https://devfeed.tech/tags/app-quality.md>), [developers](<https://devfeed.tech/tags/developers.md>), [memory](<https://devfeed.tech/tags/memory.md>), [migration](<https://devfeed.tech/tags/migration.md>), [product-news](<https://devfeed.tech/tags/product-news.md>)

### AI overview

Google Play is introducing app quality requirements for memory usage, bitmap handling, and DEX optimization, with enforcement beginning in February 2027. Starting in April 2027, apps that support sign-in must use the Android Restore Credentials API to restore users' sign-in state during device transfers. Play Console tools are rolling out to help developers measure memory use, identify crashes, and assess code optimization.

### Source excerpt

Maintaining a healthy Android ecosystem is a shared commitment where every app and game has a role to play.

## Use Google Play Instant To Handle Deep Links -- A Real World Scenario

DevFeed: [Use Google Play Instant To Handle Deep Links -- A Real World Scenario](<https://devfeed.tech/articles/use-google-play-instant-to-handle-deep-links-a-real-world-scenario-28873.md>)

Original publisher: [Read original article](<https://medium.com/volvo-cars-engineering/use-google-play-instant-to-handle-deep-links-a-real-world-scenario-c7b6b4db0aad?source=rss----4eed8113139---4>)

Author: Mehdi Satei

Published: 2024-11-07T12:29:53Z

Content type: tutorial

Language: en

Sources: [Volvo Cars](<https://devfeed.tech/sources/volvo-cars-engineering-medium.md>)

Topics: [deeplinks](<https://devfeed.tech/topics/deeplinks.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>), [android-app-bundle](<https://devfeed.tech/topics/android-app-bundle.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [deep](<https://devfeed.tech/tags/deep.md>), [deep-link-android](<https://devfeed.tech/tags/deep-link-android.md>), [google](<https://devfeed.tech/tags/google.md>), [google-play](<https://devfeed.tech/tags/google-play.md>), [google-play-instant](<https://devfeed.tech/tags/google-play-instant.md>), [links](<https://devfeed.tech/tags/links.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

### AI overview

Google Play Instant lets Volvo Cars open a co-drive invitation deep link even when the recipient has not installed the main app. The instant app can handle sign-in or sign-up, preserve the invitation and session data in an Instant App cookie, then prompt installation; the main app retrieves the saved context after installation and login to continue the invitation flow. The excerpt favors a separate instant module for a modular codebase, while noting product flavours as an alternative. It outlines manifest and App Links setup, cookie size checks (the observed limit was about 16 KB), and Play Store publishing. Constraints include keeping the instant app under 10 MB, dependency and UI reuse challenges, and the need for Play Store test-track testing to assess real link launches.

### Source excerpt

Use Google Play Instant To Handle Deep Links -- A Real World ScenarioDiving Deep into Deep Linking with Volvo Cars App Picture this: You've just settled into the driver's seat of your brand-new Volvo car. You swiftly install the Volvo Cars Application, set up an account, and link your car. The experience is exhilarating, and you can't wait to share the same experience and let your partner or your children to co-drive and relish the same thrill. With Volvo Cars App you can do this now! If you're a Volvo car owner, you can now generate a co-drive invitation link, send it over, and once they tap on it, they're all set. From a user's perspective, it sounds dreamy. But, if you switch the lens to that of a developer building this feature, the narrative takes a rather, let's say, 'complex' turn. Tapping on the generated co-drive invitation link is something that we know as deep link. Deep linking is the art of taking a user directly to a particular screen inside the app via a universal URL (a.k.a App Link). It sounds straightforward, but implementing it can give even seasoned developers a run for their money. One significant speed bump in many apps is authentication. Before accessing content, in most cases, a user needs to be authenticated. So, when clicking on the app link, the user needs to have the app installed and be signed in, and only then can the app navigate them directly to the specific content. Now, throw in the unpleasant scenario of the user not having an account, and the plot thickens. The app must intelligently handle the sign-up dance before gracefully resuming the deep link dance. Despite being a bit challenging, when the user taps on a deep link, Volvo Cars App could handle the authentication flow. But at Volvo Cars, we also throw the curveball of "Can we deliver a great user experience for a co-driving scenario, with the generated deep link for the users who don't have our app installed?" If a user taps on a deep link without having the app installed, gui

## Aircall Journey to Android App Bundle

DevFeed: [Aircall Journey to Android App Bundle](<https://devfeed.tech/articles/aircall-journey-to-android-app-bundle-25946.md>)

Original publisher: [Read original article](<https://medium.com/inside-aircall/aircall-journey-to-android-app-bundle-14d0df0d0ea7?source=rss-cbfc736ddcd3------2>)

Author: Julien Salvi

Published: 2021-02-18T15:12:51Z

Content type: article

Language: en

Sources: [Julien Salvi](<https://devfeed.tech/sources/stories-by-julien-salvi-on-medium.md>)

Topics: [android-app-bundle](<https://devfeed.tech/topics/android-app-bundle.md>), [Android](<https://devfeed.tech/topics/android.md>), [APK](<https://devfeed.tech/topics/apk.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [appstores](<https://devfeed.tech/topics/appstores.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Internationalization (i18n)](<https://devfeed.tech/topics/i18n.md>)

Tags: [aircall](<https://devfeed.tech/tags/aircall.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-bundle](<https://devfeed.tech/tags/android-app-bundle.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [apk](<https://devfeed.tech/tags/apk.md>), [application](<https://devfeed.tech/tags/application.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [assets](<https://devfeed.tech/tags/assets.md>), [build](<https://devfeed.tech/tags/build.md>), [ci](<https://devfeed.tech/tags/ci.md>), [circleci](<https://devfeed.tech/tags/circleci.md>), [code](<https://devfeed.tech/tags/code.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [feature-flags](<https://devfeed.tech/tags/feature-flags.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [impact](<https://devfeed.tech/tags/impact.md>), [journey](<https://devfeed.tech/tags/journey.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [optimized](<https://devfeed.tech/tags/optimized.md>), [play-store](<https://devfeed.tech/tags/play-store.md>)

### AI overview

Aircall adopted Android App Bundle to reduce download size by delivering device-specific APKs. Its APK included native libraries for every supported architecture and resources for multiple screen densities; the team says optimized delivery cut overall size by 60%, avoiding the need to manage four ABI-specific APKs with different version codes. The excerpt also describes splitting by language, density, and ABI, and notes a potential future use for Play Feature Delivery with the app's feature flags. The article introduces a CircleCI and fastlane release workflow, but the supplied excerpt ends before detailing it. Its estimate of 22 TB saved at one million downloads is presented as a projection.

### Source excerpt

A couple months, we decided to use Android App Bundle (AAB) to distribute Aircall's Android app in Play Store. After analyzing the Aircall Android application package (APK), we found we could deliver optimized APKs to our users -- an overall size reduction of 60%! In this article, we are going to expose our journey to Android App Bundle from our own motivations to the development within the application and the CI with CircleCI and fastlane to release on the Play Store. Why move to App Bundle? Moving to App Bundle had many advantages. The first and main reason was the APK size optimization, to deliver only what the user needs. After looking at our application file, we found that we embedded all native libraries (.so files) of all supported architectures! We could have used the abi split in our main build.gradle but we would have managed 4 APKs with different version code. We also saw we could reduce the resource assets to match the density of the device where the app is installed. Here is what the Aircall universal APK looks like on the inside: APK analysis with Android Studio Optimizing size was not the only advantage we saw. Migrating to AAB will allow us (a little bit) to save the planet! Indeed, with all the MB saved from the downloads and updates, we are using less storage space and consuming fewer energy resources. You can see our MAD Score below. If it hits 1 million downloads we could save 22 TB of data -- really a huge impact. MAD Score data from the Aircall project We were also excited by our future ability to enable Play Feature Delivery to push features to specific users. Since we are already using feature flags inside our applications, this would let us develop features on-the-go for our users. Gradle configuration Moving to AAB was a very smooth process and did not require a lot of configuration code. To replicate this move, on your build.gradle of your application, add the following block to build an AAB file. You will be able to add the language, densit

## Twitch for Android: From Meme to Dream

DevFeed: [Twitch for Android: From Meme to Dream](<https://devfeed.tech/articles/twitch-for-android-from-meme-to-dream-20456.md>)

Original publisher: [Read original article](<https://medium.com/twitch-news/twitch-for-android-from-meme-to-dream-141e6b7e8416?source=rss----3ae745429979--engineering>)

Author: Joaquim Verges

Published: 2019-02-26T21:45:39Z

Content type: article

Language: en

Sources: [Twitch](<https://devfeed.tech/sources/twitch.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Dagger](<https://devfeed.tech/topics/dagger.md>), [android-app-bundle](<https://devfeed.tech/topics/android-app-bundle.md>), [Unit testing](<https://devfeed.tech/topics/unit-testing.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-pattern](<https://devfeed.tech/tags/architecture-pattern.md>), [chat](<https://devfeed.tech/tags/chat.md>), [classes](<https://devfeed.tech/tags/classes.md>), [code](<https://devfeed.tech/tags/code.md>), [design](<https://devfeed.tech/tags/design.md>), [development](<https://devfeed.tech/tags/development.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mvp](<https://devfeed.tech/tags/mvp.md>), [network](<https://devfeed.tech/tags/network.md>), [new-features](<https://devfeed.tech/tags/new-features.md>), [redesign](<https://devfeed.tech/tags/redesign.md>), [state-management](<https://devfeed.tech/tags/state-management.md>), [stream](<https://devfeed.tech/tags/stream.md>), [twitch](<https://devfeed.tech/tags/twitch.md>), [ui](<https://devfeed.tech/tags/ui.md>), [unit-test](<https://devfeed.tech/tags/unit-test.md>)

### AI overview

Twitch rebuilt PogDroid's foundations to support a redesign and faster feature work. The team adopted a consistent MVP structure separating data, presentation and view layers; dependency injection made data and presentation code easier to unit test, and about 70% of main screens were rewritten within three months. Later changes included Kotlin, RxJava and Dagger2, alongside migrating about 90% of API calls to GraphQL with the early-stage Apollo library. For regression testing, the team built readable Espresso tests and ran them nightly. By 2019, App Bundles had reduced final APK size by 44%; modularization and a more reactive MVP pattern were still in progress.

### Source excerpt

Meet PogDroid, our beloved Android app, to watch the latest memes unfold live while on the go. PogDroid started with very humble beginnings, and has seen incredible growth in the past couple of years. We quadrupled the team, redesigned the entire app, and rewrote most of it in only a few months using the latest and greatest Android has to offer. Buckle up: this is PogDroid's epic adventure. Level 1: Meme app with big dreams Back in March 2017, PogDroid was maintained by a very small team of engineers, and covered the most basic functionality of Twitch: browse and watch a stream with Chat. Old PogDroid, before the big makeover Mobile, and Android in particular, was getting more and more users, and the company decided it was time for a serious investment in PogDroid. The plan was to give the app a fresh new look, and build up some important features that were missing. The team grew only a little bit, but were tasked to take on this big project. As with most apps maintained by a very small team, the code structure was a mess. It became clear that such a big redesign compounded with adding new features could not be built cleanly on top of the current foundation. There was no common pattern to build screens, not a single unit test, and a lot of core classes were more than 3,000 lines of code long, with very complex state management, handling everything from network requests to UI rendering. We all agreed that in order to make PogDroid what we were dreaming of, we first needed to rethink its foundations. Step 1: Agree on a common architecture pattern The first thing we did is come up with a common design pattern to build features and screens. We wanted this design pattern to be: easy to understand hard to get wrong flexible enough to be applied to any feature or screen easy to unit test We quickly settled on a straightforward MVP pattern that looks like this: With these layers in mind, it became easy to categorize the type of classes we needed for every feature: Typical c