In production
Built with Aback UI
Aback UI is built for Aback Group products first. These are the interfaces whose repeated problems shaped the system, and the components they use today.
Aback Tools
Free tools that run in your browser.
A library of browser-based utilities for files, images, data, and text. The dense tool workbench and square-corner chrome shaped the foundation components.
Visit Aback ToolsAback Launch
Launch once. Get found for years.
A launch and discovery platform for products. Its forms, dialogs, data tables, and status surfaces shaped the overlay and feedback components.
Visit Aback LaunchComponents used
Aback Group
Software, tools, and technology products.
The umbrella site and product directory for the Aback ecosystem. Its header, command menu, section headings, and status badges shaped the application patterns.
Visit Aback GroupWhat the tag means
A component is tagged with a product when its pattern was reviewed against that product's interface and the same behavior is used there. The source in this repository was reimplemented for a general API. No product's routing, auth, billing, data model, or internal endpoints are included.
Components without a tag are new shared patterns. They are documented and tested, but this site does not claim production use for them.
Why it matters
A design system that is only used in its documentation site is a demo. These products put the components under real forms, dense data, long content, narrow viewports, and both themes. That is where the API and the edge cases came from.
The products remain independent. Aback UI does not import product code, and product teams can customize the copied source without waiting for a package release.