Vev Pricing Overview

For designers, Vev is super intuitive. Compared to other no-code tools it makes creating modern web experiences straightforward, repeatable and so much less clunky. If you can use Figma, you'll figure out your way around Vev in no time.

Our dev team love using CLI to create more complex components when we need them - basically anything Vev doesn't do out the the box, a developer can usually add in.

All in all it's an excellent tool for our enterprise clients. Review collected by and hosted on G2.com.

Had a couple of issues with the review feature permissions initially although to be fair the support team got that sorted really quick.

Was worried about the price at first but having used it for a few months now the value is pretty obvious. We're yet to find something we can't build in Vev and we're actually finding we can now use it to replace a bunch of other tools that didn't do everything we needed and were cumulatively costing us a lot too. Review collected by and hosted on G2.com.

It looks like it does parallax websites well. Review collected by and hosted on G2.com.

Everything else; the design editor is glitchy and unstructured. It's got a lot of CSS options like width, height, flex, etc but they all have different names from CSS so your tech team AND your designers need to learn a new syntax just for VEV, and those controls don't always work so get used to refreshing the design editor, a lot.

Custom React components require a huge amount of boilerplate; for example: A simple input with styling parameters can easily come out at 1000 lines of code and that's if it works at all. Want to build a component with three.js, that won't work. Want to add sounds and images as assets? That won't work either.

Then we get onto actions and events. It is possible to create actions and events, and this is quite nice and clever, the intention being that you can build isolated components that a non-techy can string together in the editor. However, you would need an incredible amount of document for each component to explain how your custom actions and events work together.

We tried it with a collection of very simple components: buttons, text input and a score, the result was a mess. Our estimate was that it would take 5 to 10 times the development time to build VEV components.

The NO CODE part of this actually requires a huge amount of coding.

It's ok for Parallax Websites. Review collected by and hosted on G2.com.