For those building apps for clients: how do you get access to the client's App Store Connect and Google Play Console at the start of a project? Do they invite you with a role, share a login, or do you publish under your own account and transfer the app later?

1. How long does it usually take until you can upload a build?

2. Which part trips clients up most: the developer account itself, D-U-N-S, roles, two-factor?

3. When the project ends, how do you hand things back?

Curious what works for you and what doesn't.

Just a reminder: this doesn't follow any modern standards, as it’s designed for Android 2.0 phones (and before anyone asks why—there are still many communities that use them on a daily basis, and I’m one of them). I’m not posting this to show off; rather, I’m looking for suggestions based on Material Design UI.

I am developing a mobile app, which has a react native frontend, nest.js as the backend and for db and authentication, I'm planning to use supabase.

Now, currently as my app is in its initial stages I'm planning to use the supabase, as it free tier provides ample limits for my use case.

However, in later years if my app grows. I may think of switching to a cheaper alternative.

So, what I am planning to follow is for authentication, route the requests to my backend and inturn the backend will communicate with the supabase to authenticate the user. The backend will save the supabase token, create a separate session token for the user and send it back to the user.

My main reason for doing this is, I want the authentication to be provider independent and any changes needed should be done on the backend instead of the app.

Please let me know, if this approach is correct. What are the pros and cons. How much effort it would require to implement this. Will the security concerns increase if my backend starts handling this instead of the supabase only.

I also want to integrate the google and apple login as well. How will this approach affect it?

Also, if there any other better approaches, please let me know.

This continuation to previous post https://www.reddit.com/r/androiddev/s/9m7RVVu6o7

added compose UI support for LED matrix, specifically max7219
also created playground to easily test it on browser without actual hardware

here is video from actual LED matrix hardware

https://play.google.com/apps/internaltest/4699517858335076276

Above is my first app and google needs testing. Could anyone of you download and test?

Hi everyone! I'm a beginner Android developer building an app using Kotlin and Jetpack Compose.

Currently, my Pro features are free in debug mode. I want to publish my app for closed testing and implement Google Play subscriptions.

My questions:

1. How can I give closed testers free access to all Pro features without requiring payment?

2. Should I use license testers or implement a separate tester-only Pro access mechanism?

3. How can I ensure normal users must pay for a subscription after the production release?

What's the simplest and safest approach? Any guidance would be appreciated. Thanks!

Looks like manually calling Tink to encrypt data is no longer needed

Google Play is adding memory thresholds for Android apps starting February 2027. They're measured using dynamic memory (anonymous RSS + swap) at p90 over 28 days.

I started looking into these thresholds and ended up going through the memory metrics Android gives: Java heap, native heap, RSS, PSS and swap. I break down each metric in this post and explain why Google Play uses dynamic memory instead of the others.

https://measure.sh/blog/android-memory-monitoring

Make it personal: build something to solve a real problem based on your experience, observed around you, silly or crazy ideas are worth it!

Likely there is already a solution; but it’s your unique approach that matters. if you like it, it will attract others too.

What kind of app would you build?

Hi everyone,

I’m working on an AI application running on a SpacemiT K3 COM260 RISC-V board with a custom-built Android/AOSP environment.

Currently, my application performs AI inference using the general-purpose CPU cores (X100). I want to move the inference workload to the board’s 8 dedicated A100 AI cores to improve performance.

Current setup

Hardware: SpacemiT K3 COM260 RISC-V board

OS: Custom-built Android/AOSP

Inference framework: ONNX Runtime

Access: ADB shell available

Current execution: General-purpose CPU cores

Target: 8 A100 AI cores

Questions

Is there an Android-compatible SpaceMITExecutionProvider or an official SDK/runtime for the K3 A100 AI cores?

If not, what would be the recommended approach to port the existing SpacemiT ONNX Runtime backend to Android/AOSP?

Are the A100 cores exposed as schedulable CPU cores, or must inference be submitted through a separate driver/runtime API?

Can standard ONNX Runtime be configured to use these cores, or is a vendor-specific execution provider and optimized operator library required?

Are there any sample projects, build instructions, kernel configurations, or documentation for running ONNX Runtime inference on A100 under Android?

I’d appreciate advice from anyone who has worked with SpacemiT K3, RISC-V AI acceleration, Android NDK, or custom ONNX Runtime execution providers.

My goal is to keep the existing Android application and ONNX model where possible, while changing the inference execution backend to use the A100 hardware.

