I decided to write this topic because I became a huge fan of NocoBase since last year. In my view, it’s a unique CRUD tool, it allows us as a company to build interfaces and automate processes for a massive range of tasks in record time. I am also happy to see how rapidly the product evolves and gains new features.
However, to be honest, I’m quite surprised that version 2.0 was granted “Release” status in its current state.
While we finally got access to all these amazing new features like advanced handling of templates, JS fields/blocks, and AI employees, there’s a significant “but.” In many scenarios, we simply cannot use these new features because the new blocks lack critical basic functionality that we’ve relied on in the “Classic” (1.x) versions.
The daily struggle is real:
Regression in basics: New blocks often miss essential features like the ability to associate/deassociate records or apply custom styling for columns, many of previously commercial plug-ins are not ready to work in modern pages. etc.
Rigidity: Linking rules feel less flexible than they used to be and sometimes work unstable.
Stability: Reading the forum and following the project in github I see that the number of bugs being discovered is still quite high for a “release”.
It feels like we are caught in a paradox: we have these shiny new tools, but we can’t build a production-ready house with them because the foundation (the basic block functions) isn’t finished yet.
I believe many of you feel the same way.
I love this project and want it to succeed, that’s why I hope the team hears us: we need the “basics” in 2.0 to catch up with the “Classic” version so we can actually use all this new power.
Yes I completely agree. I suspect the team has spent a lot of time developing and fixing the AI features. Although those are nice to have, the core features as mentioned above are much more important for most applications.
I hope adding back the missing parts will also be a key focus for the dev team the coming period.
100% agree. I love nocobase too and I’m committed for the long haul! However, there are numerous capabilities I need from the pre- 2.0 that are not available yet.
I’m also a big fan of NocoBase and I truly appreciate how fast the team is innovating. The new capabilities in 2.0 are impressive — especially JS fields/blocks, AI employees, and the more advanced template system. They open a lot of possibilities.
However, in real production scenarios, I often find myself facing the same paradox you described.
Some very basic features that were extremely simple in the Classic (1.x) pages have become surprisingly complicated — or are simply not available yet — in Modern Pages. For example, something as simple as aligning a column to the left or right in a table could be done very easily in Classic. In Modern Pages, achieving the same result often requires custom JS, block customization, or workarounds that feel unnecessary for such a fundamental UI need.
This creates friction in daily development. We want to adopt the new architecture and benefit from the new power, but we still depend on those “basic” capabilities to build stable, production-ready systems efficiently.
I fully support the direction of 2.0, but I also hope the team prioritizes bringing feature parity for core block functionality. Once the basics are as solid and flexible as in Classic, Modern Pages will truly unlock their full potential.
Thanks for raising this discussion — I believe many of us share the same experience.