Kotlin app development

Kotlin is the language Android is written in today: less ceremony than Java, null safety in the type system, coroutines instead of callback chains, and full interoperability with the Java code a project already has. That last point is what makes it practical — an existing app does not have to be rewritten to benefit.

New applications start with the decisions that are expensive to change later: the minimum Android version, how data is stored and synchronised, what happens without a network, which permissions the app really needs, and how it will be released. Everything after that is ordinary work.

What we do here:
— Android applications in Kotlin with Jetpack Compose or classic views, whichever fits the project;
— an offline-first data layer: Room, background sync, a queue of requests that survive a lost connection;
— integration with your backend — REST or GraphQL — with sane timeouts, retries and error states;
— work with the device: Bluetooth Low Energy, camera, geolocation, notifications, files;
— release: signing, Play Console, staged rollout, crash reporting and the first response to what it shows.

Existing apps are the other half. We take over a project written by someone else, get it building on the first day, write down what is fragile, and only then move it forward — including step-by-step migration from Java, file by file, with the app shippable after every commit.

Our own Android work is public: Tethys is an app that gave COSMIQ+ dive computers back their sync after the manufacturer's service shut down — Bluetooth Low Energy, a reverse-engineered protocol, local storage and export in portable formats.