A framework for evaluating no-code platforms on three criteria: whether it can express logic like variables and loops without code, whether it has pre-built components for common services, and whether you can inject custom code when the no-code tools fall short.
Chapters
I find there are 3 keys to no-code, low-code feature set. The first is no-code completeness. How much can you do? How much intent can you express using the no-code interface? And it's particularly important for things like variable assignment, changing control flow, looping, etc. The second is high-level Legos. How easy they make it to interact with the services or resources I care the most about without having to go down and, you know, have to reconstruct all the primitives myself. And the third is, is there an escape hatch to be able to bring in, you know, just the right amount of, you know, code probably in the form of JavaScript or Python or whatever, so that I can either fill a gap or do the very special thing that I want the app to do while the no-code and the Legos are taking care of the, you know, more implementation concerns. When I have all three of those, I've got a really powerful system. And I think you can evaluate a lot of no-code platforms using that framework.