Kotlin

Safety and concision on native Android

Kotlin is the language Android itself recommends for native development. It fixes two long-standing pains of the platform: Java's verbosity and crashes caused by null references. The type system treats null as an explicit case, so an entire family of errors that used to surface in users' hands is caught at compile time instead. The result is code that is shorter, easier to read and harder to break.

Our default for cross-platform apps is Flutter, and that is what we recommend for most projects. Kotlin comes in when the product is Android by definition: deep hardware integration, background services, platform features that a cross-platform layer only reaches with friction. In those cases, going native with Jetpack Compose tends to be simpler and more stable than forcing the abstraction. We pick the tool for the problem, not the trend.

For whoever hires us, this means an app that keeps pace with the platform instead of chasing it: new Android capabilities land in the native APIs first. It also means full interoperability with Java, which lets us modernize an older codebase step by step instead of rewriting everything at once. And it means a large market of developers, so the project is not hostage to whoever wrote it.

• Native Android apps with Jetpack Compose
• Deep hardware and sensor integrations
• Background services and data sync
• Modernizing existing Java codebases
• Apps for wearables and Android TV