- role-based rules about views, edit rights, etc
- workflow where items flow from one role to another
- less "code" for things like dependent drop-downs...where one field drives the drop-down choices in another field. Excel can do this, but with fairly complex macros
On that last one, I imagine there's more examples where Excel stops being "low code" because you're using complex macros. It's more flexible, but that's the tradeoff.
I guess my point is alot of people outside of software development the goto for low/no code is excel
- Allow significant/good multi-user access
- Change control
- Less fragility
- Allow editing large datasets (e.g. stored in Postgres) in a controlled way
- UI elements without diving into VBA code (once you are in VBA then anything is fair game obviously)
- Easily connect to external API's and integrate with other internal systems (again without VBA)
Assume other low/no code tools are similar.
And with the difficulty going up, the likelihood that you'll do this when it's needed and makes sense to do goes down. I can't tell you how many times I said "I need a website" and didn't end up posting one, because we didn't have a ready answer to this question, and nobody could be bothered to go out and build one.
Just a simple one page website. I can think of at least three "easy" ways to do it (and that's my whole problem in a nutshell, thanks for coming to my TED talk.)
The user specification requires those tools to interact with the website, without technical help, in perpetuity. That's a MONSTER requirement.