We launch a feature here on Thursday, and the landing page section for it is the one new users keep bringing up on calls and in replies, more than the hero, more than pricing.
It is a simple block. One sentence: see the change before it ships. One picture of a working copy of your site with the change on it, and two buttons: approve, or send it back.
I think it works because it answers the question people actually have about any tool that writes code for them: what if it gets it wrong? The answer is not trust us , it is look at it first . The other sections explain what it does. This one removes the fear.
Curious what the equivalent section is on your landing page: the one that answers the fear rather than describing the feature. And for those who have run the test, did it convert better than the feature description?
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!
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?
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?
Hey @mikita_aliaksandrovich and team, lovely product. Congrats on launch.
Would definitely, give it a time to explore it more.
Best wishes ahead 😄
@whatshivamdo Thank you! WE would definetely will be glad to hear your feedback!
@whatshivamdo Same here, looking forward to it, Shivam!
Done! Good luck with your launch.
@ititov_agency Thank you, Dmitry, really appreciate it!
@ititov_agency Thank you, really appreciate the support!
@ititov_agency Your support has been truly great.
Awesome. Congratats!
@tymoxx Thank you! Appreciate your feedback!
@tymoxx Thank you, Yuri!
Good luck with the launch!
@dzianis_yatsenka Thank you! Really appreciate it!
@dzianis_yatsenka Thanks a lot, really appreciate you stopping by!