Why we chose Kotlin and Jetpack Compose

When you're building a code generator, your stack choice is permanent. Every line of every app you ever ship looks like that choice. We thought about this for months.

Why not Flutter or React Native#

Both are good products. Both are popular. Both are not native. Flutter draws its own pixels with Skia — beautiful, but never quite right. React Native bridges to native components — fast, but the bridge has overhead and quirks. We wanted apps that platform engineers couldn't fingerprint as 'cross-platform'. That meant native or nothing.

Why not Java + XML#

Because it's 2026. Kotlin is the official Android language, the documentation is Kotlin-first, the ecosystem has moved on. XML layouts are dead. Compose is what Google ships internally and what every modern Android codebase converges to within two years.

Why Kotlin#

Null safety, coroutines, extension functions, and a type system that's strict enough to keep AI-generated code honest. Kotlin's compiler will catch a generated bug before the user ever sees it. That's worth a lot when the author is a model.

Why Compose#

Declarative UI maps cleanly to AI generation. Every screen is a function from state to UI. The model thinks in components; Compose renders in components. It's the same mental model from prompt to pixel.

The future-proof bet#

Compose Multiplatform is coming. When iOS support lands at Apirex, our Compose investment carries forward. We can share design tokens, theming, and even some Composables across platforms while still emitting native Swift where it matters.