Streaming live at 10am (PST)

So has The Wishlist been abandoned?

Thanks Jianoa for the detailed statement, many of us truly do appreciate this effort at transparency. I echo many others when I say that I really do hope this means that the Wishlist starts to be utilised better (a LOT better) by Webflow staff.

Fingers crossed the Series B funding unlocks a lot of these aspirations for you - I’m rooting for you!

1 Like

While I appreciate the attempt at addressing this subject, the answer we are given is, literally, just wait another 4 months and then we can start discussing it.

I realize I’m a constant source of pessimism in this thread. I’m glad many of you are still optimists in this regard. I hope I can eat my hat. Soon.

I sincerely hope there is some semblance of progress before the Community Business Reviews occur. I think those are fantastic idea and I hope Webflow follows through. In the meantime, there are some basic missing features listed on the wishlist that are downright embarrassing for some of who have clients.


This timeline is amazing! Even better than what we have internally :wink:

1 Like

Another nail in the Wishlist coffin. Yesterday, Webflow announced it has no “immediate priority” for multi-language sites. That was the 2nd-highest Webflow Wishlist item,

As I noted, Webflow developers are unable to expand their quite-fragile backend. If it wasn’t so shamefully noted with a curt response, I’d be more sympathetic.

Even the CEO of Weglot chimed in, sharing the disappointment (or schadenfreude?). The Wishlist is a place to vent more or less, it seems. FWIW, Weglot is not ideal: $230/year for someone to slow down your site w/ external scripts, limit translated pages to 50k views/month, 50k words total (goodbye blogs), and a tedious amount of day-to-day effort as you update your site’s layout.

I can’t blame Webflow: the Webflow backend is seemingly in tatters after bolting on features and QA is likely dropping bombs every few weeks to product managers who really do not understand Webflow.

Alas. Good effort, Webflow: you have simply detached from the reality of your users. It’s been a disappointing timeline of events.

EDIT: for those curious what Webflow had previously written (late December 2019),

From infrastructure improvements, to staffing up our team, we’re currently working through various initiatives that will enable us to create a foundation for multi-language sites. Though we can’t commit to any timeline, as a team we recognize how important building multi-language sites is to all of you.

The comments on the Wishlist item are clear: users are disappointed, frustrated, confused, and disenchanted that Webflow has any ability to deliver on what many of its users actually need.


I understand the frustration, especially if you were holding out for this feature among all others, but they took the time to candidly respond to a popular Wishlist item not being an immediate priority on their roadmap—while giving a solution (albeit something that may not work for everyone)—and even said that they intend to build it the right way natively at some point. In my opinion this doesn’t seem at all like they’re abandoning the feature, but instead being transparent about the shifting roadmap they’re using internally and making sure they approach it correctly.

They may not be following the request priority of the Wishlist, but I think it’s hyperbolic to assume that they’re “detatched from the reality of [their] users”. Let’s take the 5,438 votes as individuals throwing their support behind the idea (rather than a much more likely ~3,000 folks who used up to 3 of their votes on the idea) and compare that to their 100,000 active customers. At best, that’s less than 6% support for a feature that doesn’t address the other pressing issues you’ve brought up in your own response. Your edit actually further strengthens their priority as I’d rather they focus on the core of their product before offering solutions that one, are already possible with third-party tools, and two, require a strong foundation and thoughtful implementation to be successful.

Webflow is really a unique player in the no-code (or low-code) space and it’s painfully obvious how promising it is based on the passionate responses we’re seeing here in the community. Let’s just remember that their platform (specifically the Hosting part of it) is completely optional and can be circumvented by exporting the project to modify as you see fit. It’s by no means the cheapest option, and doesn’t work for every situation, but when it makes sense for a project I’d imagine most of us can agree that it’s an absolute joy to use. When my clients need something else, I either look into other platforms all together, or consider exporting for modification to fit with the needs of the project at hand.

I apologize if my optimistic posts don’t seem super helpful to the critical responses here on the forum, but I personally feel like they need to be making more announcements like this that cause the exact type of responses and frustration from some customers. When that happens, I’ll be right here with my half full glass and the trust in the team to do what’s best in the long run.

