When Code Becomes a Design Material
1. From implementation output to a material for exploration
Code is expanding from a final delivery step into a material for testing and developing ideas.
- The one-way handoff of static mockups to engineers is changing.
- AI lets designers build and modify working prototypes, moving between the design canvas and code.
2. The danger of looking complete too early
Quick prototypes can align a team, but they can also make unresolved problems seem settled.
- In a Google Store internal-tool project, an early prototype helped establish the core workflow and product direction.
- When a complex approval process became necessary, discussions stayed on details such as interface copy rather than system structure.
- Returning to block models and information architecture maps helped the team examine the underlying logic.
3. Drawing is part of thinking
Sketches and wireframes both express ideas and help develop them.
- Drawing structures and flows encourages deeper examination of a problem.
- The article introduces embodied cognition: the idea that our hands participate in thinking.
- Even when AI generates screens quickly, user needs and the wider system still require examination.
4. Faster execution raises the value of design judgment
As implementation becomes easier, designers can focus more on product strategy and systemic problem-solving.
- What matters is what we learn through making and reviewing, rather than how much code we type ourselves.
- Prototypes can test behavior; simple diagrams can help examine structure.
XploreD Perspective
Working with code as a design material means making quickly while protecting time to think.
When to read
- When AI prototype reviews dwell on copy and visual details
- When implementation outpaces clarity about user flows and design decisions
Takeaways
- Review whether something works and whether it solves the right problem as separate questions
- Sketch uncertain structures as blocks and flows before polishing the screens further
