The founders avoid creating a rigid, atomized design system because the product is still iterating too quickly. They accept a "messy" component library and technical debt as a trade-off for speed. Formalizing a design system only makes sense once the product's UI has stabilized.
Related Insights
At Perplexity, the design system lives in the codebase, not Figma. Designers contribute directly to the frontend, creating a single source of truth that eliminates drift between design files and production code, forcing a highly practical and collaborative process.
The founders resolve the tension between speed and quality by being "obsessive." They move fast by iterating constantly, but also relentlessly go back and refine existing work. Speed is about the pace of iteration and a commitment to delight, not about shipping once and moving on.
Artist's CPO notes that while frameworks and processes can feel productive, the best product work is often messy and uncomfortable. It involves fighting with stakeholders and making bets on uncertain features rather than fixing known, smaller issues. This contrasts with the idealized view of smooth, process-driven development.
The idea that design systems stifle creativity stems from the high cost of re-coding components after a design change. In a world with a single source of truth, where design changes automatically update the code, this cost disappears, allowing systems to be radically changed without engineering overhead.
The team avoids traditional design reviews and handoffs, fostering a "process-allergic" culture where everyone obsessively builds and iterates directly on the product. This chaotic but passionate approach is key to their speed and quality, allowing them to move fast, make mistakes, and fix them quickly.
The current model of separate design files and codebases is inefficient. Future tools will enable designers to directly manipulate production code through a visual canvas, eliminating the handoff process and creating a single, shared source of truth for the entire team.
The co-founder, a designer, learned React to bypass the classic frustration of developers misinterpreting high-fidelity mockups. By designing directly in code, he maintains full control over the final UI, eliminates the handoff process, and saves significant time and back-and-forth.
While brand consistency is a benefit, the primary business impact of a well-built design system is operational efficiency. It drastically accelerates speed to market for new features and slashes onboarding time for new hires because the system's intelligence is effectively self-documenting.
Technical tools are secondary to building a successful design system. The primary barrier is a lack of shared vision. Success requires designers to think about engineering constraints and engineers to understand UX intent, creating an empathetic, symbiotic relationship that underpins the entire system.