15 Components at Launch
A component library is only useful if it covers what you actually need to build. Launch a system with three components and builders immediately hit the walls. Launch with the right ones and the most common page patterns click into place quickly.
At launch, the Swifty visual builder ships with 15 components.
The Lineup
Data components handle the core business of displaying and editing records:
- Data Table — sortable, filterable, paginated list of records with configurable columns
- Detail Form — read-and-edit view for a single record, with field-level control
- Detail Panel — read-only summary card for a record, suitable for sidebars and headers
- Related Records — list of records linked to the current record via a relationship
Metric components surface key numbers:
- Metric Card — a single number with a label, trend indicator, and optional comparison value
- Metric Row — a horizontal strip of metric cards for dashboard overviews
Layout components structure the page itself:
- Panel — a card container with optional header, footer, and border styling
- Columns — flexible multi-column layout with configurable widths
- Tabs — tabbed content sections to reduce visual complexity on dense pages
Navigation components orient users:
- Page Header — title, breadcrumbs, and primary action buttons
- Sidebar Nav — collapsible navigation list for section-level navigation within an app
- Breadcrumbs — path indicator for hierarchical navigation
Interaction components trigger actions:
- Button — primary, secondary, and destructive variants with icon support
- Badge — status indicator with color-coded variants
- Dropdown Menu — grouped action menu for secondary actions
Composable by Design
Components are designed to work together. A detail page typically combines a Page Header, a Panel, a Detail Form, and a Related Records component — all arranged using Columns to divide the layout into a main area and a sidebar.
The combinations are not prescribed. Any component can appear anywhere the layout supports it. The builder enforces no opinions about which components belong together, so your pages can reflect your actual requirements.
More Coming
15 components is a strong starting set, not a final number. The library grows based on the patterns that emerge from real usage. New components appear in the builder automatically when they're added to the platform — no updates required on your end.
The goal is a library deep enough that building a working business application requires no custom development — just configuration, composition, and data.