Angular
packages/ui-angular is KinetixUI's Angular implementation, packaged as
@kinetixui/angular. Its maturity is
Preview: it covers
80 of the 109
KinetixUI catalogue entries today — a foundation subset, not the full catalogue —
and grows incrementally.
- Package
@kinetixui/angular· preview package- Distribution
- On npm.
- Catalogue
- 80 of 109 catalogue entries. Browse components
- Not implemented
- 29 entries, each with its reason on platform coverage.
- Verification
- Catalogue verified to preview (the weakest component sets it). Components with test evidence: Interaction 80/80 · Accessibility 80/80 · RTL 47/80 · Large text 53/80. CI:
ci.yml. - Tokens
- The same generated CSS custom properties as React — one stylesheet, no Angular-specific token set How tokens reach Angular
- Start
- Install Angular
What differs from the React library#
- Written for Angular, not wrapped. Standalone components and directives with signal inputs and
ControlValueAccessor, so a KinetixUI control drops into a reactive form like any other Angular control. - Plain CSS, no Tailwind. The component stylesheet only spends the token custom properties, so an app does not adopt React's styling toolchain to get the design language.
- Overlays use the browser's top layer. Dialogs are a native
<dialog>and floating surfaces use thepopoverattribute, where React uses Radix portals. The behaviour contract (focus, Escape, return focus) is the same; the mechanism is Angular's and the DOM's own. - Some gaps are answered by Angular itself. Form is
ReactiveFormsModuleand Direction Provider is thedirattribute, shown on each component page as a native equivalent rather than counted as coverage. - The catalogue is still arriving, which is why the package is Preview. The unbuilt entries are listed by wave below, and nothing else on this page is promised for them.
A first adoption path#
- Install the package and load the token sheets before the component styles.
- Start where Angular already has a strong idiom: buttons, inputs, selects and switches in a reactive form, as in the example.
- Before planning a screen, check each component it needs in What's available; a planned one shows its wave on its own page.
- Read What Stable would require before you commit a product to the API: a Preview package can still change.
Install#
npm install @kinetixui/angular @kinetixui/tokens@kinetixui/tokens is a peer dependency, not a convenience: the components
spend generated CSS custom properties and never define them, so the token
contract has to be present for anything to render as designed. Load the token
sheets before the component styles. css carries colour, spacing and radius,
and css/extras carries the elevation and typography ramps, including the
focus ring every interactive component draws. Each has a /dark half that
redefines it under the .dark class:
@import "@kinetixui/tokens/css";
@import "@kinetixui/tokens/css/dark";
@import "@kinetixui/tokens/css/extras";
@import "@kinetixui/tokens/css/extras/dark";
@import "@kinetixui/angular/styles.css";Leave out css/extras and a keyboard user gets no focus ring, because the
component styles replace the browser outline with it. Leave out a /dark
sheet and toggling .dark changes nothing it would have redefined.
check:angular-package builds a clean Angular app from this exact block and
checks both in Chromium.
Angular 21 is the tested and supported range (@angular/core and
@angular/forms, ^21.0.0). Every export is standalone, so a template imports
the directives it uses and nothing else — there is no NgModule.
@kinetixui/angular versions independently of @kinetixui/ui,
@kinetixui/tokens and @kinetixui/cli, which release together. Its version
number will not match theirs, and that is deliberate — it is a
Preview package on its own release
cadence, so its API may still change.
What's available#
Every component below is a real export of @kinetixui/angular. This list is
read from components.manifest.json, and CI checks every entry against the
package's public API — it can't claim a component the package doesn't ship.
- Accordion
- Alert
- AlertDialog
- AppBar
- AspectRatio
- Avatar
- AvatarGroup
- Badge
- Banner
- Breadcrumb
- Button
- ButtonGroup
- Card
- Carousel
- Checkbox
- CircularProgress
- CodeBlock
- Collapsible
- Combobox
- Command
- ComparisonSlider
- ContextMenu
- DescriptionList
- Dialog
- Drawer
- DropdownMenu
- Empty
- Fab
- Field
- Footer
- HoverCard
- Image
- Inform
- Input
- InputGroup
- InputOtp
- Kbd
- Label
- List
- Marquee
- Menubar
- Metric
- Modal
- MultiSelect
- NativeSelect
- NavigationBar
- NavigationMenu
- NotificationCenter
- NumberInput
- PageHeader
- Pagination
- PasswordInput
- Popover
- Progress
- Quote
- RadioGroup
- Rating
- Resizable
- ScrollArea
- SegmentedControl
- Select
- Separator
- Sheet
- Sidebar
- Skeleton
- Slider
- Sonner
- Spinner
- Stepper
- Switch
- TabBar
- TableOfContents
- Tabs
- Tag
- Textarea
- Timeline
- Toggle
- ToggleGroup
- Tooltip
- Tour
For every platform side by side, see Platforms.
How it's built#
Angular shares KinetixUI's design and token contract with React, SwiftUI, Jetpack Compose and Flutter — not their source. These are not React components wrapped for Angular: each one is written as a standalone Angular component or directive.
Styling comes from the same pipeline as every other platform:
- DTCG token source — the JSON files in
tokens/. - Style Dictionary —
pnpm build:tokensgenerates every platform's output. - CSS custom properties — the web output, shipped as
@kinetixui/tokens/css. - Angular styles —
@kinetixui/angular/styles.css, plain CSS that only spends those custom properties (hsl(var(--action)),var(--spacing-3)).
There is no Angular-specific token set and no copied value, so a token change
reaches Angular exactly as it reaches React. Tailwind is not required: the
React package is a Tailwind consumer, but an Angular app can use KinetixUI
without adopting it. Dark mode is the same .dark class contract.
That is also why retheming is not Angular-specific. A theme from
Create is an override block over the same custom properties this
package spends, so its Web CSS target applies to an Angular app exactly as it
does to a React one — there is no Angular export target because there would be
nothing different in it. Import it after @kinetixui/tokens/css and after
@kinetixui/angular/styles.css.
Conventions#
- Standalone components and directives — import the ones a template uses. No NgModule.
OnPushchange detection throughout.- Signal APIs:
input(),model()for two-way values,output()for events. - Directives where the native element should stay the semantic element:
<button kxButton>,<input kxInput>,<label kxLabel>,<input kxInputGroupInput>,<a kxCard>/<button kxCard>for a card that is one action, and<nav kxBreadcrumb>,<nav kxPagination>,<header kxAppBar>,<footer kxFooter>for navigation landmarks, and<dialog kxDialogContent>(orkxAlertDialogContent,kxSheetContent,kxDrawerContent) for a modal surface, which is a real<dialog>. - Components where KinetixUI generates the markup:
<kx-card>,<kx-badge>,<kx-tabs>. ControlValueAccessoron form controls, so[(ngModel)],formControlandformControlNamework — includingdisabledset by the form model.- The variant and size names are the shared contract:
variant="Outline",size="lg"mean the same thing on every platform.
Example#
import { Component, signal } from '@angular/core';
import { FormsModule } from '@angular/forms';
import { KxButton, KxSwitch } from '@kinetixui/angular';
@Component({
selector: 'app-preferences',
imports: [FormsModule, KxButton, KxSwitch],
template: `
<kx-switch [(ngModel)]="notifications" aria-label="Email notifications" />
<button kxButton variant="Outline" (click)="save()">Save</button>
`,
})
export class PreferencesComponent {
notifications = signal(true);
save() {}
}This exact template is compiled and exercised by the package's own test suite, so it can't drift from the real API.
Put the five @import lines from Install at the top of the global stylesheet your angular.json
lists under styles (src/styles.css in a new app), then add PreferencesComponent to your root
component's imports, render <app-preferences /> in its template and run ng serve. You should see a switch that starts on and an outlined Save
button; clicking the switch, or pressing Space while it has focus, turns it off.
save() is empty, so Save does nothing yet.
The switch has no visible label in this example, only an accessible name: give it a visible label in a real
form. If the switch and Save look like default browser buttons, the component stylesheet is not
loaded; if a focused control shows no ring, css/extras is missing.
Once that works
- Apply your own colours without forking components.
- Browse the components that ship on Angular; each page shows its Angular code and how it is verified.
- Assemble a screen from blocks with their Angular code.
- Before you plan around a component, read What is left, by wave.
Accessibility#
- Native semantics first. Buttons, inputs and labels stay real
<button>,<input>and<label>elements, keeping their built-in focus, keyboard activation and form behaviour. - States map to real semantics:
disabledis the native attribute, checkboxes reportaria-checked(includingmixed), switches userole="switch", and the error state followsaria-invalid. - Tabs implement the APG keyboard pattern — arrow keys, Home and End, one tab stop — with arrow direction reversed in right-to-left documents.
- Composite fields are one control. A one-time code is one labelled
input with
autocomplete="one-time-code"under its cells; an input group's input is a real<input>; a rating is a radiogroup of real radios. - Navigation says where you are. Breadcrumb, pagination, tab bar and app
bar mark the current destination with
aria-current, and draw it with a shape (a bar, an outline, a pill or weight), not colour alone. Links stay links; a disabled link leaves the tab order and is not followed. Direction glyphs — the breadcrumb separator, Previous and Next, Back — mirror with the direction of the element they sit in. - Disclosure follows the APG. An accordion trigger is a button inside a
heading, with
aria-expandedandaria-controls; arrow keys move between triggers and never open one. Expanding and collapsing animate the content's height on the motion tokens, and under reduced motion land on the same state without animating. - Overlays use the browser's top layer, not a portal. Dialog, alert
dialog, modal, sheet and drawer are a native
<dialog>opened withshowModal(), so the page behind is inert; popover, tooltip and hover card use thepopoverattribute. Nothing moves in the DOM, so a surface inside an RTL region opens right-to-left. One stack decides what Escape and an outside press close: only the topmost surface, and a press inside a popover nested in a dialog is inside both. Focus moves in, Tab stays inside a modal surface, and on close focus returns to the trigger, or, when the trigger is gone, to the surface that contained it. The page stops scrolling while any modal surface is open, and starts again only when the last one closes. Floating surfaces take a logical side (start,end), flip and shift to stay on screen, follow their trigger through scrolling containers, and scroll inside themselves at 200% text. - Menus are one set of parts. Dropdown menu, context menu and menubar
share the same items (
kxMenuItem, checkbox and radio items, labels, groups, separators, shortcuts, submenus), withrole="menu",menuitem,menuitemcheckboxandmenuitemradio. Exactly one item is a Tab stop; the arrows stop at the ends of a menu and wrap across a menubar; Home, End and typeahead move too; disabled items are announced witharia-disabled, skipped and never run. Running an item closes the whole menu and returns focus to its trigger; Escape closes one level at a time. A submenu sits inside its parent menu in the DOM and opens toward the inline end, by the inline-end arrow (ArrowRight, or ArrowLeft in right-to-left). A context menu opens at the pointer, or from the ContextMenu key and Shift+F10 at the focused element. A keyboard highlight draws a focus ring a pointer highlight does not. - Listboxes keep focus where you type. Select, command and multi-select
share one listbox layer: the trigger, the search field or the input keeps
focus, and
aria-activedescendantnames the highlighted option, which is never a disabled one and never one a filter has hidden. Select is the select-only combobox (arole="combobox"button over arole="listbox");aria-selectedmarks the chosen option, apart from the highlight, and a closed select chooses by typeahead. Command filters locally — the query is never sent anywhere — and composes into a page, a popover or the command dialog. Multi-select holds its choices as chips whose remove buttons are named "Remove …", and keeps focus on a neighbour when one is removed. Combobox is a recipe — a popover holding a command — not a component.
These behaviours are covered by unit tests in jsdom and by
check:angular-browser, which runs the package as a live Angular application
in Chromium: axe over every usage example and state fixture in light and dark,
every interactive component driven by a real keyboard, direction in an LTR
page, an RTL page and each nested in the other, 200% text at desktop and phone
width, forced colours and reduced motion. That is evidence for those
behaviours, not an accessibility certification.
What is left, by wave#
Angular ships in waves rather than alphabetically, so each release is a usable
group rather than a scattering. The counts below are read from
components.manifest.json — every component with no Angular implementation
carries the wave it is in, so this table cannot drift from the plan.
| Wave | Remaining |
|---|---|
| Layout | 2 |
| Data display | 18 |
| Advanced interaction | 7 |
80 shipped. 2 more need no port at all — they are a native equivalent or a composition on Angular, and each says so on its own page.
Every component page already has an Angular tab. Where the port has not been written, the tab says so and names the wave; it does not show an invented example. Where Angular or the DOM already provides the concept — Direction Provider, Form — the tab shows that idiom, labelled Native equivalent, and it is not counted as Angular coverage.
Overlays share one architecture. Every overlay needs the same layer: stacking, focus, dismissal, scroll locking and positioning. Building that separately per component would mean getting it subtly different each time, so it was built once, with the dialog family (dialog, alert dialog, modal, sheet, drawer, popover, tooltip, hover card). The menus (dropdown menu, context menu, menubar) are built on it, with one shared collection core for keyboard navigation, and the listboxes (select, command, multi-select and the combobox recipe) on both. The notifications (toast, notification center, tour) are built on it too, and so are the navigation menu's panels and the sidebar's sheet on a phone.
What Stable would require#
Angular's maturity is Preview, and it stays there until all of the following are true. Adding more components does not by itself change the label, and nothing here is graded on a curve:
- Catalogue target reached — the waves above complete, or every remaining gap reclassified as a native equivalent or a composition with a reason.
- Overlays complete, on one shared architecture with focus trapping, scroll locking, dismissal and return-focus behaviour. The architecture, the dialog family, the menus, the listboxes and the notifications are in place.
- Forms complete — every control a
ControlValueAccessor, validation states wired toaria-invalid, and error messaging tested. - Documentation complete — every shipped component reachable from its own page with a compiled example.
Accessibility suite— an automated axe pass over the Angular components in a real browser: in place (check:angular-browser).Browser tests— real-browser keyboard, focus, direction, 200% text and motion coverage wherever@kinetixui/uihas it: in place for every component Angular implements. Both stay requirements: each new component has to arrive with the same evidence.- Distribution ready — the built package verified by
scripts/check-dist.mjs, including the stylesheet. Published to npm— done in 0.24.0. Availability was never the blocker on its own, and reaching it does not move the label: the rest of this list still has to be true.- API stability reviewed — a deliberate pass over the public surface, with any breaking change made before the label changes rather than after.
Current scope#
- Preview subset. Angular covers part of the catalogue, and full parity with the other platforms is not claimed. Because its catalogue is not yet complete, Angular is left out of the "on every platform" figure on Platforms rather than counted against it.
- Published, not settled. Being installable from npm says nothing about the API having stopped moving — the maturity label above is the thing to read, and it is independent of distribution.
- Browser evidence covers what exists. Every implemented Angular component is measured in Chromium; the planned ones are not, and nothing here claims parity with React beyond the behaviours those passes assert.