As developers, we kept running into the same problem: code reviews rarely show the actual user-facing impact of a change. Reviewers have to pull branches, run the app locally, and manually compare behavior—or approve based on code alone.
PR Preview exists to make visual changes obvious. It records a user journey before and after a pull request, then automatically generates a side-by-side comparison video that can be shared directly in the PR. The goal is simple: faster reviews, fewer misunderstandings, and more confidence when shipping UI changes.
65 people supporting this launch
4.8
6 ratings
AI video with native sound, paid per clip. Nothing stored.
A calmer Mac menu bar, one click away.
Enterprise Software. Intelligent Automation. Global Impact.
Comments
18AI Researcher | Co-founder at Open Gigantic | Building Superbrain
as a developers PR preview is the tough part but this solution is crazy
Thank you for the feedback and support!
I build & lead the engineering behind AI agents · Co-Founder & VP R&D @ Dial
This solves a real friction point in code review workflows. The gap between static diffs and actual visual changes is huge - designers often can't spot regressions in a code review, and PMs have to manually test branches to validate UX didn't break. Auto-generated before/after videos that work directly in the PR make it so much easier to catch subtle layout bugs, color shifts, or accessibility issues without checking out locally. The sub-60s render time is impressive too.
Thank you for the feedback
AI-powered golf trip planning tool helping golfers build custom itineraries.
Solving a genuine bottleneck in the review process — most teams either skip visual review entirely or someone has to manually pull the branch and run it locally, which kills momentum. Automating before/after video capture directly in the PR is a smart zero-friction approach. Would be great to see integration with Linear or Jira to auto-attach the video to the linked issue. The free tier is a great hook for open source projects.
Thank you very much for the feedback
i write a16z speedrun scout checks within 24hours | Co-Founder & CTO at Dial AI
Code review lag is real when you're trying to iterate on UI. Your reviewers have to manually spin up your branch, run the app, and manually click around to actually see the change. PR Preview flips this - suddenly your before/after video is right in the PR itself. Saves time, prevents visual misunderstandings, and gets code merged faster. Love the simple approach here.
Thank you very much for the feedback
YouThere.live
Really like how PR Preview tackles the classic “code looks fine, but what actually changed for users?” problem. Having an automatic before/after video for each PR makes it so much easier for reviewers and PMs to catch UX regressions, micro-copy changes, and layout bugs without pulling the branch locally. Also feels super helpful for async, distributed teams where designers or stakeholders can just watch the clip in the PR and give feedback. Curious how it handles longer user journeys and flaky UI states, but the core idea is spot on for UI-heavy products.
Thank you for the feedback. At the moment it is quite early stage / still testing on several more flaky UI components but slowly getting there.
I'm SEO Expert and devloper and wanderlust
How do you think about this scenario for video, I'm so much amazed and want to test it right now!!
Thank you very much for the feedback. It is available as an open source tool at the moment and once the tech is polished enough we might develop a cloud solution with some extra features for teams.
tired employee
This solves a very real gap in code review: PRs show what changed in code, but not always what changed for users. A before/after user journey video would make UI reviews much easier for developers, PMs, and designers, especially in async teams. I can see this helping catch layout regressions, copy changes, and broken flows before merge. Curious how it handles auth-heavy or flaky states, but the core idea is immediately practical.
Thank you for the feedback. At the moment you can pause on the authentication step and authenticate on the UI manually and then continue the recording once you are in.
This solves a very real review gap: code diffs show implementation, but not the user journey. A before/after video in the PR would make async review much easier for developers, PMs, and designers. Curious whether it supports authenticated flows through saved sessions or test credentials, since that’s where a lot of visual regressions hide.
Thank you for the feedback!. It does support it but in a manual way. You would see the application in an iframe and you would have to authenticate there yourself so you can continue the recording process.
Somehow this was something I missed greatly, the real "result" view of what has changed in a PR to the final users, one image is worth more than a thousand words, 1 video is worth more than a thousand lines of code :D
just an ai developer
Running the same journey against both the base build and the PR build and rendering a side-by-side is a neat CI trick. How are the journeys defined — recorded once and replayed, or written as scripts like Playwright specs? I'm curious what happens when a PR intentionally changes the flow (a button moves, a step disappears): does the 'after' run adapt or just fail? Being open source makes this easy to trial on a side project, which I appreciate.