What ships
App Store and Play builds. Shared business logic where it belongs. Auth, payments, push, and the API the app needs. You get software you can install and try.
We build mobile apps meant for the stores. Shared product logic where it helps. Native interfaces where they matter. Kotlin Multiplatform is our default when that split is a fit. Flutter and React Native are valid production stacks. We do not treat them as demos that must be rewritten.
App Store and Play builds. Shared business logic where it belongs. Auth, payments, push, and the API the app needs. You get software you can install and try.
KMP when you need one Kotlin core and native UI. Flutter or React Native when you already have them, or when a shared UI framework is the cheaper credible path. Official Flutter and React Native pages include large production products. That is proof those stacks exist in production. It is not a prescription.
Agree the user workflow and the first slice. Then screens. Then store tracks. Security, hosting, and release requirements are assessed during discovery. They are not assumed from a generic control list.
Store accounts, signing, and the codebase stay with you.
You need iOS and Android for a defined workflow. Or you already have an app to extend.
A clickable prototype or a single platform first slice can come before two stores. We will say so in the fit conversation.
Stack and cost follow the workflow and what already exists. There is no public price list. Paid discovery produces the build estimate.