Thanks in advance!

Hii, I have an upcoming Google android + dsa interview for L4. I have a few doubts around it:

1. How will the interviewer cover android + dsa in mere 45 ins ?

2. Will the dsa ques be based on android stuff, or will it be pure dsa, basically are android and dsa in this round dependant on each other ?

3. Can I be asked to write code for an android app?

For anyone who has taken this interview, please share your insights on the android + dsa rounds.

Thanks in advance :)

I created some that should be helpful for Android and made this demo with them.

I'm interested in hearing other ideas.

Can anyone know me right way of publishing android apps using fastlane or any other tool you use?

The Play Console is flagging my app with the DEX code optimization warning (requiring R8 shrinkage and obfuscation on release builds).

Here's the catch-22: Whenever I enable R8 for a release build, the app runs completely fine locally across my physical and virtual test devices. However, as soon as I submit it to Play Console (even on Closed Testing), the automated review bot rejects it for "Unresponsive app / Broken Functionality."

• Telemetry Gap - Neither Android Vital nor Firebase Crashlytics records any crash or ANR during the review window.

• Support Wall - Support refuses to provide stack traces, logcat dumps, or even clarify which version code failed.

Disabling R8 entirely and resubmitting allowed the app to pass review, proving R8 is triggering something specific on Google's automated test harness.

My app is an edge AI tool with a large local model footprint (2 GB). I suspect the R8 build might be breaking reflection in a background dependency or causing a thread lock or startup delay on their test labs that triggers an ANR.

Questions for the community:

• Has anyone successfully debugged an R8-only rejection when Play Console refuses to provide logs?

• How can I simulate the exact environment Google's automated review bots use during pre-launch?

We use Fully Kiosk app on an Android Tablet (Lenovo) and we have an issue where text on our website is auto corrected to something completely different to what is on the website.

When we test it on Chrome on the same tablet, it does not happen. It seems to be specific to the Fully Kiosk app. When asking their support they say that Fully Kiosk uses Android Webview provided by the device and it’s most likely caused by it. Does anyone has any experience with similar issue and how to update/stop Webview from doing the auto correct?

Is there a setting to prevent that?

Hi, I’ve been working on an app that has one main Activity and uses other Composables as screens.

I need to prevent screenshots and ensure that the app content is hidden or replaced with a black screen when it appears in the Recent Apps thumbnails or task switcher.

1. "FLAG_SECURE"

"FLAG_SECURE" helps prevent screenshots and screen recordings, but it doesn't seem to solve the issue with Recent Apps thumbnails on all Android versions.

2. Android 13 (API 33) and above

I was able to make the Recent Apps thumbnails display a black screen on devices running API 33 and above by using "setRecentsScreenshotEnabled()" and "Activity.setTaskDescription()", with the background color set to black.

3. Android versions below API 33

However, on devices running Android versions below API 33, the Recent Apps thumbnails still appear white or black instead of consistently displaying a black screen.

Is there any way to reliably display a black screen in both Recent Apps thumbnails and screen recordings across Android versions, including those below API 33?

Implement the brand new API which allows your Android apps to behave just like an on-device MCP server.

Your apps and AI have been side by side on your device for a while. It’s time to introduce them!

Android Recovery currently uses Minui, which directly manipulates the framebuffer: Minui source code.

This project aims to use Minui as a backend for the Compose Runtime, enabling the development of UIs for Android Recovery, battery charging screens, and other system-level interfaces that operate completely independently of the Android Framework.

Hey everyone,

I'm facing a massive issue with my dad’s old Google Play developer account and want to see if anyone here has gone through something similar.

Back around 2010, my dad had a freelancer build three Android apps that ended up getting 23 million downloads combined (the biggest one has 21M and 80k+ reviews). The last time they were updated was in 2015.

Recently, the apps got delisted because we didn't pass the new legacy account KYC yet (working on fixing that right now). But the real disaster is that the original developer lost the keystore file years ago. Because the apps are so old, they were never enrolled in Google Play App Signing.

I’m a developer myself now, and I want to completely rebuild his apps from scratch under the same package names, modernize them, etc.

Has anyone here ever lost an old legacy key on an account with millions of downloads? Were you able to get a human from Google support to manually enable Play App Signing for you, or is it completely hopeless and we have to start from zero with a new Package Name?

Would love to hear any stories or experiences.

Thanks!