This no-code game is a marathon, not a sprint, so let’s all hope that we see consistent, meaningful steps to continue transparency and features that no only help the fringe users but also the customer base as a whole :webflow_heart:


Oh, no, I agree with you: Webflow’s foundation is significantly depressed and far above its capacity (see my earlier post in this thread). I honestly believe Webflow will significantly weaken the Designer’s performance & reliability if it adds any more significant features.

If you read my previous post here, you’ll see we are on a similar wavelength: where are those foundational improvements? What is being done about Designer performance, the robustness of CMS’ backend, interactions treated as single-page citizens, back-end performance (that nearly killed nested collections, as admitted by Vlad), etc.? Those are the real priority, but those have next to zero transparency.

I would love Webflow to dedicate 6 to 12 months to pure back-end optimization and QA. Webflow desperately needs it and I’ll be the first to call for it: implement a total feature freeze now and fix the underlying weaknesses.

I’ll go even further: Webflow could even consider making some performance-degrading, niche, low-use features as opt-in only and disable these features completely on all other sites.

// on your notes

The actual issue revolve around communication, as with every serious misstep. We’re all developers in some way here. Unfortunately, Webflow’s Wishlist administrators:

  1. waited nearly 13 months to share any serious updates;
  2. gave an update not connected to the previous update—where are the various initiatives? How are those teams coming?
  3. recommended third-party software that everyone who cares about multi-lingual already knows about (because Webflow has an entire page for third-party localization tools, which Webflow somehow forgot to link, but instead picked a pricey favorite);
  4. missed the point of a Wishlist if items need a significant number of “100k users” to implement. Webflow has already implemented many features with far fewer votes. This is customer feedback 101, IMO: no one should expect 100k users to line-up for a single feature request before it becomes a priority.

From infrastructure improvements, to staffing up our team, we’re currently working through various initiatives that will enable us to create a foundation for multi-language sites. Though we can’t commit to any timeline, as a team we recognize how important building multi-language sites is to all of you.

In the end, we agree. Webflow should avoid falling into the trap of only delaying Wishlist items, but then also make 1) consistent, 2) public, and 3) material progress on its mountains of technical debt, most of it sight unseen and completely disconnected from the Wishlist.

Real candor: “Webflow is undergoing a serious back-end upgrades; this is critical for both reliability and performance, but also for sustainable growth and one day implementing major features from the Wishlist. The Wishlist is thus moving to a backlog-only mode until we are completely ready. We’ll be going through stages. Today is stage 1. We hope to reach stage 2 by Q4.”


I totally get it and I understand both you and I (as well as all other community members) want Webflow to grow, sustainably, into a truly robust platform that works for all types and scopes of projects. It takes a focused vision for the future (which I believe they have) along with lots and lots of time, energy, and passion. These changes won’t happen over night—not even after multiple rounds of funding.

With money comes new talent with new perspectives and insight, and with that, they shift their focus. This is all comes with new challenges, balancing a growing user base, and making sure they set up their current and future employees with the tools and freedom to thrive. They need to keep a strong monetary flow so they don’t depend on future funding and become reliant on outside ideas or goals. All of that happens in tandem with evolving technology and the goal of being on the forefront of that evolution.

I think everyone can agree that hindsight is 2020 and the only reason we should be looking to the past is to ensure we do things better in the future. In the 20 days of 2021 I’ve seen promising things from the Webflow team that I hope they continue with for the next 11 months and well into the years to come. Let’s encourage them to be better today while they focus on tomorrow, rather than criticizing them on what they did yesterday. Let’s encourage quality work and appreciate the amazing product they’ve made while ensuring that our criticisms continue moving them forward and focused on their customers needs.

I’m looking forward to their first Community Business Review in April and I feel like we owe it to the team to see how they approach this new avenue for communication.

1 Like

Sound like you stop developing your own tool and are going to really more on plugins and 3rd party tools thats one of the major complaints because of the costs … You read that everywhere on the forums so you still dont listen.

Also there is a lot wrong with the ui of the designer cutting of things no search features in the cms . This is something you can make a road map for too.

