What We Build with Kotlin
- Android apps, the main use case: new native apps with Jetpack Compose interfaces;
- backends: APIs and services built with the Ktor and Spring Boot frameworks;
- shared code for mobile platforms: business logic written once and used on both Android and iOS, while each platform keeps a native UI;
- internal tools: build scripts, developer utilities and small desktop apps.
When We'd Recommend Something Else
- You need a single codebase for both logic and UI on iOS and Android. In that case Flutter or React Native is simpler.
- A large, stable Java project is already running on the server. Rewriting it in Kotlin just to follow a trend makes no sense; new modules can be added gradually.
- Your team writes JavaScript or PHP and doesn't plan to learn a new language. For the backend, it's better to stay on the stack you know, since Kotlin has fewer ready-made solutions and specialists there.
Migrating from Java to Kotlin
Rewriting an entire app in one go is risky and expensive. We migrate projects gradually:
- all new code is written in Kotlin from the start;
- parts that change often or break often are rewritten first;
- stable legacy modules stay in Java until their turn comes;
- every step is covered by tests so the app's behavior doesn't change.
Android Studio can convert Java files to Kotlin automatically, but the result almost always needs manual refinement: mechanically converted code works, but it doesn't take advantage of the language.
Kotlin Multiplatform: Shared Logic for Android and iOS
This approach makes sense when you already have a strong native Android app and need an iOS version. The shared module holds everything that doesn't depend on the screen: server communication, data models, calculations, validation rules. Each platform still builds its own UI, Jetpack Compose on Android and SwiftUI on iOS, so users get apps that feel native while prices, discounts and validations work the same everywhere.
If you're starting from scratch and both platforms matter equally, we compare this option with cross-platform development and recommend the one that is cheaper to maintain.
New Project or Improving an Existing One
In a new project, we lay down a structure that is easy to grow from day one: separate layers for UI, logic and data, automated tests for key scenarios, and code style checks on every change. That way the app won't need a rewrite a year or two down the road.
With an existing project, we start with an audit. We look at how background tasks are organized, whether there are memory leaks, which libraries are no longer maintained, and where the app crashes most often. You get a clear, prioritized list of issues and a recommendation on what to fix first.
What to Prepare Before Kickoff
- A description of the app's features and users, or your existing design files.
- For an existing app: repository access, crash reports if you have them, and a list of known issues.
- Backend and API documentation, plus any third-party SDKs or hardware the app must support.
- Google Play developer account details, or a decision on who will create it.
What Affects Cost
- Type of work: a new app, migration from Java, a shared iOS module, or backend code.
- Size and condition of existing code: how many modules, whether there are tests, how outdated the libraries are.
- Integrations: backend, payments, notifications, third-party SDKs, and hardware.
- Quality requirements: test coverage, documentation, automated checks in the build pipeline.
After an audit or requirements review, we break the work into phases and explain what each one includes.
Frequently asked questions
Will the app run faster after switching to Kotlin? The language itself won't make the app noticeably faster for users. The gains are stability, fewer crashes and faster development of new features.
Can part of the code stay in Java? Yes. Both languages work fine in the same project, so there's no need to convert everything.
Is Kotlin Multiplatform a good fit for a new product? Yes, if a native UI on each platform matters to you. If the priority is one codebase for everything, a cross-platform framework is usually the simpler choice.
Will you take over support for an app built by another team? Yes. Before changing anything, we review the code and identify which parts are fragile and which ones are solid.
Can you build the backend in Kotlin too? Yes, with Ktor or Spring Boot, if your team prefers one language for both the server and the mobile app.
Can you help with an iOS version of our Android app? Yes. We can move business rules into a shared Kotlin module so both apps calculate prices, discounts and validations the same way.
Why Promodex
Our portfolio of 750+ projects since 2015 includes mobile work such as the Telcell Wallet app. Designers and developers are an in-house team, so we don't outsource work or lose context between phases. We set up automated code checks from the start so the language's flexibility doesn't turn into inconsistent styles, we explain technical decisions in plain language, and after release we keep supporting and evolving the app.