Interface over frameworks
A placeholder article for the new blog collection and route structure.
- Published
- Mar 7, 2026
- Reading
- 1 min
- Tags
- design, systems
On this page
Framework choice matters, but interface quality matters more.
People remember the surface they touch
Users rarely care how many abstractions are underneath a page. They notice whether the typography is calm, whether the navigation feels intentional, and whether the page stays stable while loading.
Tooling should protect the interface
A good stack is one that lets the site stay simple. If the framework keeps pushing the page toward heavier client logic, that is a cost, not a feature.
Keep the architecture behind the curtain
The real win is not showing off the stack. It is letting structure, spacing, and interaction feel inevitable.
Written by
Bojin Li
Bojin Li writes about software, systems, design, and the internet from a static-first, content-first perspective.
Comments
A place for follow-up discussion
Discussion loads after the page. It should feel like part of the document, not a widget pasted under it. Interface over frameworks.
Leave a note
Progressive enhancement