What I would do if I were the CEO of Wix or an advisor to the CEO of Wix:

I had fun writing this text, maybe no one will read it, but I believe it contains important things that could be useful… (I hope they don’t delete it from the forum, hehe)

The idea here is that I’m going to pretend I’m the CEO of Wix and I’m talking to the programmers or designers in charge of creating the entire Wix infrastructure.

There’s no intention to offend anyone; I did it just for fun and in the hope that it might also be helpful to someone.

Problem 1: Website Builders
CEO: Why do we have 3 website builders?

Developer: Each editor has its unique function.

CEO: I understand, but let’s focus the budget of the 3 website builders on a single one and give it all the power of the others, and let’s make product improvements only in that one.

One editor should have all the integrated functions and be flexible enough to create any current website. Let’s not waste the budget creating new products; instead, let’s improve the one we already have that works.

Problem 2: Marketplace
CEO: Why isn’t there a marketplace for designers to sell their own templates or resources and earn extra money or create a new source of income?

Programmer: We’ll do it soon, boss. It’s on the list of features to integrate into Wix.

CEO: Great, but this should be a priority, guys, because we would be helping users of all kinds generate more jobs, improve lives, help many families, and also make it easier for customers who create websites with our editor to create the sites they want.

Problem 3: CMS
CEO: Why is the CMS so confusing and lacks easy-to-integrate structures?

Programmer: As it is, it’s easy to understand; you just need to study the CMS documentation well to understand how to work with it.

CEO: Sure, it’s easy to understand if you know the CMS inside out, but let’s add ready-to-use CMS templates, let’s base them on websites that use CMS and can be easily recreated without too many configurations. For example, if someone wants to create a photo selling site, let’s create a ready-to-use CMS template that includes a page for all the photos, one for the categories, one for each category, and a list for the items. Let’s also look for the most commonly used components in these CMS and make them ready to use.

This way, we save users from headaches when they try to create a site that requires CMS usage. In short, let’s make it easier to use, as currently, it’s only understandable if you read the documentation in-depth or through trial and error, and that could frustrate users.

Problem 4: Plan Limitations
CEO: Why are we limiting designers and developers with the new “single editor” plans?

Programmer: The more we limit functions, the faster websites could be because they would require fewer resources or for users to switch plans quickly, allowing us to make more money.

CEO: I understand, it’s a good strategy, but instead of limiting them, we could introduce a pay-to-use feature in each plan. If a user reaches the limit of their plan, they have two options: upgrade to a new plan or simply pay extra if they want more of that limited function. For example, I noticed that you put limits on read and write requests and also on the number of items in the CMS, and here’s where we can do this—let users pay $1 for every additional 1,000 items or $1 for every 5,000 read and write requests. This way, users won’t feel restricted, and they won’t have to use external CMS.

Or, if this is not feasible (which I doubt), then make integrations with external CMS easier and more flexible to configure in just a few clicks.

Problem 5: Site Builder
CEO: Guys, I’ve noticed that the editor is a bit slow to use when I tried to create a site. Why is it slow?

Developer: It could be because of the number of resources it has ready to use.

CEO: I see, so let’s focus on making those resources downloadable externally and not internal to the editor.

The editor should be as fast and fluid as possible. Let’s also investigate the errors causing slowness in the editor and improve it.

Problem 6: Learning Wix
CEO: Why does learning the platform mostly rely on documentation?

Programmer & Designer: It’s because text-based content can reach any language on the planet.

CEO: That’s true, but we need to allocate a budget to create video tutorials. Reading can sometimes lead to confusion and fatigue in trying to understand, and that’s because users learn more quickly when they understand things visually.

Ideally, we should look on the internet for questions asked in social media, forums, communities, etc., and have an expert explain those questions every day in video format.

Understand that the more users comprehend how our platform works, the more opportunities they have to create incredible things. If they don’t understand and have to research on their own for hours, they’ll just feel confused and move to another platform.

Problem 7: Editor Limitations
CEO: Why are some editor component settings limited in terms of configuration?

Programmer: It makes it easier for us to update.

CEO: Okay, but let’s not limit the configuration and allow it to be unlimited. For example, I’ve noticed that the form is very limited in terms of configuration and needs to be edited externally when it should be editable in the same editor without pop-up windows for editing. Editing should be consistent for everything in terms of HTML and CSS.

That’s it; I hope you had some fun.

3 Likes

Problem 1 - Editor x is being transformed into Studio at a later date.

Problem 6 - what’s stopping you- ever heard of you tube channel Wix Fix

1 Like

This was cool! You’ve addressed a LOT of the major points many developers are constantly discussing and the problems we continue to face. Hopefully the wix team will take some of this into account :slight_smile:

1 Like