Loading component…
In applications
- Capabilities
- Transactions & money and Workflow & approvals
- Business domains
- Enterprise administration
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 timelinenpm 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.
Ordered events down a rail — marker, connector, time, content — on one side or alternating sides of a centred rail, with optional spoken statuses.
Reduced motion: off · your browser setting
2 hours ago
Deployed to production
Yesterday
Opened PR #100
3 days ago
Project created
npx @kinetixui/cli add timelineimport { Timeline } from "@kinetixui/ui";Give items a status to turn the timeline into an order, refund, booking or delivery tracker. Without statuses the
timeline renders exactly as before.
Reduced motion: off · your browser setting
12 Mar, 09:14
Completed, Order placed
12 Mar, 09:15
Completed, Payment confirmed
13 Mar, 16:40
Current, Out for delivery
Pending, Delivered
<Timeline
items={[
{ title: "Refund requested", time: "12 Mar", status: "complete" },
{ title: "Approved", time: "13 Mar", status: "complete" },
{ title: "Sent to your bank", time: "14 Mar", status: "current", content: "Usually 3 to 5 working days." },
{ title: "Received", status: "pending" },
]}
/>| Status | Marker | Spoken before the title |
|---|---|---|
complete | filled, with a check | "Completed" |
current | ringed; the item has aria-current="step" | "Current" |
pending | hollow | "Pending" |
warning | warning triangle | "Needs attention" |
error | cross | "Failed" |
neutral | plain dot | nothing |
Each status has its own marker shape and its own spoken word, so status is never colour alone. Replace the words
with statusLabels (all items) or statusLabel (one item) to localise. An item can carry an action, such as a
"Track parcel" button, under its content.
alternating places items on both sides of a centred rail using logical sides: in RTL the rail and the alternating items
mirror, and text on the start side aligns towards the rail with text-end. Screen-reader output was checked in jsdom, not with VoiceOver or NVDA.
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 |
|---|---|---|
| itemsrequired | TimelineItem[] | |
| alternating | boolean | |
| statusLabels | Partial<Record<TimelineStatus, string>>Spoken words per status, for localisation. Unset entries keep their English default. | Spoken words per status, for localisation. Unset entries keep their English default. |