Speed up visual reviews
ReviewLayer is a powerful tool to quickly collect visual feedback on live webpages. No more annotated screenshots.
Contextual Feedback
Leave comments and feedback directly in the browser on deploy previews and staging environments
Reduce Feedback Loops by 80%
Get everybody on the same version and resolve feedback more quickly by eliminating manual screenshots and unnecessary back and forth
Make feedback simple
Get everybody on the same (web)page and improve your design review today
Integrate with devtools
Great integrations with developer tools. Add status checks to pull requests and sync comments and tasks between your platforms.
Approval Workflows
Prevent mistakes from leaking into production and require approval from your team members.
How it works
Let’s understand why you need ReviewLayer
Without ReviewLayer...
1. A dev makes change to your company’s website
They might implement a new landing page, update the styles of a button, or add a new section to your webapp.
2. New Pull Request
They create a Pull Request on GitHub. The CI pipeline (like Netlify) automatically creates a deploy preview in the background.
3. Request Feedback
After they’ve waited for the deploy preview to finish building, your dev copies the preview URL and sends it to your designer or product manager on Slack, asking for feedback.
4. Teammate takes screenshots
Once the designer has some spare-time, they will open the link and try to find the change. They then take a few screenshots and add red arrows and text with their feedback.
5. They send a looong message
Your dev receives an enormous message with hundreds of bullet points of feedback. The message looks very intimidating and they procrastinate resolving the feedback.
6. Developer lacks context but tries their best
Your dev finally decides to implement their feedback. But it's hard to understand what exactly the designer meant – and because there are so many items, it's hard to ask for clarification.
7. Resolve Feedback
Your dev pushes new changes to GitHub, waits again for Netlify, and asks for another round of feedback. The designer compares their feedback notes with the status quo, and spot more flaws…
Go back to Request Feedback a few more times8. Approve Changes
After too much back-and-forth, your designer gives up. They send you a “looks good to me”-message even though that icon is still 4px off.
9. Merge Pull Request
Being exhausted, your developer finally clicks the merge button, hoping for a better way to receive feedback.
Result: Lots of back-and-forth for something that should be simple. Many manual steps resulting in lots of unnecessary overhead… just to get another pair of eyes on simple changes.
But with ReviewLayer...
1. A dev makes change to your company’s website
They might implement a new landing page, update the styles of a button, or add a new section to your webapp.
2. New Pull Request
They create a Pull Request on GitHub. The CI pipeline (like Netlify) automatically creates a deploy preview in the background.
3. Get Feedback
Once your dev requests feedback on the pull request, your designer or PM get a Slack notification. The notification includes the deploy preview link which integrates ReviewLayer. Your dev has added a comment on the preview to draw attention to what they would like to get feedback on.
Save 3+ steps and 20min4. Resolve Feedback
Your designer or PM adds feedback directly on the deploy preview. The developer gets notified about their reply, makes changes, and pushes them to GitHub. Your designer/PM can now approve the change or ask for revisions.
Save 10+ steps and an hour5. Approve Changes
Your designer has another look. After verifying that everything looks good, they approve the changes using ReviewLayer and the developer is notified.
6. Merge Pull Request
Your developer clicks the merge button (or simply lets GitHub merge the PR automatically with a successful status check).
Result: Back and forth reduced by more than 80%. Visual review is as simple and quick as code review. Barrier to provide feedback is very low, making it effortless to collect and review feedback for everyone.
Save time on visual reviews
Quickly get feedback on your pull requests when you need it
Questions and answers
What is the main problem you solve?
Code review is a solved problem. With tools like GitHub and GitLab, team members can quickly give feedback on each other's code. But feedback on visuals is still hard. ReviewLayer makes it easy to get visual feedback on your live webpages. No more annotated screenshots.
Why should I choose ReviewLayer over other tools?
There are a few feedback tools similar to ReviewLayer. But they don't integrate with deploy previews or pull requests, which makes their value to developers negligible.
What tools do you integrate with?
ReviewLayer can be connected to GitHub, GitLab, and Netlify. It deeply integrates with Pull Requests and Deploy Previews, and is super simple to set up.
How much does it cost?
ReviewLayer is currently in invite-only beta and free to use during the beta. We added pricing information to the Pricing page.
What browsers do you support?
We support all main browsers: Chrome and its siblings, Firefox, and Safari (but sorry, no Internet Explorer)
Why did you create this product?
On my previous job, I was fed up with the design feedback process on my pull requests. I’d send the preview URL to a designer, who would then take multiple screenshots of the page and add comments on top of them. We would repeat this many times. The feedback process above is real and I always thought “Isn’t there a better way?” That's why I decided to build it ✨
Reduce feedback loops by 80% today
Streamline the design review between developers and designers