We tone down our new product to fit the lifetime license model and put it up on the marketplace, or…Ģ. In short, we couldn’t sell another product under the name of Visual Composer outside their platform.ġ. We Missed One Key Detail That Forced Us Into a Difficult DecisionĪnd that “detail” was our contractual limitations with Envato. We also wanted to be directly in touch with our users to offer them stronger, faster support.īut what happened next was anything but what we had planned: We tried to move away from the lifetime license model, because our new product was more complex in features, and built for a growing part of our users whose website building needs have rapidly evolved.Īll this and the new React.JS technical stack meant much higher development costs that could only be sustained with a yearly license model. The Website Builder, our new product, was meant to go in a different direction. The Page Builder was an Envato-exclusive product with lifetime license (like all products sold with Envato). This is a different tool from the Visual Composer Page Builder and we wanted to make that crystal clear to our users (clearly, that did NOT go according to plan). It all began with our new product, the Visual Composer Website Builder. So why would we decide all of the sudden to change the name our best-known product?Īs for the long answer, you can watch the story unfold in the video or you can read it below. It was included as a premium plugin in many of your favorite themes. You’ve probably seen that name dozens of times, on every major WP theme page. Where It All Started: Changing the Name of Visual Composer Page Builder Things happened gradually, and the more we tried to “fix” problems along the way, the deeper they got. Secondly, we wrote this post to finally explain what caused it from the very beginning.Īs you’ll see, it’s quite a brain-twisting journey that led us onto this path. We’re Deeply Sorry for the Confusion Created Around Visual ComposerĪnd, most important, we’re sorry for not explaining what caused this mess from the very beginning. So we decided to write this post for two big reasons.įirst and foremost, we wanted to apologize for making an already messy situation worse. But also because we naively believed we could “fix it” (spoiler alert: we could not.) Partly, because we got swallowed whole into the snowball and had to roll down with it. What started as a minor problem quickly snowballed into a confusing mess that we did not handle right. This confusion has upset many of our users, as well as our long-term partners.
0 kommentar(er)
