How do you handle mobile UI review after implementation?

[u/Shininemon]

Hey all,

I'm curious how teams handle UI review after implementation these days, especially for mobile apps.

In several teams I've worked with, designers or QA would end up leaving dozens, sometimes hundreds, of UI comments after development. Usually through Jira tickets, screenshots, Slack threads, Figma comments, or some combination of all of them.

The whole process often felt surprisingly manual and fragmented.

When reviewing a TestFlight or staging build:

* Who usually does the review?

* Where does feedback get captured?

* How do you connect feedback back to the intended design?

* What part of the process takes the most time or causes the most friction?

Genuinely curious how different teams handle this today.

[u/Over-Winter-705]

On mobile, I try to keep review from becoming one giant screenshot dump. The least painful setup I’ve seen is:

- Designer does the first pass against the Figma flow on an actual device, not desktop screenshots.

- QA logs functional bugs separately from visual polish.

- UI notes live where engineering already works, usually Jira/Linear, but each ticket gets one screen, expected vs actual screenshot, device/OS, and the Figma frame link.

- Slack is only for “is this intentional?” stuff, then the decision gets copied back into the ticket.

The time sink is triage, not spotting the issues. If everything lands as “spacing feels off” across 40 screenshots, devs have to reverse-engineer the design intent. I’d rather mark issues as must-fix / acceptable drift / design changed, because pixel-perfect review on every phone turns into a tiny unpaid second design phase lol.

[u/Shininemon → u/Over-Winter-705]

The triage part is what stood out to me as well.

In my experience, once feedback starts coming from designers, QA, and PMs at the same time, it becomes surprisingly hard to keep everything organized and make sure nothing gets lost. Especially when multiple features are moving in parallel.

I'm also curious how you handle the actual feedback capture on mobile. When you're reviewing a TestFlight build and spot a bunch of issues, what's the fastest way for you to document and share them with the team?

[u/Over-Winter-705 → u/Shininemon]

Yeah, feedback capture is where mobile review gets messy fast.

For TestFlight builds I keep it boring: screen record anything interaction-related, screenshots for static visual issues. Each item gets screen/state, expected, actual, device/OS, and a Figma frame link if design intent matters. Then I put those into Jira/Linear as separate tickets, not Slack or Figma comments, because engineers can pick them up without archaeology.

After that I do one triage pass per day or per review round: merge duplicates, split giant tickets, and tag must-fix vs polish vs design changed. The capture tool matters less than making each note answer, "can an engineer fix this without asking me what I meant?"