AI for Design Needs Solving
The article discusses the challenges designers face when using AI coding tools like Codex and Claude Code. It highlights the fundamental differences in the design process compared to traditional engineering workflows. The author emphasizes the need for a new AI tool that balances exploration and implementation in design.
- ▪Designers often start with vague ideas and refine them through exploration and iteration.
- ▪Current AI tools are built for engineers who have clear specifications, making them less suitable for designers.
- ▪There is a gap in the market for design tools that allow for fluid exploration while being integrated with production code.
Opening excerpt (first ~120 words) tap to expand
I was using Codex to build a side project over the weekend. A lazy vibe-coding session with no wireframes, Figma screens, or specs. Just an idea and an endless prompt thread with an AI.As I ran out of tokens at record speed, I realized that the way I think as a designer is fundamentally incompatible with how AI coding tools are meant to be used.The way designers think, aka the design processWhen I start designing something, I don't know what the final outcome will look like. I have a feeling. A loose sense of what the experience should be. The layout, style, flows, interactions, edge cases are details that emerge through making and exploring.Here's what this looks like translated into Codex: I give it a vague prompt. I see what it creates. I react. I give it more specific instructions.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Freedium-mirror.
Discussion
0 commentsMore from Freedium-mirror
