Native Android apps
Interfaces in Jetpack Compose and logic in Kotlin – matching the habits of Android users.
Android apps
We build Android apps natively in Kotlin and Jetpack Compose. Where a quick prototype or a shared code base is more economical, we use React Native.
Our approach
For apps on iOS and Android we share no code between the platforms. Both sides are built natively and connected through a versioned exchange format that we treat like a contract. That way each app feels at home on its system.
Scope
Interfaces in Jetpack Compose and logic in Kotlin – matching the habits of Android users.
The Android version of an existing iOS app, with the same features and compatible data exchange.
When time matters more than the last detail: one code base for both platforms with Expo and TypeScript.
REST APIs, authentication and synchronisation with the systems you already run.
Technology
Kotlin and Jetpack Compose for native apps, React Native with TypeScript for shared code bases.
Questions
Because each platform has its own patterns. Shared code often leads to compromises that users notice on both systems. Instead we share a clearly versioned data format – dates in ISO 8601, stable enum values and amounts in cents – so both apps can exchange entries reliably.
For prototypes, internal tools or apps that mainly show forms and lists. We have built apps of our own with React Native and Expo and know the limits, for example with native modules such as document scanners.
Yes. We analyse the features and data model of the iOS app, define the shared exchange format and rebuild the Android version natively.