How much responsive design should designers actually hand off?
I've been thinking about how much detail designers really need to provide for responsive layouts.
Traditionally, we'd prepare desktop, tablet, and mobile designs, sometimes with specific breakpoints and detailed behavior for each screen size.
But now that developers are also using AI coding tools, I'm starting to question whether defining every breakpoint is still the best use of a designer's time.
I think designers should still define the important layout changes, content priorities, and interactions. But do we really need to specify every intermediate screen size?
Maybe it's more useful to define the rules and let developers handle the details during implementation.
I'm curious how other teams approach this.
How much responsive behavior do your designers specify before handing things off to development?
Replies
I try to hand off the rules that carry intent: content priority, where the layout should reflow, what can collapse, and how key components behave at narrow and wide sizes. Then I test a few awkward widths and long-content states instead of specifying every breakpoint. That gives implementation room without leaving navigation or hierarchy to guesswork.