Skip to content
KinetixUI

Supported platforms

KinetixUI is a shared design language — one token contract, one set of component contracts — with a native implementation per platform. It is not one framework's code ported everywhere: the SwiftUI, Compose and Flutter libraries are idiomatic to their platforms and are not wrappers around the web components.

This page states what exists and how it is checked, and it does not list anything that isn't implemented. Component counts and the gaps below are generated from components.manifest.json; the verification column is written by hand from each platform's CI workflow, which is named in the row so it can be checked.

  • Web · React

    React + Radix + Tailwind109 of 109 entries
    Package · distribution
    @kinetixui/uinpm, and source via npx @kinetixui/cli add
    Tokens
    CSS variables, Tailwind preset, typed TS object
    Dark mode
    Yes — `.dark` class
    RTL
    Logical properties plus `KinetixDirectionProvider` — partial: RTL test evidence for 38 of 109 catalogue entries; the rest are not audited
    Automated verification
    Unit, interaction and keyboard tests; axe in jsdom and in a real browser (light + dark); contrast, RTL, typography and grid guardrailsci.yml runsa11y-browser.yml runs
  • Web · Angularpreview

    Angular (standalone components, signal inputs)80 of 109 entries
    Package · distribution
    @kinetixui/angularnpm — versioned independently of @kinetixui/{tokens,ui,cli}
    Tokens
    The same generated CSS custom properties as React — one stylesheet, no Angular-specific token set
    Dark mode
    Yes — the same `.dark` class contract
    RTL
    The document's `dir` — partial: RTL test evidence for 47 of 80 catalogue entries; the rest are not audited
    Automated verification
    ng-packagr AOT build with strictTemplates (every template compiled), plus Vitest behaviour tests for roles, keyboard, disabled state, forms integration and RTL. No browser-level axe pass yetci.yml runs
  • iOS · SwiftUI

    SwiftUI (Swift package)90 of 109 entries
    Package · distribution
    KinetixUIFrom a repository checkout — not published to a registry yet
    Tokens
    Swift enums: colors (light + dark), type styles, spacing, radius, motion
    Dark mode
    Yes — follows the system color scheme
    RTL
    The `layoutDirection` environment value — no RTL test evidence yet
    Automated verification
    swift build and swift test on macOS: WCAG contrast of the light and dark colour sets, and the spacing / radius scale. No view-level interaction or accessibility tests yetnative-swiftui.yml runs
  • Android · Jetpack Compose

    Jetpack Compose90 of 109 entries
    Package · distribution
    com.kinetixui:ui-composeFrom a repository checkout — not published to a registry yet
    Tokens
    Kotlin objects and `dimens.xml`: colors (light + dark), type styles, spacing, radius, motion
    Dark mode
    Yes — follows `isSystemInDarkTheme()`
    RTL
    `LocalLayoutDirection` — limited evidence: RTL test evidence for 1 of 90 catalogue entries; the rest are not audited
    Automated verification
    gradle assembleDebug, lintDebug and Compose UI tests (Robolectric) for the core controls: interaction and accessibility semantics (counted in the evidence table). No screenshot tests yetnative-compose.yml runs
  • Flutter

    Flutter widgets90 of 109 entries
    Package · distribution
    kinetix_uiFrom a repository checkout — not published to a registry yet
    Tokens
    Dart classes: color scheme (light + dark), type styles, spacing, radius, motion
    Dark mode
    Yes — follows the platform brightness
    RTL
    `Directionality` — partial: RTL test evidence for 58 of 90 catalogue entries; the rest are not audited
    Automated verification
    flutter analyze, widget smoke tests (light and dark), interaction and accessibility-semantics tests for the core controls, and RTL and large-text tests across most of the catalogue (counted in the evidence table). No golden tests yetnative-flutter.yml runs

Availability, package maturity and verification are three different things#

