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:
- waited nearly 13 months to share any serious updates;
- gave an update not connected to the previous update—where are the various initiatives? How are those teams coming?
- 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);
- 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.”