The problem: the build is never quite the design
The mock-up was approved. Then it was built, and the heading sits a little too close to the picture, the button is the wrong weight, the card grid breaks at one tablet width and the empty state was never designed at all. None of this shows in the design file. It shows on the page, and only at certain sizes.
Design review after the build is usually done with screenshots and arrows. A screenshot does not say which element it shows, what styles it has or how wide the window was, so the front-end developer starts every fix by finding the thing again.
How a design review runs in ClickNote
- Open the review link on the staging or live site. The review tools load on the real page, in your own browser, at your own window size. There is nothing to install.
- Click the element and choose the kind of note: Design, Wording, Something’s broken or Question. The type travels with the note, so a developer can work through the design notes and a copywriter through the wording.
- Say what should change. “16px more space above this” on the heading itself is a complete instruction.
- Review each layout. Mobile view opens the site in a phone-sized window on your computer, with the tools in it. Or resize your own window, or open the link on a phone or tablet. Every note records the viewport it was left at.
- Leave a note about the whole page when the point is not one element: the rhythm of a page, a missing state, a flow that takes one step too many.
- Finish the round with one button, so the developer knows the list is complete.
What the front-end developer gets
- The element, exactly: its CSS selector and XPath, its text and a snippet of its HTML, and where in it the reviewer clicked.
- Its attributes and styles, as the browser had them when the note was left.
- The view: the viewport, the layout it falls into (mobile, tablet or desktop), the browser and the operating system.
- A screenshot of the element and what is around it.
- Where it lives in the theme, on the platforms that say: the Shopify section and block, the WordPress template and the page builder’s container.
In the dashboard the notes filter by type, page, reviewer and status. The designer sees the status of each note on the site itself, and can check a note marked Done by looking at the element it is pinned to. Questions go in the note’s thread, next to the thing they are about.
UX feedback, not only pixels
Much of what a UX review finds is not visual: a label that misleads, an error message that blames the user, a form that asks for something twice. Those are Wording and Question notes on the element concerned. In Browse mode the site behaves normally, so a reviewer can open menus, fill in a basket or step through a form, then switch to Comment at the step that is wrong.
For the signed-in screens of a product, see feedback on web apps, dashboards and admin panels.
Pins that survive the fixes
A review is not over when the first fixes go in. As the page changes, each pin finds its element again: by selector, then by XPath, then by a fingerprint of the element’s text. A second round uses the same review link.
What ClickNote does not do
- No design files. It does not open Figma files, images, PDFs or video. It reviews web pages in a browser.
- No comparison with the mock-up. There is no overlay, no pixel difference and no visual regression testing.
- No automated audit. It does not test accessibility, contrast or performance. It records what a person noticed.
- No drawing on the page. A note is pinned to an element and written in words. There are no arrows or freehand marks.
- No video or session recording.
If what you are checking is whether things work, not how they look, read website bug reporting and QA.