The friction points people named
- Vocabulary. One reply found their team using the word design for four different things, with more than one reading valid each time.
- Pixel-perfect expectations against pressure to ship, named as a two-way problem: designers holding out for exactness, developers quietly cutting corners.
- Developers changing a design without raising it, because they judged their version better.
- Elaborate custom interface work where an existing standard component would have done, and frustration when engineers pushed back.
- Designs that look simple but are expensive to build, from designers without a feel for what the framework makes hard.
- Platform conventions. A mobile developer described designers who worked exclusively on iOS and had no sense of Android norms, leaving the developer to translate every screen.
- Round trips on trivial changes, with interface copy singled out — a wording change needing a developer every time.
- Unsettled authority: whether the design is the decision or the suggestion.
What people said actually worked
- Pair on the work rather than handing it over, so each side learns what matters in the design and what is costly to build.
- Ask engineers for design input directly, in sketching sessions and design reviews, rather than only at the end.
- Define the shared terms once and hold to them.
- Agree who the work is for. One reply put it as deciding you serve the customer, and noticing that some details genuinely do not matter and are easy to argue about anyway.
Where the structure is the cause
One reply put the blame on team shape rather than on either discipline: trouble concentrates where a company expects frequent incremental delivery from engineers while design sits outside the team and hands over finished mockups produced in isolation. The mockups are not wrong; they simply were not made for delivery in increments.
The dissent
Two people said they do not recognise the problem. A user experience designer of fifteen years described enjoying the work with engineers and wondered whether the designers in question were junior. A developer said they had rarely butted heads with designers and put it down to mutual respect and a casual interest in each other's craft. Neither denied the friction exists elsewhere, and both located the cause in the people rather than the disciplines.
One caution about the thread
- Most replies describe product teams inside companies. A freelancer doing both jobs has none of this structure and none of these remedies.
- It is a 2022 thread, and the tools named in it have moved on. The friction described is about process rather than tooling.