New to apps and AI builders? What an app is made of, the steps engineers follow to build one, and three questions to ask your AI builder.
When I started looking into how apps get built, every conversation seemed to be in a language I hadn’t learned. Frontend. Backend. Deploy. Row-level security. People nodded along, and I nodded too.
So before this series goes any further, I want to go back to the start. This is the post I wish I’d read first: what an app is actually made of, the steps engineers follow to build one, and where AI builders fit in.
If you already know all this, skip ahead. If you don’t, you’re exactly who it’s for.
The easiest way I’ve found to picture an app is one you’ve almost certainly used: a food delivery app.
Here’s the lesson that took me longest to understand. The real checks have to happen on the company’s computers, not on your phone. Imagine the app worked out your total on your phone and simply told the server “this person owes $2”. Anyone who changed that number on their own phone would eat for almost nothing. A well-built app re-checks the price, the discount and the payment on the server, where customers can’t reach.
The same goes for who can see what. Hiding a button on the screen is like a “staff only” sign on a door with no lock. It stops polite people, and only polite people. The real check, “is this person allowed to do this?”, has to happen on the server.
Most of the data leaks I’ve read about this year seem to come back to this one idea. The records were left open, or the only check was on the screen.
Engineers don’t just write code. Building a good app takes a whole routine around the coding, and that routine has a name: the software development life cycle. Here it is as I understand it so far, using the delivery app as the example:
At every one of those steps, engineers ask three questions:
I wanted to know whether this routine is a real standard or just good habits people talk about. It turns out governments write it down.
In February 2022, the US National Institute of Standards and Technology (NIST) published its Secure Software Development Framework. It’s a guide to building software safely. It groups the work into four areas: preparing the team, protecting the software, producing well-secured software, and responding when problems are found. (NIST SP 800-218)
What caught my eye was the reason NIST gives for writing it: few software development processes cover security in detail, so these practices usually need to be added. (NIST)
In other words, even for professional teams, security doesn’t come built in. Someone has to add it on purpose. That’s worth remembering when we get to AI builders.
An AI app builder, like Lovable, Replit, Bolt or Cursor, squeezes most of that routine into a single conversation. You describe the app you want, and a few minutes later you can tap through it. It made the plan, wrote the code and put it online for you.
That speed is genuinely amazing, and it’s why so many people who’d never have built software are building it now. I’m one of them.
The question this series asks is simpler than it sounds: when the builder does all of that in one go, which steps does it actually do, and which does it skip unless someone asks? I have a hunch, but I’m going to check rather than assume. Each post takes one step, learns what engineers do, watches what the AI does, and tests a guardrail that makes it do the step properly.
You can start checking your own app today. Ask your AI builder these three questions, in plain words:
You don’t need to understand every word of the answer. Look for one thing: does it name specific places, or does it stay vague? “Every request to the orders table is checked on the server against the signed-in user” is a real answer. “Your app is secure and follows best practices” isn’t one.
If the answers worry you, that’s useful, not scary. It tells you which step to look at first, and that’s what the rest of this series is for.
Next in this series: a plain-English glossary. All the words from this post and more, kept as a page you can come back to and growing with every post.
If there’s a word you keep hearing and never quite understood, tell me and I’ll add it. Email me at [email protected].
And if this felt like a lot: it felt like a lot to me too. That’s why I’m writing it down one step at a time.
One short email a month: what’s new at Verilay, one thing to check in your AI-built app (with a ready-to-paste prompt), and the AI security news worth knowing. No spam, and you can unsubscribe from any issue.