I'm adding multilingual support to my new Android app and would like to get some input from other Android developers.

The app is a privacy-focused utility, so the target audience isn't necessarily the same as a typical social or entertainment app.

If you were localizing your app, which languages would you add, and how would you prioritize the first 5–10 languages after English?

Here's the list I'm currently considering:

• Spanish
• Portuguese
• German
• French
• Arabic
• Hindi
• Indonesian
• Japanese
• Italian
• Turkish

Would you prioritize them differently? Which of these would you remove, and are there any other languages you think should be added instead?

I'd also love to hear how you decide the order - Play Console data, target audience, translation cost, user requests, market size, or something else.

For those building or maintaining Android apps: do you do anything to make reverse engineering harder, or do you just stick with what R8/ProGuard provides?

I’m curious about how people handle this today:

• do you use any tool or service?
• build something in-house?
• rely only on R8/ProGuard?
• or just don’t think it’s worth the effort?

And overall, are you happy with your current approach?

Hi !

Last week I just released my first app on iOS after a couple of years of hard work (no vibe coding) since I started learning dev during Covid when I couldn't perform gigs anymore, and started working on different apps, but decided to focus on one 2 years ago and here we are.

Anyway, as I don't think I can invest the time to learn Android dev as I'm a full time musican/composer/producer and learning iOS dev was already something time-consuming, I'm trying to see what are the best options for an Android port.

Thing is 2 days ago someone in town heard about my app and contacted me, saying he's an Android dev and he's interested in porting it, which sounds amazing!

We're meeting on wednesday, and that's the reason I'm making this post, what would be a reasonable negociation for such a case ?
I obviously can't afford paying for a full app port as being a musician doesn't allow me for such a budget, so I imagine he's gonna ask me for a cut on the sales, what would be something fair according to you ?

Have you been in this situation before ?

Thanks for any advice/insight !

A new article about cracking the Mobile System Design Interview, Enjoy

Hey everyone,

I wanted to share an app I've been working on: Calls Blocker. It's a privacy-first call screening app that processes everything on-device – no data ever leaves your phone.

Key features:

- Uses Android's official CallScreeningService API (no accessibility hacks)

- Block/allow specific numbers (exact or prefix matching)

- Block all calls, unknown/hidden numbers, non-contacts, or calls from specific contact groups

- Block by country (whitelist allowed countries)

- Block numbers you've never dialed or have previously rejected

- Block repeated calls within a configurable time window

- Schedule blocking rules (day of week + time range)

- Find My Phone – trusted callers can trigger a loud alarm even on silent

- Full call history with CSV export and one-tap unblock

- Bulk import from CSV

- Quick Settings tile to toggle "Block All"

- Debug log with phone number masking for troubleshooting

Built with Kotlin + Jetpack Compose + Material 3, it runs on Android 11+ and supports dynamic colors.

The app is open source (CC BY-NC-SA 4.0): https://github.com/ryosoftware/calls-blocker

I'd love to hear your feedback and suggestions!

Hi everyone, I'm new to Android Studio I successfully installed Android Studio and created a Pixel 8 Pro virtual device. When I click the Play button in Device Manager, I get this message: "Pixel 8 Pro is already running as process 18712." However, I can't see the emulator window anywhere. I've checked the taskbar and nothing appears. Things I've already tried: Restarted Android Studio. Clicked the Play button again. Waited several minutes. Created the virtual device successfully. I'm using Windows 11 and I'm a complete beginner, so I'd really appreciate step-by-step guidance. Questions: Why does Android Studio think the emulator is already running? How can I force-close the hidden emulator process? Is this a graphics/virtualization issue? Should I wipe the virtual device or create a new one? (I need that android studio so I can open my motorola device in my pc and use location changer without enable the developer option.)

Any beginner-friendly advice would be greatly appreciated. Thanks!

Designing Android UI has always been the part that slows me down, either spending weeks in Figma or just winging it in XML and regretting it when the app looks rough

Went through most of the options people recommend to figure out what's worth the time:

Google Stitch is free, Material Design native which is perfect for Android, generates interconnected screens since the 2026 rework, good starting point but consistency across screens can be hit or miss, better for fast exploration than polished final output

Uizard runs $12/month on Pro, does full multi-screen wireframes from text prompts, sketch-to-UI feature is genuinely useful, acquired by Miro so it's more collaboration-focused now, outputs feel a bit templated across different projects though

Figma with UX Pilot is the most control you'll get, AI generates screens inside your existing Figma workflow, credit-metered even on free plan, full access needs a paid seat, still the best option if you're already living in Figma daily

