How do you switch into android as an experienced dev

I am a software dev with around 4 YOE and trying to switch into android but finding it hard , I am targeting the startup or any company open for remote internship or like setup but I believe most are targeted towards students only ,

My focus is to transition fully into Android in future but the starting step I am finding is hard.

If anyone have done such a transition or have any leads of possible work, I would like to know .

https://redd.it/1wzn0wb
@reddit_androiddev

Game made in Kotlin, Jetpack Compose and Filament: Things which worked and didn’t

https://redd.it/1wzpjcw
@reddit_androiddev

My Google Play Developer Account Was Terminated. If Reinstatement Isn't Possible, Is There Any Path Forward?

Hi everyone,

I’m a student and a software developer, and I’m writing this because I genuinely don’t know what options I have left.

My Google Play Developer account was terminated because of policy violations related to an app I published. I have already explained my situation to Google and acknowledged the mistakes I made. Looking back, I understand that I made serious mistakes and I genuinely regret them.

I completely understand that Google Play has policies for protecting users and maintaining the integrity of the platform, and I respect that.

If my existing developer account cannot be reinstated, I have one final request:

**Is there any legitimate way for me to create a new developer account in the future?**

I want to be very clear that I am **not asking for a way to bypass Google's enforcement**.

If I were given another opportunity, I would:

* Never publish the same app or substantially similar violating functionality again.
* Carefully study and follow all Google Play policies before publishing.
* Take additional precautions with privacy, authentication, metadata, and app functionality.
* Accept Google's review decisions and compliance requirements.
* Use the account only for legitimate software development.

I’m still a student, and I’ve spent the last two years learning programming and building real-world projects. Publishing applications on the Play Store has been an important part of my learning and career journey.

Having no ability to publish Android applications in the future feels extremely difficult, especially at this stage of my career.

I understand that actions have consequences, and I am not asking Google to ignore the violation. I’m simply asking whether there is **any legitimate path forward after learning from my mistakes**, even if my previous account can never be restored.

If anyone here has been through a similar situation, especially developers who had their accounts terminated and later found a legitimate way to continue their career, I would really appreciate hearing your experience.

Thank you to everyone who takes the time to read this.

https://redd.it/1wzpgko
@reddit_androiddev

Product tours, onboarding and feature showcases for Compose Multiplatform

https://redd.it/1wzspys
@reddit_androiddev

What it actually takes to share one set of strings between Android and iOS

If you have tried keeping strings.xml and Localizable.strings in one translation project, you know the problem is not the words, it is the placeholders. Some things I learned while building a converter between the syntaxes:

* The simple cases are mechanical: %s to %@, %d to %lld. The German translation that swaps two arguments is not. You have to emit positions like %1$s, but only for strings that need them, or Android Lint complains about the ones that do not.
* Types matter. %.2f on Android has to stay a two-decimal float on every platform, including {balance, number, ::.00} in an ICU message for the web.
* Plurals have three shapes: <plurals> on Android, %#@count@ substitutions in .stringsdict, and {count, plural, ...} in ICU. They describe the same thing, so they should land in one key.
* A literal % is written as %% only when the string is a format string, so a banner saying "50% off" without arguments must not be doubled.
* Whatever you do must round-trip. If you convert a file in and out, you want the original bytes back, or your git diffs will never be quiet again.

