No-code and low-code development environments remind me of ORM (Object Relational Mapping) and I suspect that the outcome of this trend will be similar. It will be seen as an anti-pattern.

ORMs tried to shield developers from having to deal with SQL directly - But the SQL was still being generated behind the scenes. What happened in most projects which used ORMs is that eventually, they started getting very slow as more advanced requirements were introduced and the SQL queries which were automatically generated behind the scenes by the ORM framework became extremely complex and inefficient... Then eventually developers had to replace all those with new handwritten SQL queries... At the end of a massive refactoring, the project often ended up with an ad-hoc mish-mash of ORM and SQL which made the code harder to maintain than if they had just exposed the database through a simple data abstraction layer which uses raw SQL to begin with.

The main difference between ORM and no-code/low-code is that instead of automatically generating SQL, it automatically generates code behind the scenes.

These kinds of tools have existed for many decades. Many IDEs such as Visual Studio, Delphi, Microsoft Access and IDEs for many different languages used to support drag-and-drop form building for desktop applications but those never got any serious traction. They just hid the complexity and problems behind the scenes and made it harder to maintain applications.