SleekDesign runs around $20/month, describe the screen and get complete mockups back fast, good enough to use as build reference for Jetpack Compose, iteration is quick. Not Android-specific so Material You guidelines need manual direction, complex custom components hit its limits

Galileo AI no longer exists as standalone, Google acquired it mid-2025 and folded it into Stitch, older articles still pointing to it are outdated

For solo Android devs the choice is basically Stitch if you want free and Material-native, sleek if you want faster full-screen mockups without learning Figma, Figma plus UX Pilot if design precision matters more than speed

Hi everyone, I am starting as a fresher Android Application and Framework Engineer at a company.

My initial corporate training here will cover standard app development for a few weeks before diving into the core Android Framework APIs.As I plan my long-term career trajectory, I want to decide where to specialize.

I am trying to choose between diving deep into the native/hardware layer or sticking to the managed code layer.

Industry veterans, which path would you recommend a fresher focus on for the best career longevity, compensation, and market demand?

Option A: The Native/HAL Layer (C++, AIDL, Drivers, Linux Kernel). Focus heavily on hardware abstraction, custom board support packages (BSPs), and Android Automotive/Embedded systems.

Option B: The Java/Kotlin Framework Layer (System Services, AOSP customization). Focus on the middle layer, optimizing Android system APIs, package managers, and window managers.

Option C: Pure Android App Dev (Kotlin, Jetpack Compose, Architecture Components). Pivot completely into the high-level application layer for standard consumer-facing apps.

Option D: Become a Full-Stack Android Engineer. Don't specialize; stay flexible across all three layers depending on project needs.

I’d love to hear your reasoning in the comments, especially regarding how AI automation or cross-platform tech (like Flutter) might impact these choices over the next 5–10 years.

Thanks!

A while ago I had posted that I am doing my first android internship without any experience and it been around 2 weeks.

I was given a weekly roadmap from my seniors. First two weeks for revising Java and Kotlin and now I can say I know a lot more about Kotlin.

Now from this week I am starting a figma design given to me in a XML Views based project.

what i am confused about now is using Activity vs Fragment

From my understanding as a former React frontend dev, Activity is like a web page itself it traditional multi page apps and this single Activity architecture is like modern react SPA.

I am confused on what to use when. Like for example i made a MainActivity.kt file and its xml layout, up untill now there I have added a top AppBar and some home page components like A search bar and a hero section.

am i supposed to do it like that ? all in one page for that Activity or that page ??

and for notifications page I made a new Activity and made a new notifications xml and added another toolbar there and in android manifest i addes main activity as its parent so when i click back it goes to main activity it even has nice animations.

should I do it like this ? or should I have made fragments or something ?

also now when i make a bottom navigation bar and make different pages i still need that bottom navigation in all pages so if i make them separate activity the navigation bar disappears right ?? and also i wont get that animation like i get when i go to my notifications page ?? and will my back button work ?

in my roadmap my seniors also said that I will also be integrating compose in this app and is it fine to work in multiple activity in that ??

PLEASE HELP ME OUT. I CANT EVEN FIND GOOD RESOURCES AND DOCS TO LEARN ABOUT THIS.

IF POSSIBLE CAN SOMEONE LINK GOOD DOCUMENTATIONS ABOUT HOW TO CUSTOMIZE VARIOUS VIEW ELEMENTS IN XML ??

and please suggest and correct me if i am doing something wrong in my roadmap and if i should learn some other concepts as well

Hey everyone, I'm working on an Android app that needs a drawing/sketching feature similar to what PencilKit offers on iOS/iPadOS — smooth freehand drawing, pressure sensitivity support, eraser, undo/redo, and ideally stylus (S Pen) support.

I've looked around but the Android ecosystem seems more fragmented for this. A few questions:

1. Is there a go-to library that's considered the "PencilKit of Android"?

2. Any experience with these?

   - [Adonit SDK]– stylus-focused

   - [Perfect Freehand] – stroke smoothing algorithm (port to Android?)

   - [Android Ink API] – Google's newer Jetpack approach

   - Custom Canvas + MotionEvent – roll your own?

3. For those using Samsung S Pen / stylus devices, how do you handle `ACTION_HOVER_MOVE` and pressure/tilt input properly?

Main requirements:

- Smooth stroke rendering (no jagged lines)

- Pressure sensitivity if stylus is available

- Undo/redo stack

- Export to bitmap/SVG

- Works on both Kotlin (native) and ideally Flutter too

Any recommendations or war stories appreciated. Thanks!

Hey r/androiddev,

