Designers debate the necessity of writing production code

The case for code. Proponents argue that designers must move past visual mockups to understand the grain of the web, treating code as a primary material (UX Collective). Designers who write code gain immediate connection to their creations, allowing them to identify layout failures that static screens mask (UX Collective). At companies like Clay, growth teams now build functional web assets without dedicated engineering support, shipping custom landing pages in two hours instead of days (GTM Strategist). This hands-on approach allows teams to act on sales feedback instantly and experiment with interactive lead magnets that drive higher conversion rates.

The case for abstraction. Critics maintain that production-first habits erode the underlying design thinking required for high-quality interaction. Alan Cooper argues that coding is not a necessary skill for top-tier interaction designers, while others fear that focusing on implementation details distracts from the core user experience. Instead of writing code, teams can use generative protocols like A2UI, which allow agents to render interactive screens using native components without requiring the designer to manage the underlying markup (TLDR AI). This separation allows designers to focus on interface logic while relying on automated SDKs to ensure platform fidelity (React Status).

The tension centers on whether code serves as a temporary test bench for understanding model behavior or as a permanent requirement for the design role. While some designers use sampling code to build evaluation sets that identify model failures, others prefer visual editors and headless libraries that abstract away the browser's technical complexities.