New Android apps in Kotlin
Greenfield Android clients where new code starts in Kotlin against the Android SDK and the libraries your product needs.
Mobulous is a mobile app development company that builds Android apps in Kotlin and extends existing Java codebases without a forced rewrite. We do not sell Kotlin Multiplatform, Jetpack Compose showcases or server-side Kotlin as shipped product lines on this page. 700+ apps delivered, 12+ years, ISO 27001 certified.
This page is about language-level Android delivery: new modules in Kotlin, mixed Java/Kotlin repositories, and Play Store submission. Platform depth for Android as a whole sits on our Android app development page. Dual Swift and Kotlin product builds sit on native mobile app development.
Greenfield Android clients where new code starts in Kotlin against the Android SDK and the libraries your product needs.
New features and modules written in Kotlin beside existing Java. Interop is the rule, not a temporary workaround.
File-by-file conversion where tests and active feature work make it safe. Not a billed full rewrite by default.
Android clients that share APIs with web or iOS surfaces. Stack rows in apps.csv often list Kotlin beside React JS or Node for that reason.
Signing, store listing support and release coordination for Android builds after scope is agreed.
Ongoing work on repositories that will stay mixed for years. Half-migrated is a normal steady state.
Most Kotlin work is not greenfield. It is an existing Java Android app, and the real question is how much to convert and when. Broader Android platform choices, including Compose depth, stay on Android app development.
Nothing forces a full rewrite, and that is the most important fact in this decision.
Ship features in Kotlin while Java modules keep working. Interop is what most real engagements need.
An automated conversion compiles and still reads like Java. Idiomatic Kotlin is a separate pass with reviews and tests.
Java code calling Kotlin can still pass null into something that does not expect it. Platform types remain a risk until annotations and wrappers catch up.
Converting one without tests is a rewrite pretending to be a migration.
There is no dependency forcing function that requires Kotlin everywhere before you ship.
Many production apps stay mixed for years while feature work drives conversion.
A small codebase, a team already fluent in Kotlin, or a rewrite already planned for other reasons.
A large legacy app with thin tests, no Kotlin experience on the team, and no feature work driving the change.
New Android projects default to Kotlin because Google standardised on it and the tooling assumes it. That does not make Kotlin cross-platform, and it does not repair a weak architecture.
Kotlin’s type system pushes null handling into the compiler for Kotlin-authored code. It reduces a common class of NullPointerException inside Kotlin modules. It does not remove nulls arriving from Java, reflection or unannotated platform APIs until those boundaries are handled deliberately.
Structured concurrency makes asynchronous Android work easier to read and cancel than deep callback chains. It improves maintainability when the team uses it consistently. It is not a performance guarantee on its own.
This is what most commercial engagements need: call Java from Kotlin and Kotlin from Java in one Gradle project. Teams keep legacy modules while new work ships in Kotlin.
Build scripts can use the Kotlin DSL. That is a tooling choice for the repository, not a product feature for end users. Version alignment between the Kotlin compiler and libraries remains a maintenance concern on every upgrade.
Compose is Google’s modern UI toolkit for Android. This page does not claim Compose as a delivered product line in apps.csv. Deep Compose versus XML guidance belongs on Android app development.
Kotlin is not a cross-platform product on its own. Kotlin Multiplatform, Ktor and server-side Kotlin are not evidenced as delivered lines in apps.csv. Bad module boundaries stay bad after a language change.
Discovery starts with the repository you have: module map, test coverage, Gradle versions and which packages still change every release. Free functional and technical discovery calls come first. Mutual NDA before detailed discussion.
We write new work in Kotlin where it is safe, leave stable Java alone when conversion buys nothing, and only convert hot paths when tests and active feature work justify it. If you need two store-native codebases, Swift plus Kotlin, that decision lives on native mobile app development.
Source code and IP transfer to the client on delivery. Four months free post-launch support is standard in every contract.
Five Android products where apps.csv records Kotlin. The first three list Kotlin first in the stack. UDEL is included because it is the Kotlin row not already used on rebuilt Flutter, React Native, cross-platform, native or Android portfolios. No install counts or store ratings are attached here. More shipped work is in our development portfolio and app and software development case studies.
Digital billing and filings on Android: customisable bills and tax invoices, multiple businesses, estimations, quotations, debit and credit notes, delivery challans, low-stock alerts, debtors and creditors, and tax filing surfaces. Stack in apps.csv: Kotlin, React Js, Node JS.
Support app for Syrotech OLT and ONT users: register a device by QR or by entering MAC, model and serial, then reach real-time technical support and guided troubleshooting. Framed here as a Kotlin-first Android client for device support, not as an IoT lab story. Stack: Kotlin, Swift, Node Js, React JS, MongoDB.
Healthcare access in India on a Kotlin-led Android client with a web layer: doctor appointments, health records, home healthcare and hospital management. Described here as Kotlin Android delivery for clinical workflows, not as a wearable companion. Stack: Kotlin, Swift, PHP, React JS.
University of Delaware Connect: academic and research hub, campus life, athletics, study abroad, multi-campus navigation and admissions resources. Kotlin appears in a multi-surface stack with React JS, Node.js, HTML5 and Swift. Included because this Kotlin row is not already claimed on the rebuilt Flutter, React Native, cross-platform, native or Android portfolios.
Student accommodation across India: search and filter hostels and PGs, verified listings, landlord portal, booking and availability, community resources and safety features. Kotlin sits mid-stack with React JS, Node.js, HTML5 and Swift. Framed here as the Android Kotlin client inside that product, not as a native dual-codebase case study.
These are language-scoped Android services. They sit beside our mobile app development services when you need the wider mobile programme, not only Kotlin.
New Android applications and modules written in Kotlin against agreed scope.
Incremental conversion plans driven by tests and active feature files, not a forced rewrite.
Ongoing delivery on repositories that will remain mixed while product work continues.
Architecture and migration advice for teams deciding how much Java to leave alone.
Store submission support for Android builds after QA on the devices your users run.
Four months free post-launch support, standard in every contract, then ongoing maintenance if you choose it.
No week counts and no published prices on this page. Scope sets both after free discovery.
Functional discovery covers the product and users. Technical discovery covers the repository, Gradle versions, test coverage and release constraints. Mutual NDA before detailed discussion.
Module map, mixed-language hotspots and conversion candidates are written down before UI promises. Greenfield Kotlin work skips this gate.
Discovery becomes a scope document you keep. Proposal and agreement follow that artifact.
Kotlin modules, interop with remaining Java, and Android UI work against the agreed backlog.
QA follows the device and OS matrix written in scope, not a single lab phone.
Store packaging and submission support after release criteria are met.
Source code and IP transfer on delivery. Four months free post-launch support is standard, then optional ongoing maintenance.
Eight apps.csv rows list Kotlin. We describe primary versus mid-stack honestly and do not invent Multiplatform or Ktor delivery.
Incremental Kotlin beside Java is the default. Full conversion is recommended only when the codebase and team justify it.
This page owns Kotlin-by-name search. Platform Android and dual-codebase native stay on their own URLs.
700+ apps delivered, 500+ clients, 12+ years since 2013, 30+ countries, 100+ experts.
4.7/5 on Clutch (103 reviews), 4.8/5 on GoodFirms (65+ reviews), 5.0/5 on G2 (5 reviews), 4.3/5 on Google Reviews.
ISO 9001:2015, ISO/IEC 27001:2022, CMMI Level 3. Source code and IP transfer on delivery. Four months free post-launch support, standard in every contract.
"Their friendly nature and open communication set them apart from competitors."
Verified on Clutch →"Overall it was a great experience working with Mobulous. They are very professional and stick to their commitments done on the pre-sales stage. The team is well organised and work on the recommendations and feedbacks."
Verified on GoodFirms →"Mobulous is excellent at interpreting and bringing client ideas to life. The Mobulous team is very responsive and quick to execute client requirements."
Verified on GoodFirms →Mobulous rates 4.7/5 on Clutch (103 reviews), 4.8/5 on GoodFirms (65+ reviews), 5.0/5 on G2 (5 reviews), and 4.3/5 on Google Reviews. Clutch → · G2 → · GoodFirms →
There is no single best vendor for every backlog. Prefer a partner that writes new Android work in Kotlin, leaves stable Java alone when conversion buys nothing, transfers source code and IP on delivery, and states post-launch support in the contract. Ratings such as 4.7/5 on Clutch (103 reviews) are context, not a substitute for those terms.
Mobulous provides Kotlin Android development, Java-to-Kotlin migration support and mixed-codebase maintenance. Apps.csv lists eight projects with Kotlin in the stack. Platform Android depth is on our Android page; dual Swift and Kotlin product builds are on our native page.
Look for engineers who treat interop as the default, can explain what null safety does and does not remove at Java boundaries, and will not sell a full rewrite when incremental conversion is enough. Ask what their last mixed Java/Kotlin repository still looks like in production.
Scope determines cost. Free discovery produces a scope document before any proposal. This page does not publish price bands or hourly rates.
Yes. Google made Kotlin a first-class language for Android and recommends it for new Android development. That is why new Mobulous Android modules default to Kotlin. It does not mean every legacy Java line must be rewritten.
Kotlin can target more than Android, including multiplatform and server options in the wider ecosystem. This page does not claim Kotlin Multiplatform, Ktor or server-side Kotlin as delivered Mobulous product lines, because apps.csv does not record them.
Agree scope, assess any existing Java repository, build in Kotlin with Java interop where needed, test on the Android versions your users run, then submit to Play Store. Mutual NDA and free discovery come first.
From the blog
Null safety, concision and Java interop: what changes when new Android work moves to Kotlin.
Continue Reading
Where Kotlin Android work sits against shared-codebase and web-app options before you fund a stack.
Continue Reading
What drives budget on Android and multi-surface products, drawn from delivery work across 700+ apps.
Continue ReadingBring the Android repository you have, or the product you want to start in Kotlin. 700+ apps delivered, 500+ clients, 12+ years, 4.7/5 on Clutch (103 reviews). Mutual NDA before detailed discussion. Source code and IP transfer on delivery. Four months free post-launch support, standard in every contract.
Related: Android app development · our development portfolio · app and software development case studies · estimate your project.
Related: Android app development, our development portfolio, app and software development case studies, estimate your project.