Disclosure: I maintain Polhem, an open-source (MIT) framework, and I'm using it as the example here. It isn't a tool for non-developers. Setting up the project and the server needs a developer, so this is more for people who end up handing a no-code project over to one.
A pattern I see a lot: a tool takes you most of the way, then you hit one rule, report or integration it can't do. The options are workarounds, or rebuilding in code, and in a rebuild almost nothing you set up in the tool carries over.
The approach I've been working on keeps the no-code part as data that the coded system reads. Each form is described once in an Excel workbook, one row per field: the type, the length, a drop-down, which other form it links to, a formula, plus a sheet of rules that block saving. Import the workbooks and the app runs, with the tables, screens, lookups, computed amounts and save rules all derived from them. When requirements change, you change the description and the app follows.
When one form needs something the description can't express, a developer writes code for that form only. The rest of the forms stay as descriptions, so the handoff happens form by form instead of all at once.
The costs: you need a developer from the start, reports and batch jobs are written by hand, and it fits business apps with lots of similar forms (orders, customers, inventory). It's not for landing pages or consumer apps.
Highlights (3 min): https://youtu.be/OAlAgAuGdKE
Full walkthrough (10 min): https://youtu.be/5WjUTwoPyGw