Disclosure: I work on Localizely and we shipped this as "universal placeholders". Docs with the full syntax table: [localizely.com/universal-placeholders/](https://localizely.com/universal-placeholders/)

How are you handling this today, separate projects, a script, or copy by hand?

https://redd.it/1wzwyll
@reddit_androiddev

First time iOS -> android is slow emulation the norm?

Ok I m new to kotlin new to android dev. Done swift Xcode dev product is online in ios appstore.

I loaded a fraction ( say 10%) of code to kotlin hoping for the basics to simulate, run the pixel 9 emulator and it has been nothing but “google play services isn’t responding”

Is it impossible to dev without a physical android phone? Or am I just hitting the wrong spots of the ui rendering .

Please help thanks

https://redd.it/1wzxry3
@reddit_androiddev

Publish Android Apps: F1 Theme

Hi everyone, I'm not a developer, and I haven't even studied. I'm developing an F1-themed app with AI and I'd like to ask you some questions.

All the AIs are telling me that in order to publish the app, to use copyrighted terms, to monetize it, to use pilot photos, monthly and annual subscriptions, etc., I must of course have official licenses, rights and permissions from FOM.

There are many f1-themed apps on the play store that have everything mentioned above, and more, but they probably have nothing between licenses, permissions, etc. In fact, many apps write that they have no official licenses or permissions.

But don't they risk anything? I'd like to go ahead with my app because I believe in the project, and I'd like to see it published on the play store.

Thank you all for your answers!

https://redd.it/1wzzfzg
@reddit_androiddev

Done with creating these similar apps.Need something worthwhile for now

I've created some decent to basic apps, but realised this is just a loop.

I don't enjoy designing much which is probably the sole of app dev in android.

I've tested alot of stuff , but can't really get hold into it.

My pc specs are limited, so ASOP is not an option.

I've decently curated a portfolio and add stuff to existing things, but I need something which is deep in this field.

I'm done writing screens, viewmodels, connecting stuff, entrypoints.

It's just same.

Anyone who can guide me, I've explored spring boot,but it's again same Architecture or more or less same thing.

https://redd.it/1x01uf6
@reddit_androiddev

My first app failed Google's production access review. The second passed — here's what changed

A few months ago I tried to get my first Android app into production and got rejected after the closed test.

Technically, I had enough testers. The problem was that the actual testing was pretty bad.

A lot of people joined because I asked them to, but some never installed the app at all. Most of the people who did install it opened it once, registered, clicked around for a bit and never came back.

That app required an account, so I could actually see this in the login data. For almost everyone the registration date and last login date were the same. I was basically the only person regularly coming back after updates and testing new builds.

Google rejected the production access request. The email didn't give me one exact reason, but it listed two possible ones: testers weren't engaged enough, and I hadn't followed testing best practices, including collecting feedback and making changes during the testing period.

So with my next app I approached the whole thing very differently.

The app is called AutoSkan. It's an Android OBD diagnostic app, and this time I treated the fourteen days as an actual QA and development period instead of a timer I had to wait out.

I had fourteen accounts in the test when I applied. Some were mine or belonged to family members and four were external testers. The group also changed during the testing period as I found new people.

And no, I didn't suddenly have twelve people enthusiastically testing every build and sending me bug reports every evening. Nothing like that happened.

What changed was mostly what I did on my side.

I had four Android phones available to me and after updates I kept going through the app on those devices. I also started running structured audits. One focused on UI and UX, one on performance, and later I did a broader pass over performance, UI and correctness.

That uncovered a surprising amount of stuff.

There were screens that became dead ends without a paired Bluetooth adapter, Android 16 navigation problems, Bluetooth sessions living longer than they should, live vehicle data continuing to poll in the background, UI breaking with larger system fonts, issues around deleting exported data, and edge cases where a partial scan could look more complete than it actually was.

I also did a proper performance pass. Cold startup improved from a median of 468 ms to 370 ms on the device I was measuring, memory use went down, some work moved off the UI thread and PDF/export operations stopped blocking the interface.

Across the three main audits I documented 131 findings. That's not 131 crashes or critical bugs — it included UX issues, performance findings, regressions, edge cases and design decisions. 125 were closed and six were deliberately deferred.

The automated test suite grew from 192 tests in an earlier version to 257 by the later build.

I also tested on physical Android phones, used an Android 16 emulator with different screen sizes and text scaling, and tested with a real OBD adapter and a real car. One of the older-car K-line tests didn't even fully succeed, but that was useful too because it exposed failure cases that needed to be handled better.

The external tester feedback itself was mostly positive. They weren't finding dozens of bugs.

Most of the problems came from my own audits.

I kept notes separating actual tester feedback from things I found internally, instead of pretending every bug had been reported by a tester.

Once the testing requirement was complete, I applied for production access.

This time Google approved it in less than a day.

Obviously I can't know which signals Google actually used internally, so I don't want to present this as some formula for getting approved.

But having gone through one failed attempt and one successful one, the biggest difference was pretty clear.

The first time I had testers enrolled.

The second time I was actually testing the app.

So if you're doing the fourteen-day closed test now, I wouldn't treat it as a

countdown. Keep touching the app. Test different devices. Ship improvements. Find your own problems if your testers don't find them. Keep track of what changed and why.

You probably don't need twelve people producing detailed QA reports every day. I definitely didn't have that.

But when those fourteen days are over, you should probably be able to show that something real actually happened during them.

https://redd.it/1x01rq9
@reddit_androiddev

guest mode

Inspired by this article: `https://curvise.net/the-phone-features-i-cant-believe-we-dont-have/`

I would like to create something like this. My take is: Build an app with a (fake) phone app that can only call one specific number (for example: 911 in the U.S., 112 in EuropeJ). A (also fake) message app that shows only one message. A (also fake) photos app with a chosen number of photos (that can off course not be deleted). A calculator (maybe with a build in specific code to get out of the app). A fake settings screen that shows only if wifi is on and the battery percentage (maybe with a wifi toggle that when selected shows a specific message to the user that changes cannot be made).

What else would you add?
And also: how would you make shure the phone is completely locked (so no status bar, no back/home button or disabled back/home button, no recent apps, no app drawer,...) with the exception of the code in the calculator?

https://redd.it/1wzy507
@reddit_androiddev

Building the same build tooling for Xcode and Gradle, and how differently the two went

I work on Tuist. For years we've built caching and build/test insights for Xcode projects, and earlier this year we added Gradle support. I didn't expect how different the two would be. The Xcode integration took us months, and Gradle took about three weeks. Some of that is because the server side already existed, but most of it comes down to Gradle being designed to be extended and Xcode not.

Take remote caching. Xcode 26 added compilation caching, but the only way to plug in a remote cache is to run a daemon that speaks an undocumented gRPC protocol over a Unix socket, and Xcode makes thousands of calls to it during a build. On Gradle we implemented BuildCacheService and that was pretty much it, because Gradle already decides what's cacheable and computes the keys. The granularity is different too. Gradle caches whole tasks, so a large project does a few hundred lookups per build, while Xcode caches compilation units and does thousands, which makes network latency matter a lot more on the Xcode side.

Build data went the same way. With Xcode we parse a binary activity log after the build finishes. The format isn't documented and changes between Xcode versions, and it's written asynchronously, so sometimes it isn't on disk yet when our post-action runs. With Gradle we register a listener and get each task's outcome, duration and cache key as it finishes. For flaky test quarantine we pass -skip-testing flags to xcodebuild, and on Gradle we add the tests to excludeTestsMatching before the test task runs.

I'm not trying to bash Apple, they have their reasons. But if you only work with Gradle, it's easy to forget how much its plugin API gives you. I wrote the longer version here: https://tuist.dev/blog/2026/03/16/xcode-and-gradle-two-worlds-one-infrastructure, and the plugin is open source if you want to look at the BuildCacheService implementation: https://github.com/tuist/tuist/tree/main/gradle

Has anyone here written their own BuildCacheService? I'd be curious what you ran into.

https://redd.it/1wzxuyh
@reddit_androiddev

Google Play wants organization verification for my payments profile, but I'm an individual

Hi everyone,

I've had a Google Play developer account for years. It's an individual account, and the identity payments profile under "About you" is also individual.

When I set up the merchant payments profile used for payouts, I picked "Organization" by mistake, even though every detail on it is my own personal name and address. I've never had a registered company or a VAT number.

In the past Google asked me to verify this same merchant profile and accepted my government ID. Now a new verification request asks for a VAT attribution certificate or a company registration document, which I simply don't have because no company exists.

According to the help pages, a payments profile can't be switched from Organization to Individual, and the merchant profile can't be unlinked from the developer account. So I'm stuck: there's a significant balance pending on the profile, and the account has apps with active users and subscriptions that I really don't want to lose.

I contacted support and opened a ticket more than a week ago, but I still haven't received any reply.

Has anyone been through this? Is there a way to get support to fix the profile type, or to verify it as an individual like before?

Thanks.

https://redd.it/1x06pte
@reddit_androiddev

Payouts on hold since August, merchant verification rejected 15+ times with "the reason you provided is not clear". Has anyone ever reversed this?

https://redd.it/1wzw4b7
@reddit_androiddev

Custom Launcher Project

https://redd.it/1wzxjfj
@reddit_androiddev