They were once one word, and the word being printed was the one nothing backed up. Keep them apart:

  • Availability — is there an implementation here? A component either has one on a platform, or has guidance in its place (a native equivalent, a composition, or a planned port). Only an implementation counts as coverage.
  • Package maturity — is this platform's package a finished product? A product decision about the offering, not a measurement. @kinetixui/angular is Preview because its catalogue is knowingly incomplete; the others are Stable packages.
  • Verification — what automated tests actually prove about an implementation. Measured, from the test files, and never inferred from either of the other two. A file called Button.swift existing proves that the file exists.

@kinetixui/ui is a Stable, published package whose catalogue is verified to Beta. Both are true, and one word cannot say both.

React

Implementations
109 of 109 · catalogue complete
Package maturity
stable
Distribution
npm
Catalogue verification
beta

Evidence

Build verification
Verified
All 109 React catalogue entries have build evidence.
Interaction verification
Partial
49 of 109 React catalogue entries have interaction evidence.
Accessibility verification
Verified
All 109 React catalogue entries have accessibility evidence.
RTL verification
Partial
38 of 109 React catalogue entries have right-to-left evidence.
Large-text verification
Partial
39 of 109 React catalogue entries have large-text evidence.
Visual verification
Not yet verified
No React test records this yet.
Published
On npm
109 of 109 React catalogue entries are published to npm.

109 beta. The catalogue figure above is the weakest of these, not an average.

Angular

Implementations
80 of 109 · catalogue incomplete
Package maturity
preview
Distribution
npm
Catalogue verification
preview

Evidence

Build verification
Verified
All 80 Angular catalogue entries have build evidence.
Interaction verification
Verified
All 80 Angular catalogue entries have interaction evidence.
Accessibility verification
Verified
All 80 Angular catalogue entries have accessibility evidence.
RTL verification
Partial
47 of 80 Angular catalogue entries have right-to-left evidence.
Large-text verification
Partial
53 of 80 Angular catalogue entries have large-text evidence.
Visual verification
Not yet verified
No Angular test records this yet.
Published
On npm
80 of 80 Angular catalogue entries are published to npm.

80 preview. The catalogue figure above is the weakest of these, not an average.

SwiftUI

Implementations
90 of 109 · catalogue complete
Package maturity
stable
Distribution
Swift Package Manager — not published
Catalogue verification
experimental

Evidence

Build verification
Verified
All 90 SwiftUI catalogue entries have build evidence.
Interaction verification
Not yet verified
No SwiftUI test records this yet.
Accessibility verification
Not yet verified
No SwiftUI test records this yet.
RTL verification
Not yet verified
No SwiftUI test records this yet.
Large-text verification
Not yet verified
No SwiftUI test records this yet.
Visual verification
Not yet verified
No SwiftUI test records this yet.
Published
Source checkout only
SwiftUI is not published to Swift Package Manager yet; build it from a repository checkout.

90 experimental. The catalogue figure above is the weakest of these, not an average.

Jetpack Compose

Implementations
90 of 109 · catalogue complete
Package maturity
stable
Distribution
Maven Central — not published
Catalogue verification
experimental

Evidence

Build verification
Verified
All 90 Jetpack Compose catalogue entries have build evidence.
Interaction verification
Partial
9 of 90 Jetpack Compose catalogue entries have interaction evidence.
Accessibility verification
Partial
10 of 90 Jetpack Compose catalogue entries have accessibility evidence.
RTL verification
Limited evidence
Tests record it for 1 Jetpack Compose entry so far.
Large-text verification
Not yet verified
No Jetpack Compose test records this yet.
Visual verification
Not yet verified
No Jetpack Compose test records this yet.
Published
Source checkout only
Jetpack Compose is not published to Maven Central yet; build it from a repository checkout.

80 experimental · 10 beta. The catalogue figure above is the weakest of these, not an average.

Flutter

Implementations
90 of 109 · catalogue complete
Package maturity
stable
Distribution
pub.dev — not published
Catalogue verification
experimental

