Blog/

Systems under the UI

Interfaces are only as good as the services, data, and constraints underneath them.

  • systems
  • engineering

Pretty screens fail when the system underneath is muddy. Latency, unclear ownership, and half-modeled data all show up as UI friction — even when the design looks finished.

I treat the interface and the system as one problem:

  • If a status is hard to show, the domain model is incomplete.
  • If a form needs five confirmation dialogs, the workflow is wrong.
  • If loading states feel endless, the service boundaries are wrong.

Design without systems work is decoration. Systems work without design is unfinished.