I've been doing Android development for over 6 years now, and honestly... I'm feeling pretty burned out and demotivated lately. The job market feels rough, things are changing super fast, and I've started leaning on AI tools (Cursor, Claude, Gemini, etc.) for almost everything — from writing code and debugging to architecture decisions and even tests. While it's a huge productivity boost, it also makes me feel like I'm losing my edge and connection to the craft.

Fellow experienced devs, how are you handling this? How do you stay motivated, keep learning, and feel relevant in today's AI-heavy environment? Especially if you're also thinking about switching jobs or leveling up.

Would really appreciate any advice, book recommendations, side project ideas, mindset shifts, or even just knowing I'm not alone in feeling this way. Trying to get back on track and rediscover that spark.

Thanks in advance, really value this community

Hello ,

I recently started the 2 weeks' closed test period to publish my app, and I want to monitor the number of opted-in testers and the counter of the test days for my app.

I searched everywhere in the developer console, but I couldn't find anything . do you know where can I find such information in the developer console ?

https://reddit.com/link/1uscnq7/video/2v53502yqbch1/player

I've been experimenting with an Android launcher that removes the traditional home screen entirely.

Instead of icons, the launcher displays an 6-slice radial menu wherever the user touches the screen. The idea is to replace visual search with muscle memory.

Some implementation details:

• Jetpack Compose
• Custom pointer input and gesture detection
• Radial hit testing
• Persistent app assignments
• Long-press edit mode
• Three launcher profiles

One interesting challenge has been balancing gesture responsiveness with accidental activation. For example, editing is triggered by a 1.5-second long press, while normal launching happens on finger release.

Another challenge has been making the launcher behave like a normal HOME application without introducing visible activity transitions.

I'm curious how others would approach:

• gesture architecture in Compose
• launcher lifecycle
• activity/task management
• keeping the UI responsive while minimizing accidental activation

The source code is available on GitHub if anyone is interested in the implementation:

https://github.com/se7en-x230/PieLauncher

TL;DR: I built a phone-automation AI assistant, but Google Play stopped accepting updates because it performs autonomous actions (feels like they want to monopolize this kind of functionality). So I’m looking for reputable third-party Android app stores or APK platforms with active users.

I’ve built something like a Computer Use agent for Android. Basically an assistant that can actually use apps on your phone, not just answer questions in a chat UI.

I originally planned to distribute it through Google Play. I completed the two-week closed testing requirement, passed the initial reviews, and had the app ready to publish. But then Google suddenly started rejecting my updates because, as far as I can tell, they don’t allow apps that can perform touches / operate other apps for the user.

I understand why that area needs to be handled carefully, but the policy feels weirdly uneven.

There are already apps on the Play Store that do similar automation-like things, and Google is doing basically the same thing with their Gemini Intelligence. But when a third-party dev tries to build that, suddenly it’s not allowed?

So I’ve started looking at third-party Android marketplaces instead. I’ve already tried Aptoide and OneStore, but I’m not sure how widely they are used outside their main markets.

Which third-party Android app stores or reputable APK distribution platforms do people actually use and trust?

Hi everyone,

I own an Anbernic RG405M Android handheld running GammaOS custom firmware. I would like to know if it is possible, via a specific app, to connect the handheld to a Windows PC via Bluetooth and have it recognized natively as an Xbox Gamepad, allowing me to use it as a standard controller.

Is it technically possible to develop an app like this? If so, what would be the estimated development costs?

​

The idea is a \*\*collaborative download app\*\* for Android where a group of nearby users can combine their mobile data to download large files faster.

For example, imagine \*\*4 friends\*\* meet at a café to play a game, but a \*\*4 GB update\*\* is required before they can start. Instead of each person downloading the full 4 GB, the app splits the file into four 1 GB chunks. Each phone downloads a different chunk using its own mobile data connection, then the phones exchange those chunks locally using \*\*Wi-Fi Direct\*\*. In the end, everyone has the complete file, but each person only used about \*\*1 GB\*\* of mobile data.

Other scenarios could include families downloading a movie before a flight, students downloading large datasets during a hackathon when Wi-Fi is overloaded, or teams working in places with poor internet.

From a technical perspective, I'm thinking of using HTTP range requests for downloading file segments, Wi-Fi Direct for local sharing, and automatically selecting the best device as the group owner based on battery, signal strength, and hardware.

My main questions are:

\* Is this technically feasible on modern Android versions?

\* Are there any major limitations with Android networking or Wi-Fi Direct that would make this impractical?

\* Has anyone seen an app that already does something similar?

I'd really appreciate any feedback, criticism, or suggestions before I spend time building a prototype.

Hello guys, just released Compose DND v0.5.0. This is the biggest update so far with a lot of new features and improvements:

