[oneplane]

Generally, no effective SDLC except for when the vendor builds a half-assed version of SCM into their product. Generally no such thing as Low-code + Git.

Most of the systems either don't have the big benefits they claim to have (time spent just flows elsewhere), or they are of limited use (think basic form workflows into a database or spreadsheet).

It's somewhat similar to a 'website builder' where yes, you can build a website, but instead of learning general tools, you're learning builder-specific tools. And instead of solving logic in logic solving tools, you're solving logic in (mostly) sub-optimal tools.

This is essentially the same problem with say Excel and Access; to use those at scale you'll still need to learn a 'variant' of programming and data modelling and it doesn't help much that it's inside of an application instead of inside of an IDE.

In this specific case, I would ask the software engineering team to find out ways to do rapid prototyping with a trade-off in UI quality; you can generally get away with the same principles as OpenAPIV3 spec based data structure and interface generators. You focus on specifying how the application should process and model data, and auto-generate all the required persistence and interface stuff from that.

[alphalima]

You've hit the nail on the head about my reservations.

Regarding your recommendation, were there any libraries that exist already?

Otherwise, I assume that you mean:

1) write some code to derive a CRUD/RPC OpenApiV3 Spec from some data-at-rest spec/JSON Schema other (e.g. RDBMS Table)

2) generate endpoints conforming to that spec and wire it to persistence

3) generate UI components that allow you to drive requests to those endpoints.

4) build something to serve backend + front-end

Those steps look like a low-code system to me?