Know a bug is really fixed, without checking it yourself
A developer says “done”, the task is closed, and someone still has to open the site on a phone to be sure. UICheck does that part. When a finding is marked fixed, a comment is resolved or its task is closed in Linear, Jira, GitHub or Worksynk, UICheck checks that page again at the screen sizes where it broke, shows it before and now, confirms the fix or reopens it, and emails the result.
Included in Lens and Prism · Free plan to try UICheck, no card needed
How it works
- 1
Close it the way you already do
Mark it fixed in UICheck, resolve the comment, or move the task to Done in your tracker. Bulk works too.
- 2
UICheck re-checks the page
Within minutes, only that page, only at the widths where it was broken. It doesn’t use your daily checks.
- 3
Get the answer
Fixed is confirmed, still there is reopened, and an email lists both, with Before and Now for every comment.
What it catches
- “Fixed” tasks where the bug is still on the phone layout
- Fixes that broke the same spot at another screen size
- Client comments that were resolved but look the same
- Bugs that come back in a later deploy (marked Reopened)
- Tasks closed in Linear, Jira, GitHub or Worksynk, synced back
- One email per check: what’s fixed, what’s still there
Questions
What starts a re-check?
Marking a finding fixed (one or many), resolving a comment, or a task made from either being closed in Linear, Jira, GitHub or Worksynk. UICheck reads the tracker every few minutes, so nobody has to tell it.
Does it use my daily checks?
No. Re-checks only test that page at the sizes it broke, and don’t count. They are part of Lens and Prism; on Free, your next check of the page confirms the fix instead.
What if a task is reopened in the tracker?
The fix mark UICheck made from the closed task is taken back, so the finding is open again. A mark someone made by hand is never changed.
Who gets the email?
The person who marked it fixed, or who sent it to the tracker. Comments go to the person who wrote them, with Before and Now and a one-click “Yes, it’s fixed”. Anyone can turn these emails off.
More answers in the FAQ
More ways to check
Breakpoint sweep
Find every width where your layout breaks
Safari & Firefox
Test your website on Safari without a Mac
Figma comparison
Compare your website to the Figma design
Full-site checks
Check every page of your website before launch
Integrations
Send every bug where your team already works
Visual changes
See what changed since the version you approved
Review mode
Walk through the site on every device at once
Client feedback
Feedback from clients, in the same place as the bugs
Change alerts
Know when your sites change, and if it broke something
Teams
QA your client sites as a team
CI / deploys
Check every deploy before your client does