Technology & engineering

The stack behindapps thatkeep working.

Swift, Kotlin, Flutter and React Native on the client; typed APIs, PostgreSQL and managed cloud behind them. Chosen for your product's next three years — not for our CV.

See our process

Native or cross-platform, in writing

Typed end to end

CI, tests and phased rollouts

05 — Technology

Architecture first. Logos second.

We choose tools for the product's next three years, not for our CV. Here's how a typical system fits together.

Native when the device is the product.Camera, sensors, wallets, widgets and heavy animation get Swift and Kotlin.
Cross-platform when speed to both stores matters.Flutter or React Native, with native modules where they earn their place.
Boring infrastructure, interesting product.Proven databases and managed cloud, so your budget goes into what users see.

Reference architectureTyped end to end

Mobile & web appsClient layer

iOSSwift · SwiftUI

AndroidKotlin · Jetpack Compose

Cross-platformFlutter · React Native

Web & adminReact · Next.js · TypeScript

API layerContracts

Node.jsPythonOpenAPIWebhooksRate limiting

ServicesIntegrations

Auth · OIDCPayments · StripePush notificationsMaps & locationAnalyticsRealtime

DataStorage

PostgreSQLRedisObject storageSearch

CloudInfrastructure

AWSFirebaseSupabaseCI/CD

06 — Engineering standard

The spec sheet behind every build.

Quality isn't a value statement. It's a list of things that happen on every project, whether anyone is watching or not.

ARCHITECTURE: Modular, feature-based codebasesDecisions recorded as ADRs so the reasoning survives the people.
CODEBASE: Typed, linted, reviewed on every pull requestNo merge without a second senior engineer's approval.
AUTOMATION: CI builds, tests and signs every mergeInstallable builds for your team, daily if you want them.
SECURITY: OAuth 2.0 / OIDC, encrypted storageChecks aligned with OWASP MASVS before every major release.
ANALYTICS: Event schema agreed during designSo launch day answers questions instead of raising them.
APIS: Versioned contracts and latency budgetsGenerated clients mean the app and server can't silently drift.
PERFORMANCE: Cold-start and frame-time budgetsMeasured on mid-range devices, not just the latest flagship.
RELEASES: Feature flags and phased rolloutsProblems reach 5% of users, not all of them.
HANDOVER: Documentation your next hire can useSetup in under an hour, or we fix the docs.

Release 2.4.0 RC3Healthy

Lint & type check0 issues
Unit tests412 passed
UI tests · device farm86 passed
Build & signiOS · Android
Phased rollout25% → 100%

Crash-free sessions99.94%

Cold start · budget 1.5s1.1s

API p95 · budget 300ms142ms

Example release dashboard

Start a project

Let's build the one they keep.

Tell us where you are today — idea, prototype, or existing product — and we'll help define the smartest next step.

info@kurchu.com

Two-minute brief

Where are you today?

Currently scheduling discovery sprints · Reply within one working day