Ovren Live Preview - See your product change live before it ships
by•
Describe a change in plain words. Ovren writes the code on a safe copy of your project and gives you a live preview of every frontend change — your real page, with the change on it. Click through it, approve it, and your team merges the pull request.
Replies
What does the preview include... different viewport sizes or does the requester need to switch between desktop and mobile manually?
@nuseir_yassin1 Good question, Nuseir! There's no desktop/mobile toggle in the preview panel today. The Open button loads the preview in its own tab, so you can resize the window or use your browser's device mode to check mobile. Would a built-in switch be useful for your team?
@nuseir_yassin1 Paul's right, and it's a fair gap. Opening the preview in its own tab and using your browser's device mode works today, but a requester shouldn't have to know that trick. A desktop/mobile switch in the panel is now on our list. Thanks for raising it!
I like how it clearly states the division of responsibility. Non-technical teammates judge the result, and developers judge the implementation. Congrats on the launch!
@himani_sah1 Thanks, Himani!
Glad that comes through. Who usually plays the "judge the result" role on your team?
A lot of times there are small changes that are needed for the website, and they stay in the backlog for weeks. This will reduce those. Congrats on the second launch.
@roopreddy Thanks, Roop! Those small changes are exactly what we had in mind. Which kind tends to get stuck the longest for you?
As a developer, one of my day-to-day challenges is having to pause larger improvements to handle small UI portal tweaks. The context switching alone consumes a significant amount of my internal resources. This tool allows my managers and UI designers to implement validate their ideas more quickly WITHOUT DEPLOYMENT. And deploy only final version.
Every product has plenty pending quick tweaks or customer requests for UI improvements. It’s great that Ovren could handle these small UI tasks and, most importantly, enable teams to validate the fixes visually before merging and deploying them.
I hope many teams discover this product and enjoy using it.
@maxim_agapov Thanks! You put the developer half of the story better than any of us. The small tweaks were never hard, they were interruptions and every one cost you and hour of context to pick the bigger work back up. Now the people who asked for the change can check it themselves. Proud to build this with you!
seeing the section on our real page before anyone merges is realy what our marketing side keeps asking for
if the change touches something shared like the header, does the preview show it across all pages or only the one you described??? and what about pages behind a login???
@thamibenjelloun Good questions, both of them.
Shared header: the preview shows the page where the change was made, so you see the new header there, in context, before anyone merges. It does not walk through every other page that uses the same header. For a shared component like that, your developer checks the rest in the pull request, where the change to the header is a single file anyway.
Pages behind a login: the preview runs on sample data rather than your real backend, so it does not depend on a real signed-in session. How well a page behind login renders depends on how your app handles sign-in. What do you use for it? I can tell you what to expect.
@thamibenjelloun Thanks, that's exactly who we built it for.
Two great questions. What I can say for sure: the preview opens on the page your change affects, and it runs on generated sample data, not your real accounts. How far you can click from there, to other pages or into logged-in areas, is a question for @mikita_aliaksandrovich, and I'd rather he gives you the exact answer than I guess.
What's the first thing your marketing side would want to see in a preview?