Evidence

Build verification
Verified
All 90 Flutter catalogue entries have build evidence.
Interaction verification
Limited evidence
Tests record it for 7 Flutter entries so far.
Accessibility verification
Limited evidence
Tests record it for 7 Flutter entries so far.
RTL verification
Partial
58 of 90 Flutter catalogue entries have right-to-left evidence.
Large-text verification
Partial
58 of 90 Flutter catalogue entries have large-text evidence.
Visual verification
Not yet verified
No Flutter test records this yet.
Published
Source checkout only
Flutter is not published to pub.dev yet; build it from a repository checkout.

83 experimental · 7 beta. The catalogue figure above is the weakest of these, not an average.

Evidence is shown as a fraction, never a tick, because a check mark beside a partially covered catalogue would be the most misleading thing on this page. Catalogue verification is the weakest component on that platform, not an average — a well-tested Button cannot compensate for an unverified Dialog, since you will apply the figure to whichever component you are about to use. Individual components often sit above their platform's floor; each component's page shows its own level.

How a verification level is earned#

Verification levels
LevelEvidence required
experimentalBuild
betaBuild · Accessibility
stableBuild · Accessibility · Interaction · RTL · Large text · Visual · Published

Every positive result traces to a source. The evidence is derived from the test files themselves — each marked passage declares what kind of verification it performs, and the components it covers are read from the KinetixUI symbols that passage calls — so a test that is deleted stops counting on the next run. The generated result is verification.json in the repository, and pnpm platform:matrix --verification=<component> prints the file and line range behind every tick. Each platform's workflow above links to its CI runs.

Nothing is verified Stable today: that rung additionally requires RTL, large-text and visual-regression evidence per component, and a published package.

Where the tests ran#

The levels above count what was tested. A second scale, used on use-case pages such as Commerce and for blocks, says where it ran:

  • Build verified: a required CI step compiles it.
  • Headless verified: tests CI runs assert both its interaction and its accessibility, but at least one ran only headless, in jsdom, Robolectric, flutter_test or XCTest.
  • Runtime verified: both were observed running in a real browser. No native component has simulator, emulator or device evidence yet, so none is Runtime verified.
Components by evidence tier
PlatformBuild verifiedHeadless verifiedRuntime verified
React602920
Angular02060
SwiftUI9000
Compose8370
Flutter8460

Reading the table#

  • Components counts the components each platform implements, out of 109 catalogue entries in the manifest. React is the reference implementation; the native ports mirror its API where it makes sense on the platform.
  • Automated verification is what the platform's CI actually runs, and the evidence counts above are the measure of it, read from the test files rather than written here. React has behavioural, keyboard and accessibility tests across the whole library. Every native library is compiled in CI on every change; beyond that, behavioural, accessibility-semantics, RTL and large-text tests cover a subset of components, and the subset differs by platform — read each platform's fractions rather than assuming one from another. No native port has screenshot tests, and a component with only build evidence is compile-checked and nothing more.
  • RTL — each native platform has its own layout-direction mechanism (LocalLayoutDirection, the layoutDirection environment value, Directionality). The RTL row in each platform's evidence counts the components with a test that proves mirrored behaviour; the rest are not audited yet. See RTL.
  • Maturity is recorded twice, on purpose. Each platform's package maturity is in the manifest and shown above — Angular is Preview. Each component is also marked (97 stable, 12 beta), per component rather than per platform: that label is about the component's API, not about how well any one platform's implementation of it is verified, which is what the evidence counts are for.

Not on every platform, on purpose#

Not every component belongs on every platform, and parity isn't a goal. These are the deliberate gaps on the catalogue-complete platforms, with what each component's page shows in place of a port and the repository's reason for it. Neither a native equivalent nor a composition is counted as platform coverage anywhere on this site — that is what keeps the numbers above meaning one thing.

