Report

ReviewLayer

Visit

Simple visual reviews for websites

The Problem Getting feedback from designers on websites you’ve implemented is cumbersome. You receive a design in Figma or Sketch, and then go on to implement it in the browser. Once you’re done, you create a new PR and request a code review from another developer, who quickly gives you feedback on your code. But getting feedback on the visuals is not as straight-forward. You might already have a staging environment or deploy previews (e.g. with Netlify/Vercel), which you can share with others. You send the preview link to the designer or design team on Slack, and ask for feedback. Once the designer has time for it, they visit the URL, scroll around a bit, and take screenshots of different sizes. They then paste them into Figma and add annotations in the form of red arrows and comments. They can’t preview their suggestions (it’s only comments) and can’t leave feedback on interactive elements. They might also just record a Loom video (which is a pain to extract feedback from as a developer 😅). When they are done, they send the Figma/Loom back to you. You try to understand what exactly they mean (the context isn’t always clear), you make new changes, and the cycle repeats. Approval from the designer or other stakeholders is only possible through Slack (“looks good to me”), and it’s not always clear what has already been implemented and what is still unresolved. This works reasonably well for getting simple feedback (I tried this at my last company), but costs everyone a lot of time and effort. I think this overhead is unnecessary. Benefits For a monthly fee, ReviewLayer integrates with a typical website stack (think GitHub, GitLab, Netlify) and allows your team to leave feedback on deploy previews. You can leave the feedback directly on the preview, without going through extra tools. This way, the context of the feedback becomes clear, or is easy to clarify. Everybody always sees the same version. Designers and other stakeholders can approve parts of the changes (it’s no “all or nothing” like with Figma/Slack). Giving and receiving feedback is quicker than recording+watching Loom videos, and definitely faster than Figma+Screenshots. Because the process integrates with development tools like GitHub and others (think status checks that block merging, integration with bug tracking, etc.), visual review becomes a strong part of reviewing pull requests without adding unnecessary overhead. All in all, I expect this tool to reduce feedback loops by at least 80%, which saves both developers, designers, and other stakeholders like PMs a lot of time. With reviews typically taking about 1h+ for developers and designers each, the tool will pay for itself after the first visual review.
SUBMITTED BY
Marc

Passionate young developer and musician from Berlin 🌱