[mcdonje]

I've been in some really bad situations related to low-code products.

A. If the product isn't powerful enough, then users can't easily handle situations outside of the normal workflow or quickly change processes to accommodate business needs.

B. If the product is too powerful, then you need someone technical to work on it. And no technical person wants to work on it. Code is easier to write and more powerful than some convoluted SaaS low-code product.

The reason excel is the most popular low-code solution is because it's turing complete and non-technical people can do the bare minimum with it.

Any solution that isn't turing complete is going to run into problem A. Any solution that is turing complete, including excel, is going to run into problem B.

The best thing you can do is solve for A as much as possible, and let technical people under the hood as much as possible to solve for B. Don't try to force technical people to use the problem A workflow.

[mr_o47]

+1 on the excel

It's a very popular tool and plus its almost available in every organization and there's so much you can do much with excel that it literally blows my mind.

For example I read about a Japanese artist who used excel to create paintings