ince 2015, the terms “no-code” and “low-code” have become more common, but I think of them as buzzwords that simply indicate higher-level abstraction layers for building software.
As developers, we’re used to working on different layers of abstraction. “Operating systems are abstractions on top of bits and bytes, programming languages are abstractions on top of operating systems, and libraries are abstraction layers on top of programming languages,” Nick Selman of [Draftbit told me. Low-code tools are essentially another layer, so while they might rely more heavily on [WYSIWYGthan code, they can serve you well when you know how to use them.
Let’s look at a few use cases for low-code tools and some examples of how different kinds of organizations are using them.
Let’s look at a few use cases for low-code tools and some examples of how different kinds of organizations are using them.
Prototyping
“When you are bringing a new product or concept to market, it is important to realize you will be layering in a lot of bets. Leveraging no-code or low-code platforms allows you to stand up products with more fidelity than a clickable prototype and a fraction of the cost of building an app, and it allows you to quickly test features, flows, and value propositions.”