Mobile Development · head to head
Kotlin Multiplatform vs Preact

Kotlin Multiplatform
Mobile Development
JetBrains-funded technology for sharing Kotlin business logic across iOS, Android, web, desktop and server
- From
- Free
- Free plan
- Yes

Preact
Web Development
3kB alternative to React with the same modern API
- From
- Free
- Free plan
- Yes
The short version
- Both are free.
- Only Kotlin Multiplatform lists shared Kotlin logic; only Preact lists 3kB runtime.
- Where Preact falls short: compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose.
- Prices and features on this page were last checked on 20 November 2026.
How do Kotlin Multiplatform and Preact differ?
Kotlin Multiplatform and Preact differ on platforms and category (Mobile Development against Web Development). Only the attributes on which Kotlin Multiplatform and Preact actually diverge.
| Attribute | Kotlin Multiplatform | Preact |
|---|---|---|
| Platforms | iOS, Android, Windows, macOS, Linux, Web | Web |
| Category | Mobile Development | Web Development |
Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes).
Which features does each one have?
They share no listed features; 6 appear only for Kotlin Multiplatform and 4 only for Preact. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Kotlin Multiplatform
- Shared Kotlin logic
- Native UI retained
- Compose Multiplatform (optional)
- IDE tooling
- Gradle-based builds
- Incremental adoption
Only in Preact
- 3kB runtime
- preact/compat
- Same modern API
- Fast rendering
What is each one used for?
Preact is most often brought in for embedded widgets that load inside someone else’s page and must stay small. The jobs each tool is most often brought in to do.
Kotlin Multiplatform
- A company with existing separate native iOS and Android codebases wanting to stop duplicating business logic and networking codenot Preact
- A team that wants shared logic but is not willing to compromise on fully native UI per platformnot Preact
- An organisation already using Kotlin on the backend that wants to reuse the same models and validation on mobile clientsnot Preact
- A team evaluating Compose Multiplatform for UI sharing but wanting the option to fall back to native UI per screennot Preact
Preact
- Embedded widgets that load inside someone else’s page and must stay smallnot Kotlin Multiplatform
- Marketing and content sites where JavaScript payload affects Core Web Vitalsnot Kotlin Multiplatform
- Applications targeting low-bandwidth or low-powered devicesnot Kotlin Multiplatform
Where do Kotlin Multiplatform and Preact fall short?
Preact's most cited limit: behavioural differences from React exist in edge cases, particularly around event handling. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Kotlin Multiplatform
- It shares logic, not UI, by default, so a team expecting a Flutter-style single UI codebase has to also adopt Compose Multiplatform, which is newer and less proven on iOS than on Android
- iOS interop relies on Kotlin/Native compiling to a framework consumed from Swift, and debugging across that boundary is more friction than debugging pure Swift or pure Kotlin
- Because logic-sharing is the whole premise, teams still need genuine iOS and Android UI expertise on staff; it does not reduce the native skills bar the way a full cross-platform UI framework aims to
- Build times and tooling maturity for multiplatform Gradle projects lag behind single-platform Kotlin or Swift projects, and multiplatform-specific build errors are less well documented
- JetBrains funds it as part of the broader Kotlin investment, so its roadmap priority competes internally with IntelliJ, Android Studio and other JetBrains commitments rather than having dedicated headcount the way Flutter has at Google
Preact
- Compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
- Behavioural differences from React exist in edge cases, particularly around event handling
- A much smaller community, so unusual problems have fewer existing answers than React
How much do Kotlin Multiplatform and Preact cost?
Kotlin Multiplatform is free to use; Preact is free to use. Plan by plan below, from each vendor's own pricing page.
Kotlin Multiplatform
Free- Kotlin MultiplatformFree
- Apache 2.0 licensed, unlimited apps
- IDE tooling in the free Android Studio and free-tier IntelliJ IDEA Community
- No paid Kotlin Multiplatform edition exists
Preact
Free- PreactFree
- Full library
- Commercial use permitted
- No usage limits
Which should you pick?
Choose Kotlin Multiplatform if
- You need shared kotlin logic.
- You want to start without paying.
- You work on iOS, Android, Windows, macOS, Linux, Web.
- You also want native ui retained.
Choose Preact if
- You need 3kb runtime.
- You want to start without paying.
- You also want preact/compat.
Questions people ask
- Is Kotlin Multiplatform or Preact better?
- Neither clearly leads. Kotlin Multiplatform starts at Free and Preact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Kotlin Multiplatform or Preact?
- Kotlin Multiplatform starts at Free and Preact at Free.
- Does Kotlin Multiplatform or Preact run on more platforms?
- Kotlin Multiplatform runs on iOS, Android, Windows, macOS, Linux, Web. Preact runs on Web.
- Can I use Kotlin Multiplatform for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Kotlin Multiplatform best used for?
- Kotlin Multiplatform is most often used for a company with existing separate native ios and android codebases wanting to stop duplicating business logic and networking code, a team that wants shared logic but is not willing to compromise on fully native ui per platform, an organisation already using kotlin on the backend that wants to reuse the same models and validation on mobile clients, a team evaluating compose multiplatform for ui sharing but wanting the option to fall back to native ui per screen. Of those, a company with existing separate native ios and android codebases wanting to stop duplicating business logic and networking code and a team that wants shared logic but is not willing to compromise on fully native ui per platform are not what Preact is typically brought in for.
- What can Kotlin Multiplatform do that Preact cannot?
- Kotlin Multiplatform covers Shared Kotlin logic, Native UI retained, Compose Multiplatform (optional), IDE tooling. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.
Answered from the vendors’ own pages
Kotlin Multiplatform: Does Kotlin Multiplatform replace my native UI code?
Not by default. It shares business logic and data layers; UI stays native per platform unless you separately adopt Compose Multiplatform.
Preact: Is Preact free?
Yes, open source under the MIT licence.
Kotlin Multiplatform: Is there a paid version?
No. It is Apache 2.0 licensed and free, funded by JetBrains as part of the Kotlin project.
Preact: Can I use React libraries with Preact?
Most, through the preact/compat layer. Compatibility is good but not complete, so libraries relying on React internals can break.
Kotlin Multiplatform: Do I need Compose Multiplatform to use it?
No, they are separate. You can share only logic and keep fully native UI on each platform indefinitely.
Preact: Why choose Preact over React?
Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.
Related pages
More on Kotlin Multiplatform
Other head to heads
- Kotlin Multiplatform vs Jetpack Compose
- Kotlin Multiplatform vs .NET MAUI
- Kotlin Multiplatform vs Ionic
- Kotlin Multiplatform vs React Native
- Kotlin Multiplatform vs NativeScript
- Kotlin Multiplatform vs Swift
- Kotlin Multiplatform vs Emerge Tools
- Kotlin Multiplatform vs Sencha
- Kotlin Multiplatform vs AWS Amplify
- Kotlin Multiplatform vs RevenueCat
- Kotlin Multiplatform vs Superwall
- Kotlin Multiplatform vs Adjust
- Kotlin Multiplatform vs AppsFlyer
- Kotlin Multiplatform vs BuildFire
- Kotlin Multiplatform vs Android Studio
- Kotlin Multiplatform vs Capacitor
- Kotlin Multiplatform vs Xcode
- Kotlin Multiplatform vs Flutter
- Kotlin Multiplatform vs SolidJS
- Kotlin Multiplatform vs Lit
- Kotlin Multiplatform vs React
- Kotlin Multiplatform vs Vue.js
- Kotlin Multiplatform vs Qwik
- Kotlin Multiplatform vs Stencil
- Kotlin Multiplatform vs Svelte
- Kotlin Multiplatform vs Alpine.js
- Kotlin Multiplatform vs MUI
- Kotlin Multiplatform vs Bootstrap
- Kotlin Multiplatform vs esbuild
- Kotlin Multiplatform vs Stimulus
- Kotlin Multiplatform vs NestJS
- Kotlin Multiplatform vs shadcn/ui
- Kotlin Multiplatform vs Tailwind CSS
- Kotlin Multiplatform vs Wix
- Kotlin Multiplatform vs Netlify
- Kotlin Multiplatform vs Ruby on Rails
- Preact vs Jetpack Compose
- Preact vs .NET MAUI
- Preact vs Ionic
- Preact vs React Native
- Preact vs NativeScript
- Preact vs Swift
- Preact vs Emerge Tools
- Preact vs Sencha
- Preact vs AWS Amplify
- Preact vs RevenueCat
- Preact vs Superwall
- Preact vs Adjust
- Preact vs AppsFlyer
- Preact vs BuildFire
- Preact vs Android Studio
- Preact vs Capacitor
- Preact vs Xcode
- Preact vs Flutter
- Preact vs SolidJS
- Preact vs Lit
- Preact vs React
- Preact vs Vue.js
- Preact vs Qwik
- Preact vs Stencil
- Preact vs Svelte
- Preact vs Alpine.js
- Preact vs MUI
- Preact vs Bootstrap
- Preact vs esbuild
- Preact vs Stimulus
- Preact vs NestJS
- Preact vs shadcn/ui
- Preact vs Tailwind CSS
- Preact vs Wix
- Preact vs Netlify
- Preact vs Ruby on Rails
