at i/o yesterday google shipped a Migration Assistant inside android studio that takes an existing iOS app and hands you back a native kotlin port in hours instead of weeks. it maps your features, converts your assets — storyboards, svgs — and rebuilds the ui in jetpack compose using google's recommended libraries. it's genuinely good. it's also aimed at the wrong half of the problem.
what was announced#
the migration assistant ports from iOS, react native, or web frameworks into native android. google's framing is "weeks of manual porting becomes a streamlined agentic workflow." that's not marketing fluff — it's basically formalising what devs have been doing informally with LLMs for two years, except now it's wired into the IDE and outputs compose, kotlin, and the jetpack patterns google actually wants to see.
so the objection that's kept thousands of solo iOS devs off android — "i'd have to learn kotlin and rewrite the whole thing" — is mostly dead. good riddance.
why this matters for indie devs#
the reason most one-person iOS shops never ship android was never really the language. it was the tax of standing up a second platform. and that tax has two parts: a second codebase, and a second store. google just deleted the first part. it did nothing about the second.
here's what the migration assistant does not touch, because none of it lives in your kotlin:
- a brand-new play store listing, from zero
- screenshots across play's device matrix — phone, 7" tablet, 10" tablet — plus a feature graphic the app store doesn't even ask for
- the data safety form, which is a rejection trap even for people who've shipped to play before
- the content rating questionnaire
- the closed-testing requirement that makes a fresh personal account run 12 testers for 14 days before it can even touch production
the agent ports your code. it cannot port a play console account you've never opened.
the wall just moved#
porting didn't remove the wall. it relocated it. the blocker used to be "i'd have to rewrite my app." now it's "i have a working android build sitting right here and fourteen console forms i don't understand standing between it and a download button." that's a better problem to have. it is still a problem, and it's the one nobody demos on stage.
the stora angle#
that second half — the listing, the screenshots, the compliance pass, the data safety form, the actual submission — is the half stora exists for. point it at the repo your migration assistant just generated: it captures play-spec screenshots across every required device size, drafts listing copy from what the app actually does rather than a template, runs a pre-submission compliance scan that catches the data safety and policy mismatches before google does, and publishes. the porting agent gets you a build. stora gets you a live listing.
the call#
the code was never the wall. apple and google spent a decade quietly making submission the wall, and a porting agent doesn't lay a finger on it. port your app this weekend — seriously, try the assistant, it's good. just budget a real chunk of time for the part google left off the keynote slide.