Work with Redigit

Kotlin Multiplatform and Android engineering for teams shipping cross-platform products — from one codebase to Android, iOS, web, and desktop.

What Redigit does

Redigit is my studio, backed by 11+ years of production Android and cross-platform engineering across fintech, healthcare, and developer-tooling teams. I take Android and Kotlin Multiplatform work that has to be right — shared code across platforms, libraries other people depend on, migrations that can't break the API their users are already shipping — and I ship it. The open-source projects on this site are the same work in public, recognized with a GitHub India grant as one of 15 open-source contributors nationally.

Where the 11+ years comes from

  • Developer tooling, currently. Maintaining and extending a production PDF SDK — including a legacy-UI-to-Compose migration and the custom Gradle tooling that automates its release process.
  • Fintech, end to end. Ran mobile delivery for a lending platform from proposal through build to maintenance, directing a small team's work and instituting the code-review discipline that kept technical debt down. Picked up backend and DevOps along the way — Spring Boot, Docker, Kubernetes, Jenkins.
  • Healthcare. Owned mobile architecture across multiple apps in a regulated domain, refactoring shared internal libraries and steadily paying down technical debt other teams had left behind.
  • Logistics. Built real-time fleet-tracking systems — live vehicle tracking, mapping integrations, remote vehicle control — for a product doing with a fleet what Uber or Ola do with a ride.

How we work together

Audit

A focused review of an existing Android or KMP codebase — architecture, public API surface, and the real risk in a multiplatform migration. Fixed fee, one to two weeks, ends with a written plan.

Fixed-scope build

A defined deliverable — a library, an SDK, a Compose Multiplatform migration — scoped, priced, and shipped against a clear definition of done.

Retained engineering

Senior KMP and Android capacity for a team that needs it, by the month. Reviews, architecture, and the hard parts of the shared module.

The kind of problem we solve

  • Take an Android-only library multiplatform without breaking it. DrawBox went from Android to Android, iOS, web, and desktop on one source set — and kept its public API. That is a migration, not a rewrite, and it is the one we do best.
  • Build tooling that works offline and keeps no secrets. Universal Context Pipeline is a local-first MCP server: no cloud, no telemetry, a single Rust binary. When the constraint is privacy, the architecture has to earn it.
  • Ship developer tooling that maintains itself. statsvg_rs renders and republishes its own stats every six hours with zero servers. Small, boring, and it never pages you.

Have something like that?

Tell me what you're building and where it's stuck. I read every email.

Email akshay@redigit.io