The Illusion of Progress: AI and Design Regression

The narrative around AI in design and development often centers on acceleration and efficiency. Yet, for many in the trenches, the reality is more complex. Olena Ivlieva, a UI Engineer at Kavita Systems, found herself questioning the direction of AI's integration, observing a peculiar trend: AI seemed to be making her see more bad design, not less. This sentiment, captured in her own words, feels like "inventing a time machine and starting to move backwards." The ease with which AI tools can generate interfaces can mask underlying design and implementation flaws, especially for founders with limited technical backgrounds who might incorrectly assume AI can autonomously bridge the gap between concept and functional product.

Ivlieva's professional journey, from UX/UI Designer to UI Engineer to Front-End Developer, provides a unique vantage point. She remembers a time before ubiquitous tools like Figma, where the design-to-code handoff was a more human-centric process, relying on direct communication and agreement between designers and developers. Today, with AI tools capable of generating code from design mockups, there's a risk of automating away the critical thinking and nuanced collaboration that lead to truly effective user experiences.

Developer comparing AI-generated UI code with manual implementation for a component

The Figma ↔ Code Experiment

To investigate this phenomenon, Ivlieva embarked on a practical experiment: translating designs between Figma and code, leveraging AI tools. The goal was to understand where the AI excelled, where it faltered, and what this revealed about the current state of automated design implementation. The experiment wasn't about proving AI's inadequacy, but about understanding its limitations and the potential pitfalls it introduces into the design and development lifecycle.

The process involved taking a design, often created in a tool like Figma, and using AI to generate the corresponding code. Conversely, she also explored generating designs from code components. The core tension arose when the AI-generated output, while syntactically correct, lacked the polish, accessibility, or semantic correctness expected in professional development. It highlighted a critical disconnect: AI could replicate visual appearance but struggled with the underlying principles of good design and robust engineering.

What AI Misses: The Nuances of Good Design

The experiment revealed several key areas where AI-generated designs and code fell short. Firstly, accessibility is often an afterthought. While an AI might generate a visually appealing button, it may not correctly implement ARIA attributes, ensure sufficient color contrast, or consider keyboard navigation. This oversight is particularly concerning, as accessibility is not merely a compliance issue but a fundamental aspect of good design that ensures products are usable by everyone.

Secondly, semantic correctness in HTML and CSS is frequently compromised. AI tools may opt for generic `div` elements where more specific semantic tags like `