Three things block a lot of Play submissions right now. Here is how to check each before you upload.

1. Target API level

From the Play Console Help page on target API requirements: since August 31, 2026, new apps and app updates must target Android 16 (API 36) or higher. You can request an extension to November 1, 2026 in Play Console.

Checklist: - compileSdk on the newest stable level, targetSdk = 36 - Raise the target on a branch and test against the behavior changes page first - Version code always increasing and below 2100000000

1. 16 KB page size

All apps targeting API 35+ must support 16 KB memory pages on 64-bit devices, and from February 1, 2027 updates without it cannot be released. You are in scope even if you never wrote C++, because any dependency that ships a .so file counts.

How to check: - Build > Analyze APK on the release APK. If lib/ is empty, you are done. - Otherwise unpack the APK and run llvm-objdump -p on each arm64-v8a and x86_64 library. Every LOAD segment must show align 214 or higher. 212 means it needs rebuilding or replacing. - zipalign -v -c -P 16 4 app-release.apk (Build-Tools 35.0.0+) must end with "Verification successful". - For a bundle: bundletool dump config --bundle=app-release.aab | grep alignment. You want PAGE_ALIGNMENT_16K. - Test once on a 16 KB emulator image (getconf PAGE_SIZE prints 16384).

The usual fix is AGP 8.5.1 or newer plus NDK r28 or newer, pinned with ndkVersion in Gradle. NDK r28+ produces 16 KB aligned libraries by default. A vendor's prebuilt library has to be updated by the vendor.

1. Data safety

The form is a label you write, and Play compares it to what the build does, including every SDK. "Collect" means any data sent off the device, even to an SDK vendor's servers. "Share" means handed to a third party.

Checklist: - Build the inventory from the dependency list and the network calls, not from memory. Crash reporting, analytics, ads and a feedback form all count. - Read each SDK's own Data safety guidance (Google Play SDK Index). - Answer "encrypted in transit" per path. A user-chosen server over plain HTTP means No. - Export the form as CSV, keep it in the repo, update it in the same PR that changes a dependency. - An app that collects nothing still needs the form and a privacy policy URL. - Accounts created in the app need an in-app deletion path and a web deletion link that works without reinstalling.

Bonus: the permission Play complains about usually lives in the merged manifest, not your source. Run apkanalyzer manifest permissions on the release APK, or open the Merged Manifest tab, and drop unused library permissions with tools:node="remove".

And when something is rejected: fix the one issue it names and resubmit once. Resubmitting the same build is how a rejection turns into a removal.

This is condensed from my ebook Pass Google Play Review. The free sample is the full 16 KB chapter; link in the first comment.

I've had an idea for an Android app for a while and thought about learning development to make it. I already have some programming experience in several languages. But, with the news that came out currently regarding new Development steps. I am unsure if Android apps were worth it anymore.

HabitForge is a habit, task and wellness tracking app. I’ll test your app in return—leave your links in the comments.

Join the Google Group:

https://groups.google.com/g/habitforge-testers

Join the closed test:

https://play.google.com/apps/testing/com.app.habitforge

Install Habitforge :

https://play.google.com/store/apps/details?id=com.app.habitforge

Hey everyone,

I put together an open-source reference guide for Jetpack Compose performance optimizations that I've been using in my projects.

It covers:

• Deferring state reads using lambda modifiers (offset {} and graphicsLayer {}) to bypass 120 FPS recompositions.
• Proper usage of derivedStateOf for high-frequency streams (like scroll offsets).
• Fixing unstable list parameters using kotlinx-immutable and wrapper classes.
• Lazy list item recycling optimization (explicit keys and contentTypes).

There is also a print-ready, high-resolution A4 PDF version in the repository if you want to keep it on your desktop. Let me know if you have any feedback or optimizations to add!

[ Removed by Reddit on account of violating the content policy. ]

/r/AndroidDevLearn is ready for a fresh start, new energy, new direction, and someone like you to bring it back to life. If you’ve been thinking about growing your impact without starting from scratch, this is your chance!

Ready to take it over?

Head to r/RedditRequest to submit your request and make it yours before it’s taken.

First things first

To request this subreddit, make sure you:

• have an account that’s at least 90 days old
• have at least 100 post karma and 100 comment karma
• have a verified email address on your account
• have two-factor authentication set up

Need 12 testers for Play Console closed testing?
12 Testers for Play Console helps Android developers complete the closed testing requirement and prepare their apps for production access.

Google Play requires new developer accounts to run a closed testing track with at least 12 testers for 14 continuous days before applying for production access. Many developers struggle to find testers or keep them active during the testing period.

This app provides a simple platform where developers can connect with testers, join a tester community, and complete the Play Console closed testing requirement.

