Skip to content
mh studio Book a free call
← All articles

Design QA

Design isn't done at handoff. How I QA a build before users see it.

The gap between the file and the build is where products lose quality. My checklist, my bug format and why severity matters.

Mohamed Hassan, Lead Product Designer
· 4 min read

There is a moment in every project where the design file stops being the truth. The screen is built, it looks roughly right in a screenshot, and everyone wants to move on. That moment is where most of a product's quality is lost. Not in big mistakes. In a hundred small ones: a tap target that shrank, a balance that jitters because the numbers are not tabular, an error state nobody built because it lived on a separate frame.

I treat design QA as part of design, not a favour to engineering. Every built screen gets checked against the design before it ships, and I test the builds developers send, whether that is a staging link, an APK or a TestFlight build, on real devices. Here is what that pass looks like.

Start with the job, not the pixels

The first pass is not a pixel comparison. I use the build to do the main job the product exists for, end to end, the way its users would. In Corridor, a concept money app, that means: get paid, check what will land, send money home. In Crewday, a concept rota and payroll product, it means: publish next week's rota as the manager, then clock in as a barista. If the main path has a dead end, a confusing label or a missing confirmation, nothing else on the list matters yet.

Then break it on purpose

Happy paths are what the design file shows. Real products live in the other states. My standard list:

  • Empty, loading, error and partial states for every list and dashboard.
  • Very long names, very large amounts, zero amounts and negative balances.
  • No network, a slow network and a request that fails halfway.
  • Double taps on every primary button. Anything that moves money or sends a message must never fire twice.
  • Back button and swipe back in the middle of a flow.
  • Rotation, the keyboard open, and system text size turned up.

For fitness and wellness products I add one more: use it the way people actually do, with one hand, mid-workout, at arm's length. A rest timer that reads fine at a desk can be useless between sets.

Check the details that make it feel finished

This is the part people imagine when they hear "design QA", and it still matters:

  • Spacing and type against the tokens, not against my eye. If the system says 16 and the build says 15, that is a token problem, not a nitpick.
  • Tabular figures wherever numbers change, so balances and timers stay still.
  • Touch targets of at least 44 by 44 points, especially icon buttons.
  • Text contrast of 4.5:1 or better, including placeholders and disabled states.
  • Focus order and a visible focus ring for keyboard users on the web.
  • Motion against its spec: duration, easing and the reduced-motion fallback.
  • The widths designers forget: 320 and 390 on phones, tablets, and very wide desktops. Horizontal scroll on a phone is a bug every time.

Write bugs engineers want to read

A QA pass is only as useful as the bug reports it produces. Mine follow a fixed format: where it is, steps to reproduce, what I expected, what happened, a screenshot or short recording, the device and build number, and a severity.

Severity is the part designers skip, and it is the part that earns trust with engineers. I use three levels. Blocker: the person cannot finish the job, or something unsafe can happen, like a payment sent twice. Major: the job gets done but it is broken or confusing for a group of people, like a missing screen reader label on the Send button. Polish: it is wrong, but nobody is hurt, like two pixels of spacing. Honest severities mean the team fixes the right things first, and when I flag a blocker, people listen.

Make it a rhythm, not an event

QA at the end of a project is a fire drill. I make it part of the weekly rhythm: a short pass on whatever was built that week, before the Thursday demo, so feedback lands while the code is still fresh in the developer's head. Small, frequent checks are cheaper than one big audit, and they stop the same issue being copied into ten screens.

The same list, applied to my own work

The concept products on this site are working prototypes, and I hold them to the same list: every page checked at phone and desktop widths for overflow, the main flows working end to end, and the motion layer respecting reduced motion and touch input. It is not glamorous. It is the difference between a prototype that feels like a product and a picture of one.

The takeaway

If you are a designer, test the build, not the file. If you are hiring one, ask how they QA. The answer tells you whether you are getting someone who makes nice screens, or someone who cares about what ships.

Get new articles first.

Leave your email and get one short note when a new article is out. Nothing else, no spam.

One short email when a new article is out. Unsubscribe with one reply. See the Privacy page for details.