Android app development with Kotlin and Jetpack Compose
I build native Android apps in Kotlin and Jetpack Compose and take them all the way to a live Google Play listing, as one senior engineer working directly with you.
A lot of Android projects stall in the gap between a working build and an app real people can install. Store listings, signing keys, permissions, release tracks and the first round of user feedback all land at once, right when the budget is running out. I plan for that part from day one, because I've been through it with my own apps.
I build natively in Kotlin with Jetpack Compose, Android's current UI toolkit. That means the app follows the platform's own patterns, works with the Android share sheet and system features properly, and stays maintainable for the next engineer who opens the project.
Apps I've built and shipped on Android
Echoes Board is a visual curation app. You share a link from Instagram, TikTok, YouTube, Pinterest or the browser, and it lands as a preview card on a board, with notes, tags, status tracking, filtering, and export, backup and trash recovery.
FitCharge is a fitness tracker that brings step counting, workout logging and sleep tracking into one app, with weekly and monthly summaries. It stores data locally on the device.
Both are live on Google Play, and I designed, built and published each of them myself.
See my products →Kotlin and Jetpack Compose developer, not a cross-platform wrapper
Cross-platform frameworks make sense when you need iOS and Android from one codebase on day one. When Android is the priority, a native Kotlin app gives you full access to the platform, with no bridge layer between your app and the OS, and a codebase any Android engineer can pick up.
If you do need iOS as well, I'll say so on the scoping call and talk through the trade-off honestly, rather than pushing the stack I prefer.
An Android app for your existing web product
Many of the teams I work with already have a web app or SaaS product. Adding Android usually means connecting to the API you already run, or one I design for it, with auth that works the same way as on the web. Because I build web backends as well, the API and the app get designed together instead of negotiated across two contractors.
API development →Who this is for
- Founders who need an Android app in front of users without hiring a mobile team
- SaaS and web products adding an Android app on top of an existing backend
- Businesses with an app idea who want one engineer to own it from design to Google Play
What an Android build includes
Native Kotlin app
Screens built in Jetpack Compose, following Android's own patterns, with navigation and state that hold up as the app grows.
Platform integration
Share sheet, notifications, permissions and local storage handled the way Android expects, not worked around.
Backend connection
Your existing API or a new one, with authentication and offline behaviour decided up front.
Google Play release
Signing, store listing, screenshots, release tracks and the policy forms that block first-time publishers.
Post-launch updates
Crash fixes and improvements from real user feedback, shipped through staged releases.
How an Android project runs
- 01
Scoping call
What the app needs to do, who it's for, and whether native Android is the right call. You leave with a written plan.
- 02
Screens and data
Key screens and the data model agreed before the build starts, so there are no surprises halfway through.
- 03
Build with test builds
Regular test builds installed on your own phone, so you're reacting to the real app rather than mockups.
- 04
Google Play launch
Store listing, signing and release, published under your developer account.
- 05
Handover or retainer
A clean handover with documentation, or a rolling retainer to keep shipping updates.
Engagement options
MVP Sprint
Idea to shipped product, fast
From $1,000
4–8 weeks
Founders who need a real, usable v1 in front of users this quarter.
- Scoping workshop and a written technical plan
- Production build — app, API, database, auth, deployment
- CI/CD and a live deployment you own
- Regular demo checkpoints, async updates in between
Monthly Retainer
An embedded senior engineer, minus the hiring cycle
From $1,000 / month
Rolling, one-month minimum
Teams shipping continuously who need senior capacity without a headcount req.
- A fixed block of engineering hours each month
- Feature delivery, code review, and refactors
- Works inside your existing tools — Slack, board, standups
- Cancel or pause with notice
Architecture Audit
An honest read on what's already built
From $1,000
1–2 weeks
Teams inheriting a codebase, pre-fundraise diligence, or diagnosing 'why is this so slow'.
- Codebase, infrastructure, and cost review
- Written findings ranked by risk and effort
- A prioritized remediation plan
- A walkthrough call to go through the findings
Android development FAQ
Do you build for iOS too?
I build natively for Android. If you need iOS from day one, I'll tell you on the scoping call and talk through whether a cross-platform approach or a separate iOS build makes more sense for you.
Can you publish the app to Google Play for us?
Yes. I handle signing, the store listing and the release, under your own Google Play developer account, so the app and its reviews belong to you.
Who owns the code and the app listing?
You do. The code lives in your repository and the app is published from your developer account from the first release.
Can you add an Android app to our existing web product?
Yes. That's a common shape of project for me. The app connects to your existing API, or one I build alongside it, so web and Android share the same data and accounts.
How long does an Android MVP take?
It depends on the number of screens and integrations, but a focused first version usually fits an MVP Sprint of 4–8 weeks. You get a firm timeline after the scoping call.
Related services
Keep reading
Ready to talk about android app development?
Book a call or send a message — you'll hear back within a day.
