I’ve had an AMA on Reddit and This is What I’ve Learned About Visual Composer From the Community

5 things I've learned from doing AMA on Reddit

As you may already know, Visual Composer has been going through some changes lately.

We’ve launched a new plugin, which compelled us to change the name of our first plugin, which in turn confused a lot of our users. If you haven’t heard the full story yet, you can check it out here:

For the past 6 months, we’ve been working hard on clearing up the confusion around our brand and our two plugins.

We’ve published articles, created videos, answered comments… and slowly, but steadily, the fog started lifting.

But here’s the curious thing:

The more the confusion cleared up, the more follow-up questions we got. It was almost impossible to follow every thread and answer each and every question.

So we thought of a way to centralize these questions and answer them all at once.

“Let’s do a Reddit AMA!”

I’ve got to admit… I’m not an active Reddit user.

But I do love talking to the Visual Composer community and I knew a huge part of it was hanging out on Reddit.

Now, looking back, I’m blown away by how much I’ve learned from this live conversation.
And I wanted to share with you the top 5 things that I took away from it.

Top 5 Things I’ve Learned About Visual Composer
From the Reddit Community

1: The only way to clear up the confusion was to dig beyond the surface and get to the REAL questions

For almost half a year now we’ve been actively explaining the differences between our first plugin, WPBakery Page Builder, and our new one, Visual Composer Website Builder.

Judging by the comments and questions people were posting about Visual Composer, we were convinced the root of the problem was this confusion around our products.

But after talking to the community on Reddit and digging deeper into their questions, I realized there was another confusion hidden beneath the surface:

What’s going to happen with Visual Composer? What’s the future of the plugins?

Reading between the lines and understanding what our users were thinking about Visual Composer triggered a whole new conversation with my team:

How do we prepare our plugins for the future?

Where do we go from here? Where should we focus our efforts in the next few months?

We’re still in the testing stage, but what I can say for sure is that we’re planning exciting things for our user community in the near future.

2: When you create disruptive products like our plugins, you’ll be equally loved and hated.

This struck me the minute the questions started rolling in.

There was a fine balance between comments from people criticizing my work and comments from users who loved it.

There were people who congratulated me & my team for creating one of the most disruptive products in the WordPress space back in 2011. Others hated the fact that we changed the rules of the game.

And I understood both sides. They were all right in their own way.

On the one hand, we created something innovative. On the other hand, we made mistakes on the way. But who doesn't?

Which leads me to the next thing on my list…

3: Learning from my experience with the first plugin (WPBakery Page Builder) was essential to evolving to a whole new level.

When we developed WPBakery Page Builder, we wanted to redefine the way we build WordPress websites. And that’s exactly what we did.

But, like with any other new tech product, two things happened:

  1. There are always mistakes, bugs, and glitches that can mess things up (especially when the plugin integrates within other products).

    That can be highly frustrating for the users and almost impossible for us to track each one down and fix it in due time, despite our best efforts.

  2. New technology becomes available and sets a brand new standard (and different expectations from the user community).

    We see amazing new technology making its way to the market year by year. Which is why we’ve developed our new plugin, Visual Composer Website Builder using React.js

4: Competition is fiercer than ever and that’s good news—such a great way to push your own limits.

We’ve got a lot of comments about some new products that are in direct competition with our plugins.

The general “vibe” of the questions was Aren’t you scared?

And my genuine answer—and, please believe me, not at all arrogant or self-sufficient—was No, not scared at all.

And that’s because we’ve learned from our past mistakes and wrapped up our experience and the knowledge we’ve gained into a new & better product.

That’s how Visual Composer Website Builder came to life.

When we built WP Bakery Page Builder, we wanted to change the way we used to build websites in WordPress at the time. And we did.

Now, we wanted to meet our users’ current standards and build a complete website builder that covers all they need. And we did.

Because that’s in the Visual Composer DNA: we push our own limits to evolve and create better experiences for our users.

Sure, we make mistakes along the way. But we learn from them and do better work, time and time again.

5: The best way to come up with the next big thing is to listen c-a-r-e-f-u-l-l-y to your users’ wishes.

I left this one for the end, not because it’s the least important. Just the contrary.

After my AMA, I felt like I discovered a secret treasure of brilliant ideas, well-thought opinions, and rock-solid arguments.

Things that my team and I had been thinking about, individually and together, for months. But until the AMA, it all felt like walking on a water bed. If you’ve ever tried to pull that off, you know you can’t walk with confidence on one of those.

But when I talked to the community, saw their concerns about Visual Composer and their on-point questions about our plugins… it was like someone was reading our minds.

But here’s where the AMA made a huge difference…

The community not only voiced concerns and asked questions.
They gave advice, made suggestions, told us what they wanted and expected from us, and planted the seed of new outcomes.

Right now, we’re working on improving Visual Composer Website Builder, taking all that input into consideration.

And to make sure we make the plugin exactly as our users want it, I want to offer you something in exchange for your honest opinion:

I’m giving you free access to the premium version of Visual Composer Website Builder.

I’m giving away 30 free licenses to the premium version of Visual Composer Website Builder. (UPDATE: We are out of free licenses in this giveaway - thanks for the massive interest). Would you like to try it out and let me know what you think? Leave a comment below and, if there are any free licenses still available, my team will give you access. The giveaway will be active for a whole month until May 31, 2019.

Why am I doing this?

Any feedback from our users will help us make the plugin even better (and you’ll have access to all the updates, of course).

All in all, I hope you’ve enjoyed these little nuggets of wisdom from the Reddit community. If you want to read the thread, you’ll find it here—it’s pretty entertaining, I must say.

And I hope you’ll take me on my offer to give Visual Composer Website Builder a free trial. Leave a comment if you’re in!

Thanks for reading,
Michael