Most low-code platforms force developers to manually code security restrictions, a tedious task many skip. The speaker argues platforms should instead build in automatic permission controls that grant temporary, step-specific access and then revoke it, eliminating custom security work for every app.
If you use the right platform, a lot of those things that people that dabble in creating applications hate to do, they get done automatically anyway. They get handled by the platform so that each application doesn't have to be responsible for it. I'll give you a perfect example, security. Security is unpleasant to most people. Security is usually in the business of no. Security in an application, most low-code tools in particular, start off with the point of view that everybody's allowed to do everything. Then if you remember, at some point you need to build logic into your application to take away the privileges from people that you don't want them to have. Doesn't have to be that way. You could use a platform that is based on need-to-know or need-to-do and only awards the necessary permissions during a given step in a process to the right person for the length of that step and then withdraws them gracefully. But most application platforms, low-code or high-code, don't do that. But asking citizen developers to deal with that, It's not going to happen. Even professional developers hate getting involved in that. But if the platform provides a common agreed-upon approach to security that you can reuse over and over again, now you got something.
