Build and ship an Android app from a phone with Claude Code in the cloud

A solo developer in Ukraine built Molfar, about 35,000 lines of Kotlin, with Claude Code coding in the cloud and every build tested on a phone; seven Play Store releases shipped in two weeks.

Done withClaude CodeinGitHub· Nov 9, 2026

What they did

The developer behind Molfar, a free Android app for chatting with several AI models, works entirely from a phone. They open Claude Code from the Claude mobile app with a short task; Claude plans, writes code in a cloud session with no Android SDK or emulator, runs what checks it can and commits. Those checks are plain-Java test harnesses for the app's logic, each with a deliberate break it must catch, a compile of the UI against stubs, and a script that checks strings in all five languages. The person builds the APK on the phone in NanoIDE, tries the change and replies with a screenshot. GitHub Actions makes the signed build and the person uploads it to Google Play. Rules, lessons and handoffs between sessions live in CLAUDE.md.

How it went

The Kotlin rewrite started on 24 September 2026, Claude has worked in the repo since 15 October, and seven public releases went out between 25 October and 7 November. By 8 November the project had about 35,000 lines in 220 files. At least five bugs passed in the cloud but broke on phones, including a regex Android does not support, which took a day to find, and an Android 15 layout bug that users saw first. It was fixed the same day as release 2.0.7.

Worth knowing

With no emulator, real users are the first to see some layout and runtime failures, so each failure class got its own check or rule afterwards. Claude remembers nothing between sessions; whatever is not written in CLAUDE.md is lost, and even the test tools are rebuilt from the README each time. The write-up itself was drafted by AI from project notes and approved by the developer.

Try it

With Claude Code· 4 parts to fill in

You are working in [my app repo] in a cloud session without [the SDK or emulator my app needs]. For each task I send: read CLAUDE.md first, plan briefly, make the change, and run every check you can here, such as unit harnesses for pure logic, a compile against stubs and [my resource or lint script]. Before relying on a new check, break the code on purpose and confirm the check fails. Commit, then report in three parts: what you did, what you could not check, and exactly what I should test on [my device]. Record any lesson in CLAUDE.md. Wait for my result before the next change.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related