A New Way to Render Pages
Most business applications are built around static templates. You have a customer page. It has a fixed layout. Changing that layout means changing the template — which means a developer, a deployment, and time.
We replaced that model with something fundamentally different.
Components All the Way Down
In Swifty, every page is assembled from components. A list component. A form component. A detail panel. An action bar. A related-records section. Each component is a reusable, self-contained unit that knows how to render its type of content.
Pages aren't templates — they're compositions of these components, arranged according to your configuration.
What Changes
The practical implications of this shift are significant.
Flexibility. Adding a section to a page means adding a component to the configuration — not writing HTML. Rearranging sections means reordering components. The layout is as flexible as the configuration allows, which is: completely.
Reuse. The same component that renders a list of invoices on a customer detail page is the same component that renders a standalone invoice list. Define the behavior once, use it anywhere.
Consistency. Components enforce consistent behavior across every instance. Every list has search. Every form has validation. Every detail page has the same navigation patterns. Your application feels coherent because it's built from the same pieces.
Composability in Practice
Consider a customer detail page. It might be composed of:
- A summary panel showing the customer's key fields
- An edit form for updating the record
- A list of related orders
- A list of related invoices
- An action bar with workflow buttons
Each of those is a component. Each can be configured independently. Each can be reordered or removed without affecting the others.
That's composability. It means the page is as specific or as generic as you need it to be — and changing it later costs almost nothing.
The Result
Pages built this way are faster to create, easier to change, and more consistent than pages built from static templates. The upfront work of building a composable system pays off every time something needs to change.
In business software, something always needs to change.