Loading component…
Loading component…
What automated tests prove about each implementation — separate from whether the package itself is a finished product. Derived from the test files; how the levels are earned.
React
React setupPackage maturity: stable · Implementation verification: Beta
Angular
Angular setup · previewPackage maturity: preview · Implementation verification: Preview
SwiftUI
SwiftUI setupPackage maturity: stable · Implementation verification: Experimental
Jetpack Compose
Jetpack Compose setupPackage maturity: stable · Implementation verification: Experimental
Flutter
Flutter setupPackage maturity: stable · Implementation verification: Experimental
This platform’s whole catalogue is verified to React beta, Angular preview, SwiftUI experimental, Jetpack Compose experimental, Flutter experimental. The catalogue figure is the weakest component on that platform, not an average.
npx @kinetixui/cli add ratingnpm i @kinetixui/ui @kinetixui/tokens@kinetixui/ui on npm@kinetixui/tokens on npmThe CLI copies React source. Usage imports from @kinetixui/ui require the npm package; for copied source, use your configured local import instead.
npm i @kinetixui/angular @kinetixui/tokens@kinetixui/angular on npm@kinetixui/tokens on npmSource only, not on Swift Package Manager yet: use a repository checkout pinned to a commit.
Source only, not on Maven Central yet: use a repository checkout pinned to a commit.
Source only, not on pub.dev yet: use a repository checkout pinned to a commit.
A star rating input / display.
Reduced motion: off · your browser setting
npx @kinetixui/cli add ratingimport { Rating } from "@kinetixui/ui";
<Rating value={stars} onChange={setStars} aria-label="Rate this article" />
<Rating value={4} readOnly />A rating is one choice out of five, so it is a radio group of real radios — "3 stars, radio, checked, 3 of 5". That makes the keyboard behaviour the browser's rather than ours: one tab stop (the chosen star, or the first when nothing is chosen yet), and the arrow keys move and choose, mirrored in a right-to-left page. Home and End choose the lowest and highest. Clicking a star chooses it; hovering previews the fill without changing the value.
Give the group a name with aria-label or aria-labelledby — it is "Rating" if you give neither,
which is rarely what you want on a page with more than one.
readOnly is a rating that is shown rather than given: role="img" named "Rated 3 out of 5", the
stars hidden from assistive technology, and no tab stop.
This is the same contract Angular's kx-rating states and asserts. The arrow-key half of it is the
browser's, so no test here proves it on a real engine: the unit tests exercise it through
user-event's emulation of radio-group navigation, and the structural half —
a component claiming a radiogroup must contain real radios and must not describe them with
aria-pressed, which is a toggle button's state and cannot say which one of a group is chosen — is
held by check:role-coherence. An automated accessibility scan passes that contradiction, because
no single element in it is wrong.
SwiftUI, Compose and Flutter render the stars as tappable images with no control role and no selected state, so the announcement above is React's and Angular's only; see the cross-platform note in the pull request that introduced this.
Styled entirely from the KinetixUI token contract — bg-action,
text-muted-foreground, border-input, ring-ring. Works in light and dark
with no extra config. Keyboard and ARIA behaviour is inherited from Radix where the
component is built on a primitive; the hand-built widgets (DataGrid, TreeView,
ColorPicker, MultiSelect, Tour, KanbanBoard) have their own documented interaction
models — see Accessibility.
The props of @kinetixui/ui, generated from its TypeScript. Props inherited from the underlying DOM element (className, id, event handlers) are accepted too and are not listed.
This table is React-specific. The SwiftUI, Jetpack Compose, Flutter and Angular implementations share the design contract — the same variants, sizes, states and tokens — but each exposes its own idiomatic interface. Their real usage is in the platform tabs on the example above, not here.
| Prop | Type | Notes |
|---|---|---|
| value | number | |
| defaultValue | number | |
| max | number | |
| readOnly | boolean | |
| onChange | ((value: number) => void) | |
| size | "sm" | "md" | "lg" | null |