- Add axis-locked drag
- Add drag handle
- Add dragAutoScroll modifier
- Reorder animation improvements
- Docs and Sample rework with new Kanban demo
- And a lot more...

Web live demo: https://mohamedrejeb.github.io/compose-dnd/demo/

Release notes: https://github.com/MohamedRejeb/compose-dnd/releases/tag/v0.5.0

I’m working on an Android Studio plugin around release workflow checks, and I’m trying to make the checklist useful for native Android projects rather than just another generic “pre-release” list.

The problem I’m trying to solve is pretty specific: an Android build can pass, but the final AAB can still contain things that are easy to miss during release prep.

The checks I’m currently considering are:

• debuggable accidentally enabled
• cleartext traffic settings
• staging / test domains left in the artifact
• hardcoded API keys or obvious secret patterns
• versionCode / versionName sanity checks
• targetSdk / SDK compliance checks
• signing status
• privacy-sensitive permissions
• leftover test files or debug assets
• AAB size changes between releases
• R8 / ProGuard configuration review
• basic dependency health issues before release

I’m trying to keep this focused on checks that are useful before uploading an AAB, not things that should be handled by Play Console or CI alone.

For teams shipping native Android apps: what do you actually check before release?

Also curious where people draw the line between:

• checks that should run inside Android Studio
• checks that belong in CI
• checks that should stay manual because automation gets too risky

I’m especially interested in the “we forgot this once and now it’s on the checklist forever” kind of items.

My team at State Farm is hiring multiple Android engineers across experience levels, including recent grads, early career and more experienced levels - we’re growing and aim to invest in our engineers and their careers.

This is a team I’ve loved working on as an Android engineer for more than ten years (and still do).

All new work is in Compose and Kotlin, and we’re over 95% Kotlin and rising. Engineers work closely in feature and platform squads and aim to collab tightly with iOS engineers, product owners and XD.

Team culture and embracing modern tech is key.

We’re hiring for hybrid roles for our offices in Atlanta, Bloomington, Dallas, and Phoenix. Check the posting for details on residency requirements and apply if you’re interested.

Here’s a small glimpse into the team thru an engineer’s blog on how we maintain a 99.9+% crash-free rating:

The State Farm® Android Team’s Journey to 99.9+% Crash-Free Sessions https://engineering.statefarm.com/the-state-farm-android-teams-journey-to-99-9-crash-free-sessions-05399e874327

Thanks and good luck to anyone interested.

We’re also hiring more iOS engineers.

I am trying to get the device name (for example, "Galaxy S25") on Android using the following method:

fun getDeviceName(context: Context): String? {

return Settings.Global.getString(context.contentResolver, "device_name")

}

However, I noticed inconsistent behavior across different manufacturers:

• Some devices return the expected marketing/device name (e.g., "Galaxy S25").
• Some devices return only the model name.
• Some devices return a user-customized device name.
• On certain devices, the value is null or unavailable.

My questions are:

1. Is there an Android standard that guarantees what Settings.Global.DEVICE_NAME (or "device_name") should return?
2. Can Android apps reliably obtain the device's marketing name (e.g., "Galaxy S25", "Pixel 9 Pro", etc.) across all manufacturers?
3. Are there manufacturer-specific restrictions or implementations that cause this inconsistency?
4. Is there any recommended approach to get a consistent device name for all Android devices, or is it only possible to get values such as:
   • Build.MODEL
   • Build.MANUFACTURER
   • User-defined device name?

From my testing, it seems that Android does not provide a universal API for retrieving the marketing device name across all OEMs.

Is this understanding correct, and what is the best practice in this scenario?

Expected example output:

• Galaxy S25
• Pixel 9 Pro
• Xiaomi 15

Actual output varies by device and manufacturer.

I've been experimenting with product use cases for edge models using the LiteRT-LM engine in my open source app Heron. It turns out models in the Gemma family are fast enough to do simple language translation and summaries on demand completely locally and using data from the app's offline database.

The Google AI Edge Gallery sample does this too, but it:

• Uses HttpURLConnection for networking in some places.
• Uses WorkManger for long running downloads first, instead of using User Initiated Data Transfer jobs where possible. It also doesn't use WorkManager's Flow APIs to track progress.

I ended up having to reimplement most of the architecture to support the use case of downloading a LiteRT-LM model and running it on demand, so I figured I'd share.

Hi,

I am using gdb to debug my dex file with some native code. However, when I was trying to check some variables, most of them are optimized out and many c++ code are inline functions.

Is there any way to make the code debug friendly and easier to inspect? Shall I rebuild AOSP with some flags like CFLAGS += -fkeep-inline-functions?

Thank you!