I use it for simple unambitious systems in room escapes and similar, in situations where you want to be able to monitor the state of a system and make changes on the fly. The low code framework adds lots of debugging, monitoring, and logging hooks.
The system is very explicitly not meant to ever support any real programming.
You can't even create reusable functions, there's just IFTT style rules and Excel inspired =expressions.
Anything beyond that, Python already does, and I don't wanna design a new DIY general language.
I think low-code has a lot of potential, as a way to connect pieces of existing code. Things like VVVV and Excel are really nice.
But when it tries to be as general as code, it has to be careful not to just become.... code. I'll choose the common well known language over the "just right" special purpose language every time.
To me, Excel is the premier example of low-code success. It covers it's range of use cases very well with just a few high level primitives.
The interesting part isn't exactly the language although the way that they have a fairly standard and compatible batteries-included library is nice, it's the premade structure and tools optimized to work with that structure.
It's real "software" not a pure diy software kit.