SaaS dashboards

Filter state, bulk actions, and unsaved edits are where SPA complexity accumulates fastest. SAUI simplifies each.

Try the live demo →

The client-side state model

SaaS dashboards are among the most complex SPA deployments. They accumulate:

  • Filter and sort state: managed client-side, sometimes synced to URL, sometimes not
  • Pagination state: page number, page size, cursor; held in multiple places
  • Bulk selection state: which rows are checked, across pages
  • Unsaved edits: inline editing that has not been submitted
  • Real-time updates: new records appearing while the user is on page 3 of results

Each of these is a synchronisation problem. Each requires its own state management solution. Together, they produce dashboards that are fragile, slow to build, and expensive to maintain.

What moves to the server under SAUI

  • Filter and sort state: encoded in the URL, applied server-side, returned as a projection
  • Pagination: server computes the page; cursor is opaque to the client
  • Bulk action validation: the gateway validates each selected record before applying the bulk action
  • Real-time updates: SSE pushes updated projections; the client swaps the target element

Filter state in the URL is bookmarkable, shareable, and survives reload without any client-side state management. The server applies the filters and returns the correct projection.

What stays on the client

  • Dropdown open/close state for filter controls
  • Row hover highlight
  • Column resize drag state (ephemeral, not persisted)

Unsaved inline edits are a genuine case for ephemeral client state: the user is mid-edit and the UI should not submit until they confirm. This is legitimate UI-only state. It has no business meaning until submission, at which point it becomes an action.

Bulk actions

Bulk actions are a common source of correctness problems in SPAs. The client holds a selection set. The user triggers a bulk delete. The client sends a list of IDs. Between selection and submission, some records may have changed state: already deleted by another user, locked by a process, no longer accessible.

Under SAUI, the gateway validates each record in the bulk action set before appending any events. If any record fails validation, the entire action is rejected with the current state. No partial application. The client receives a projection of what actually happened.

Next: Distributed systems