[fabianholzer]

Vendor lock-in and business continuity would be my top concerns from a high-level perspective.

And as a developer I would be less than excited to take over the maintenance of low-code based applications, because well to a high-code person such usually web-app/saas based proprietary dev environments feel like a straitjacket. And anyways you'll likely be asked to jump in when the limits are reached and all extension efforts are uphill battles.

If you get the handover out of the low-code tooling to a "standard" development tooling (meaning something text-based in a non-proprietary programming language that I can edit in a IDE of my choice and have under proper version control) smooth, I'd be listening.

[Aaikansh22]

Vendor lock-in and the need for smooth maintenance are definitely high-priority concerns.

Speaking of solutions, that's where low code/no code comes into play. It's designed to break down those barriers and offer flexibility. With the right platform, you can avoid being boxed in by proprietary environments and have the freedom to transition quickly when needed.