Deep Frustration with NocoBase – Overcomplicated, Unintuitive, and Not Production-Ready

After spending a significant amount of time working with NocoBase in real-world scenarios, I feel compelled to give brutally honest feedback:

I am extremely disappointed.

NocoBase markets itself as a low-code platform meant to simplify development. In reality, it does the exact opposite. Basic, everyday use cases are turned into unnecessarily complex, fragmented, and frustrating workflows.

Here are the core issues:

  • Simple things are absurdly complicated: Tasks like prefilling data, querying from another table, or passing parameters between forms — things that should take minutes — become hours of trial-and-error with unclear logic.
  • Terrible developer experience: The system lacks consistency. Logic is scattered across multiple layers (UI, actions, workflows, fields), making it extremely difficult to understand, maintain, or debug.
  • Debugging is a nightmare: Error messages are vague or completely useless. When something breaks, you’re left guessing. There is no clear visibility into what’s actually happening under the hood.
  • Mobile experience is unacceptable: The UI is poorly optimized for mobile. Layouts break, interactions feel clunky, and performance is slow. This alone makes it unsuitable for many real-world use cases.
  • Documentation is misleading and impractical: Many examples either don’t work or lack real-world applicability. Instead of guiding users, it forces them to reverse-engineer the system.
  • Over-engineered for no reason: Instead of simplifying workflows, NocoBase introduces unnecessary abstraction layers that complicate even the most basic operations.
  • Poor UX design overall: Too many clicks, too many steps, too much friction. Nothing feels intuitive. It feels like the system was built without considering actual end users.
  • Performance issues: As soon as data grows or workflows become slightly complex, the system starts to slow down noticeably.
  • Lack of clear best practices: There is no clear “right way” to build things, which leads to inconsistent implementations and wasted time.
  • Feels unfinished: Many features feel half-baked, as if they were released without being fully thought through or tested in real scenarios.

To be blunt: this is not what a low-code platform should feel like.

Instead of accelerating development, NocoBase slows it down. Instead of reducing complexity, it amplifies it. Instead of empowering developers, it frustrates them.

If these fundamental issues are not addressed — especially simplicity, mobile experience, and debugging — it will be very difficult to justify using NocoBase in any serious production environment.

This is harsh feedback, but it reflects a real experience. I strongly urge the team to rethink the core product philosophy, not just patch surface-level issues.

Obviously, this depends entirely on your use cases. For me, it’s meeting all of my demands and when it comes short, I’m able to customize in ways I never could with other platforms I’ve tried. Frankly, the capabilities you get (for free) with the opensource self hosted approach are incredible.

I think the biggest challenge with Nocobase is the smaller user community size relative to other larger more established platforms. As this community grows, so will the capabilities and the ability (financially) for Nocobase to accelerate updates and new feature releases.

I’m a little frustrated with the slow roll-out of features (available in the classic version) to the new 2.0 version. Nocobase 2.0 is not ready for prime time yet.

Anyway, I share your frustrations but encourage you to keep trying. It’s been worth it for me so far.

I’m with you on this. I understand I’m dealing with free software and I’m thankful for the developers, but there is too much complexity with making simple changes. I’m putting together my list of feedback items and I’m going to look for something else. I don’t want to deal with the number of steps required for simple changes in my collections.