Components not on every platform
ComponentMissing onWhat the page shows insteadWhy
address-fieldsSwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 2 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Roadmap target: Cross-platform Core. Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
amount-displaySwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 2 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Roadmap target: Cross-platform Core. Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
avatar-groupSwiftUI, Compose, FlutterA composition of other componentsstanding non-port — the React component re-wraps its children, which no native layout system does; compose an Avatar row directly. Its cap and +N marker would port to a data-driven native API, so this is a scope decision rather than an impossibility
comboboxSwiftUI, Compose, FlutterA composition of other componentsnot a component — a documented composition of Command (CommandInput/CommandList/CommandItem) in a Popover. There is no Combobox export on any platform; the recipe exists on React and Angular, the two platforms with Command.
country-selectSwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 2 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Roadmap target: Cross-platform Core. Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
date-range-inputSwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 2 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Roadmap target: Cross-platform Core. Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
direction-providerSwiftUI, Compose, FlutterThe platform's own idiomReact-only by design: the web needs a provider to thread direction through Radix, while SwiftUI (environment .layoutDirection), Compose (LocalLayoutDirection) and Flutter (Directionality) already carry layout direction in the framework itself. Nothing to port.
formSwiftUI, Compose, FlutterA composition of other componentsstanding non-port
guest-pickerSwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 2 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Roadmap target: Cross-platform Core. Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
kanban-boardSwiftUI, Compose, FlutterA composition of other componentsstanding non-port — built on @dnd-kit; each native platform would need its own from-scratch accessible multi-container drag-and-drop implementation (no equivalent dependency exists in this repo's native packages)
native-selectSwiftUI, Compose, FlutterA composition of other componentsstanding non-port — KinetixSelect already wraps each platform's own native picker
navigation-menuSwiftUI, Compose, FlutterA composition of other componentsstanding non-port
pass-cardSwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 1 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
phone-inputSwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 2 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Roadmap target: Cross-platform Core. Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
price-breakdownSwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 1 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
reference-codeSwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 1 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
result-stateSwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 1 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
time-slot-pickerSwiftUI, Compose, FlutterA composition of other componentsReact-first business foundation (business capability roadmap, Phase 2 — docs/BUSINESS-CAPABILITY-ROADMAP.md). Roadmap target: Cross-platform Core. Native ports are an open roadmap decision, not a standing non-port: until one is made, each native tab shows the composition of existing Kinetix primitives that delivers the same outcome.
tourSwiftUI, Compose, FlutterA composition of other componentsstanding non-port — targeting an arbitrary already-rendered element needs a CSS-selector-equivalent live-tree query, which no native platform has

Angular's gaps are a different kind and are listed separately, by delivery wave, on Angular: its catalogue is still rolling out, so a gap there is unbuilt work rather than a decision.

Not supported#

These are platforms people reasonably ask about. The repository has no implementation of any of them, so none is given a status:

Not supported
PlatformStatus
Wear OSNot supported. No implementation yet. Approved as a separate track that derives from Core tokens rather than shrinking the phone components (design spec: WEARABLES.md).
watchOSNot supported. No implementation yet. Approved on the same track, following watchOS conventions rather than Wear OS's (design spec: WEARABLES.md).
Plain HTML / CSS packageNot supported. There is no kx-* class API. On the web, use React or the registry (npx @kinetixui/cli add).

Further reading: Cross-platform design systems: architecture, parity and trade-offs; How to verify design system parity across web, iOS and Android.

Where to go next#

  • Foundations — the grid, radius, elevation and motion behind every platform.
  • Angular — the preview web implementation, its delivery waves and what Stable would require.
  • SwiftUI, Jetpack Compose, Flutter — installation and usage for each native library.
  • Tokens and Theming — the color and type contract.
  • Explore components — each component page shows what it is on every platform.
  • Accessibility — the React library's keyboard, focus and contrast evidence.
  • Contributing — the platform rule for new components, and what every platform tab has to show.