Shared architecture
Presentation, domain, data and UI layers. ViewModels, state/events, typed results, repositories and use cases — organized for real product work.
THE SWISS KNIFE FOR KMP
BOTH, ONE CODEBASE
BOTH, ONE CODEBASEThe production-ready Kotlin Multiplatform starter kit
Stop rebuilding the same app every time.
Build Android and iOS apps faster with a complete Compose Multiplatform scaffold—8 ready-to-adapt feature flows, 40+ screens, a 4-axis theming system, offline-first sync and AI-ready architecture—so week one is product work, not plumbing.
✱ launch pricing — 23 of the first 200 spots left
100+ developers build on KMP✱SK
one-time · full source · android + iosUNDER THE HOOD
Kotlin
Compose Multiplatform
Supabase
Firebase
RevenueCat
Material 3
Google Maps
Ktor Client
Room
GradleAndroidiOSEvery blade in the knife
Ready-to-extend auth
Login, registration, password reset, OTP and sessions. Fake auth for demos, Supabase-ready wiring, Firebase scaffolded.
Networking & data
Ktor clients with retries, tokens and error mapping. Room, DataStore, connectivity checks and offline-first sync primitives.
Design system
Material 3 theming — type, motion, shapes, dark mode, variants — plus a big catalog of reusable Compose components.
40+ sample screens
Dashboard, onboarding, chat, search, gallery, map, calendar, media player, forms, permissions, list/detail and more — plus 8 full feature flows.
Quality tooling
Detekt, ktlint, Jacoco coverage, dependency guard, BuildKonfig secrets and ProGuard rules — already part of the build.
All you might need, ready to go
Eight product flows, already built
Each pack is a clean-room reference implementation — three connected screens, a fake repository (no API key needed) and reusable components — ready to adapt to your product.
Focus sessions
A focus/break session state machine with a timer and time-block timeline — for productivity, study and habit apps.
Cart & checkout
Cart totals and a checkout lifecycle with integer minor-unit money — for commerce and food-ordering flows.
Resource scheduling
Overlap-aware multi-resource time planning — for clinics, salons, studios, coworking, field teams and equipment rental.
Adaptive reader
Compact-to-wide editorial browsing with a list-detail scaffold — for news, blogs and content apps.
Reviews & feedback
Eligible reviews, drafts and submission with rating and composer components — for marketplaces and service apps.
Live operations
Remote entity streams with freshness and telemetry — for delivery, logistics and live-tracking products.
Media workspace
Non-destructive media edits — zoom, pan, filter and compare — for photo and video tools.
Audio queue
Discovery, a persistent queue and a mini-player — for music, podcast and audio apps.
Bring your own agent.
It already knows the codebase.
The kit ships the context files agents actually read — architecture map, layer rules, naming, generation recipes. Point any harness at the repo and what it writes looks like the rest of the codebase, first try.
~/my-app · Claude Code
$ git clone kmpsk-app.git && cd kmpsk-app$ claude↳ reads CLAUDE.md · AGENTS.md↳ skills quickstart · add-screen · add-endpoint · release> Add a Workouts feature: list + detail screens,
/workouts endpoint, offline-first cache.✱ reads the map, matches the existing feature layout✱ writes ui/ · domain/ · data/ in the kit's shape✱ reuses the design system instead of new components✓ ./gradlew check — detekt, ktlint, tests green
/workouts endpoint, offline-first cache.✱ reads the map, matches the existing feature layout✱ writes ui/ · domain/ · data/ in the kit's shape✱ reuses the design system instead of new components✓ ./gradlew check — detekt, ktlint, tests green
Every harness, one set of rules
AGENTS.md, CLAUDE.md, Cursor rules and Copilot instructions all ship in the repo — same rules, so no agent gets a different story.
Skills written for this repo
Quick start, add a screen, add an endpoint, cut a release — call a skill by name instead of explaining the codebase again.
Code lands where it belongs
Every layer names the exact package to write into, and one command — detekt, ktlint, tests — proves the result. You review a diff, not a rewrite.
no plugin · no MCP wiring · no per-agent rewrite — clone and prompt
Twenty kits. Free for creators.
Make Kotlin, Android, IOS or KMP content? We'll hand you the Source kit free — any platform, no subscriber minimum. Tell us what you'd cover and drop a link to your channel or profile; if it's a fit, it's yours.
- Kotlin, Android or KMP content — any platform
- One honest review — good, bad, whatever's true
- One post about it, wherever you post
Pick your blade
Pay once. Both come with the complete source. After Stripe confirms payment, we email a sign-in link to the inbox you pay with.
LAUNCH PRICING — 23 OF THE FIRST 200 SPOTS LEFT- Complete scaffold source
- Full component catalog & 40+ screens
- The version current at purchase
- No later versions
- No support included
- Everything in Source
- Private GitHub access to later versions
- Lifetime support
- Priority on fixes & requests
- Discord community
Before you buy
straight answers · no fine printWhat exactly do I get?
The full Compose Multiplatform scaffold — architecture, auth, networking, offline data, the Material 3 design system, 40+ screens and the quality tooling. Source is the version for sale on the day you buy, sent as a download. Lifetime adds read-only access to the private GitHub repo, so later versions arrive when you pull.
What's the difference between Source and Lifetime?
Both include the complete kit and the same license. Source stays on the version you purchased. Lifetime keeps that access and adds later versions, support, priority on fixes, and Discord. After payment we email a sign-in link to the inbox you enter at checkout. Open your kit there to download, and Lifetime buyers can leave a GitHub username for the private repo.
Will it work with my backend?
Yes — the Ktor layer is backend-agnostic. Fake auth is included for demos, Supabase is wired in, Firebase is scaffolded, and your own API drops in behind the existing repository interfaces.
Is it built for AI coding tools?
A consistent codebase is the best context you can give Claude or Cursor. The layered architecture means generated screens land in the right place instead of inventing their own patterns.
One codebase for Android and iOS, really?
Yes. Compose Multiplatform renders both, and expect/actual wiring is already in place where the platforms genuinely differ — permissions, maps, storage.
Can I use it for client work?
Pay once, build unlimited apps — personal, client or commercial. The only thing you can't do is repackage the kit and sell it as a boilerplate.
Refunds?
Delivered source can't be returned, so no refunds — peek at the full toolbox and screen list above, and email me anything before you buy.
I already bought Source. Can I upgrade to Lifetime?
Yes. Sign in to your account and pay the $30 difference. Your account becomes Lifetime — later versions, private GitHub access, support, priority on fixes, and Discord. The upgrade is a new one-time sale, not a refund of Source.
Is the creator offer the same as the affiliate program?
No. Creators can receive a free Source kit for an honest review and one post. Affiliates use an invite-only tracking link and earn a privately agreed commission when someone they send buys. Joining one track does not automatically enroll you in the other, and the buyer always pays the same public price.
Why Kotlin Multiplatform
Kotlin Multiplatform lets a team choose its sharing boundary: share domain and data code, add Compose Multiplatform UI where it helps, and keep native implementations where the platforms genuinely differ.
| COMPARE | Kotlin Multiplatform✱ OUR PICK | Flutter | React Native |
|---|---|---|---|
| Code sharing | Kotlin MultiplatformChoose your level — logic only, or full UI with Compose | FlutterOne Flutter codebase for app logic and widget UI | React NativeShared React application logic and UI |
| UI approach | Kotlin MultiplatformCompose Multiplatform or native UI, feature by feature | FlutterFlutter widgets rendered by the Flutter engine | React NativeReact components backed by native platform views |
| Native integration | Kotlin MultiplatformDirect Kotlin/JVM and Kotlin/Native platform interop | FlutterPlugins, Dart FFI and platform channels where needed | React NativeNative modules and components through React Native APIs |
| Team ecosystem | Kotlin MultiplatformKotlin, Android and JVM experience | FlutterDart and Flutter experience | React NativeReact, JavaScript and TypeScript experience |
| Adoption path | Kotlin MultiplatformShare logic first, then expand into shared UI if useful | FlutterIntroduce a Flutter module or start a Flutter app | React NativeEmbed React Native surfaces or start a React Native app |
A concise decision aid—not a performance ranking. Read the detailed KMP vs Flutter and KMP vs React Native comparisons for context and official sources.