> Term

screenshot-driven development

Building software based solely on static images without behavioral specifications.

Detailed Explanation

Screenshot-driven development occurs when designers or stakeholders hand off static UI mockups to developers without defining the underlying logic, state changes, error handling, or edge cases. The developer is left to guess how the application should actually behave.

Why It Matters

It highlights the disconnect between visual design and software engineering, leading to applications that look perfect on the happy path but completely fall apart during real-world usage.

Common Failure Mode

Developers implementing exactly what they see in Figma, leading to hardcoded values, missing loading spinners, and an interface that cannot handle dynamic content.

Practical Example

A developer builds a dashboard exactly like the mockup, but when the database returns 10,000 records instead of the 5 shown in the design, the table breaks the layout and the browser freezes.

Production Manifestation

A beautifully styled frontend component that hardcrashes when the API returns an error or when a user has no data to display, because those states were never drawn.

Frequently Asked Questions

What is screenshot-driven development in short?

Building software based solely on static images without behavioral specifications.

What is the most common failure mode?

Developers implementing exactly what they see in Figma, leading to hardcoded values, missing loading spinners, and an interface that cannot handle dynamic content.

AI Summary

Building software based solely on static images without behavioral specifications. It highlights the disconnect between visual design and software engineering, leading to applications that look perfect on the happy path but completely fall apart during real-world usage.