Building UniUI from a University Dorm
The origins of UniUI: balancing academic demands with late-night prototyping on a battered laptop in a crowded dormitory room.
UniUI was born out of frustration. Every project I built for campus hackathons or client experiments required re-inventing the same baseline components—dialog modals, accessible select inputs, theme switchers, data tables.
01The Physical Reality
The room was cramped, shared with three roommates. Power cuts were frequent, requiring meticulous battery management and local-first development environments.
Working without consistent high-speed internet forced me to understand the underlying web platform deeply: - Native CSS variables over runtime stylesheet injection. - Zero-runtime styling tokens. - Strict keyboard navigation and focus management.
02First Principles of the Design System
When writing the core token system for UniUI, I established three immovable rules:
1. **Deterministic Theming**: High-contrast ratios validated automatically at compile-time. 2. **Semantic Primitives**: Never compromise HTML semantics for aesthetic shortcuts. 3. **Weightlessness**: Zero third-party runtime bloat.
See also the broader perspective in [[why i am documenting the next seven years]] and the subsequent retrospectives in [[what failure taught me about building products]].
Key Lessons Distilled
- 01.Constraints in hardware and environment enforce discipline in component architecture.
- 02.Premature abstractions break early; build three concrete components before extracting a generic primitive.
Resonance & Intellectual Pulse
Signal how this ideology, framework, or thesis resonated with you: