No-code platforms bundle building tools with hosting but hide what's happening inside. When things break, support teams and users are blindsided. The speaker argues observability matters most when moving from prototype to production, not at launch.
Observability is the next key feature in no-code. I've now run into a bunch of these no-code systems where their model is they're going to be SaaS and have a subscription because they're providing you with a hosting service, which means not only providing software to build with, but they're also providing you with infrastructure. The trick is they usually aren't providing that much the way that you will see how that infrastructure is working, particularly your piece of that infrastructure. This creates all sorts of challenges in terms of you getting surprised when something is going a bit wrong. That observability should at the very least be clear to the customer support personnel and ideally directly to the customer. How much is of resources getting used? Where are the limits? Where are things going down? Where are the performance benefits? This is not something you necessarily need to have on day one when you're offering the service, but as people start to shift from initially doing prototyping to starting to put production things in place, this is going to be key to your long-term success.