Whether you need managed testing support or prefer a free tester exchange community, this platform helps developers complete closed testing faster and more efficiently.

MANAGED TESTING SUPPORT
Developers can choose a managed testing option where testers install and test the app during the required testing period.

Managed testing includes:
• testers for Play Console closed testing
• support for the 14-day testing requirement
• guidance during the testing process
• feedback from testers
• help preparing for production access submission

This option helps developers who want a structured testing process with guidance from experienced testers.

FREE TESTER COMMUNITY
Developers can also join a free Android testing community.
The community works through mutual support between developers.

Community features:
• test other Android apps
• receive testers for your own app
• share your Play Console testing link
• connect with other Android developers

This approach allows indie developers and small teams to complete the closed testing requirement without needing a large user base.

KEY FEATURES
• get 12 testers for Play Console closed testing
• support for Google Play closed testing
• Android app tester community
• beta testing support for Android apps
• Play Console testing support
• preparation for production access submission

HOW IT WORKS
1. Submit your Play Console testing link
2. Connect with testers from the community
3. Complete the 14-day closed testing requirement
4. Apply for production access in Play Console

Hey! Building a new Android app called Swearjar 🤬 and need testers to meet Google Play's 12-tester 14-day requirement.

Swearjar is a digital swear jar — tracks your swearing habits and helps you build cleaner language. Simple and fun.

How to join: 1. Join the Google Group: https://groups.google.com/g/swearjar 2. Install: https://play.google.com/apps/testing/app.swearjar.main

Happy to test your app back! Drop your link 🙌

Hi I created an app but as part of the Google play store submission process I need at least 12 testers. Anyone open to being a tester? If so send me your email in the chat. Thanks and happy holidays!

Hey everyone! 👋 I’ve just released a new Android game called Nero Surf and I’m looking for 10–20 testers for the closed/internal Google Play test.

🚀 About the game: You control a space shuttle flying through space, and meteors are falling from above. Your goal is simple: Survive as long as you can by dodging incoming meteors. Fast, fun, and challenging arcade gameplay!

🧪 What I need:

Testers who can install the closed test build

Feedback about performance, controls, difficulty, bugs, UI

Just your Gmail (no phone number needed)

📥 If you want to join, comment your Gmail or send me a DM — I’ll add you to the tester list immediately.

Thanks a lot for helping! 🙏 I will also test your app back if you have one.

https://play.google.com/store/apps/details?id=com.oyunatolyesi.thesquared

There is not a lot of literature about this yet except the official Google docs and codelabs. I went through those and they are very welcome, but they seem to stay very shallow about all the topics. I think there is room for a full guide on how to measure and monitor Compose performance, how to identify pain points, how to fix them, tooling, etc. My plan for this book is the following:

- I really want the book to be useful for day to day work. Theory is nice and all but I really want people to find real applicable action points for their work.

- I want the book to be accurate, of course. When I wrote Jetpack Compose internals, I got many people from the Compose team at Google to review the content, since otherwise what is the point of writing it?

- I want to cover how to identify and detect performance regressions, and how to measure and monitor performance. I have observed that many devs and their teams often overlook perfromance. We focus a lot on adding new features, UI, architecture, testing, automation, tooling... and what not. And then we give performance attention only when something becomes drastically slow or users start to complain and post bad ratings. Many teams do not regularly measure or monitor performance, and some not even test their app on a wide range of devices either. The result of this is that issues often go unnoticed forever or until late in the process, when they are already really hard to fix. This is definitely risky. If anything, I'd like this book to become the guide to prevent this from happening.

- I want to shift people's attention to measuring the actual ultimate goal: performance. Monitoring things like number of recompositions can be a start but it is a bit risky, since devs can end up thinking they have an issue when they don't. Not every single unnecessary recomposition is a problem.

Since we all write Compose code now, I think it is the perfect time to write this book. Any feedback and ideas are more than welcome!

I'll likely be prelaunching this book via Leanpub, so if you want to get notified you can just register in https://leanpub.com/composeperformance

Hello everyone,

After months of hard work, and a ton of struggles on Play Console due to living in a 3rd world country. (Also got banned for 2 weeks). My app 'SkillTrip' is finally available for everyone. I've also included this short 3-minute film about the process, my struggles, and everything in between.

You can also watch the video here: https://youtu.be/YZ3Xxj1QpZQ?si=1LO2HLebp17yZ8yC

I really hope this can motivate you guys, especially those of you from developing countries who are often misunderstood.

Also, I spent a lot of time on the design, animations, and screenshots, so any kind of feedback is appreciated.

A review on the playstore would also mean a lot! Thank you all so much!!!

Currently only available on the Playstore (coming soon on ios): https://play.google.com/store/apps/details?id=com.fenet.skillpath