We already have made this request to the support webflow forums facebook socialmedia channels you just dont seem to listen.


“Enterprise plans”…that’s all you need to know. I’ve yet to see a company tackle enterprise that hasn’t seen a fall in small business support. I don’t just mean responsiveness of service, but diverting resources to the features that actually help small business become efficient and productive. A newly found round of millions in funding and basic features requested for years are still not addressed. I expect an exacerbation in these matters.


I do not see this until @callmevlad mentions this thread in his reply to another post.

Yes! I am so excited to hear this.

This is the very key reason that clients are not convinced to use Webflow for e-commerce. I believe it is essential to any serious online shop.

Btw, I also think it is important to raise or remove the limit of items for nested collection list.
Currently, it is only 5… which makes this excellent feature almost useless.



Wow, I can’t believe they deleted it. That leaves a really bad taste in my mouth. Come on guys, don’t go censoring people for calling you out. This is how companies fail.


Fast forwind → 2031, interview with Vlad in WIRED

We started this company Webflow which we wanted to disrupt the community. We did very well. After a few rounds of injected capital we had to shift our focus more and more towards those of the investors. Meanwhile we neglected the voice of many users. Other start ups caught up on us and the rest is history.

Please dont let this be true


I recently read this good article on the rise and fall of InVision. It should be a sobering lesson to the Product People at Webflow.

InVision was in everyone’s mouth. They had all these ambitious plans, including actually building their own design tool. They were doing conferences, had their own publications and merch. All they concentrated on was getting enterprise customers, which they got, including us.

Now just a few years later we just cancelled our enterprise account. Apparently, we are not alone and people are leaving in droves.

What was their biggest mistake? They didn’t listen to their customers and didn’t actually build the things people asked for. They put all their efforts into everything BUT their product.

Here is the article:

It kind of reminds me of this situation.

Don’t get me wrong I love Webflow and what it can do. But all it takes is a worthy competitor, which there is not really currently. Bubble is already a much better choice if you need more functional things, rather than just a nice portfolio or static site, which is what Webflow themselves seem to think is their main target group. But all those people that make portfolio websites for themselves, also actually need to build websites for clients. And if you client says they need a website in more than one language (like you would pretty much anywhere outside the US) and then you have to tell them there is separate service you have to pay for an log into and all that, they might not be happy about that.

As you can see with Wordpress and many others: the best way to quickly have people be invested in your platform, while also giving people what they want, is to have a solid plugin system. Wordpress would be long dead without the millions of plugins, a lot of which are actually very good. Sure, you create some new problems and the usability is not always super great, but I’d sure much rather have that, then having to do a half hour video on translations and explaining why there is a different tool and how they work together and having to constantly justify the shortcomings of Webflow to my clients.


So right, and interesting the article mentioned folders when we’ve been waiting years for similar functionality in asset management.
I have seen website companies receive investment before and completely lose the plot; primarily the addition of brand new features at the expense of stability…

I just created some folders for assets in Webflow the other day actually. What are you referring to?

Yes, but it was pretty much top of the wishlist for years! It;s the reason I never used webflow for image-heavy sites.

Because I almost missed it – Webflow recently announced their “Q2 Community Update” in a month and a half from now. You can register to join at that link.

We’re excited to bring back quarterly sessions with our CEO Vlad Magdalin and other leaders from the company. In these sessions our community can look forward to hearing first-hand about our company news, initiatives and roadmap updates.

Join us on Wednesday, April 14th at 11am PT for a live session covering features we’re working on, programs we’re developing, and where we can use your help and input. Register below and submit questions beforehand from the link in your confirmation email.

1 Like

Common, we built entire web-based ERP system for our company in 1-2 years with 3 developers. The ERP is handling millions transaction of material, stock, production entries every year. 300 users are using the app for daily operations for everything from purchasing, invoicing, production, stock management, shipping, R&D and just about every other business process we need.

I am sure adding couple of essential web features to Webflow, should not take the same time as sending NASA’s SLS rocket into space!!


Did they actually said ‘‘GOODBYE JOJO’’ to it and never looked back?