You built something with an AI tool. It looked finished. You clicked around for a while, felt good about it, and sent the link to someone who actually needed it. Then they messaged back confused, because the thing they were looking at was not real.
This happens constantly and it is not really a coding mistake. It is a looking mistake.
Looks connected is not the same as is connected
AI builders are very good at one specific trick: making an empty screen look full. Sample names, sample dates, a calendar that already has bookings on it, a dashboard with numbers already in the boxes. None of that proves anything is wired up. It proves the builder did not want you to stare at a blank page.
You cannot tell the difference by looking at it. That is the whole problem. A screen full of realistic-looking data and a screen full of real data render exactly the same to your eyes. The only way to know which one you have is to test it, not admire it.
Three checks that take about a minute, no code required
1. The write test. Add one real thing through your own app. A booking, a record, whatever the app is for. Then hard refresh the page. If what you added is gone, it never reached a database. It was living in the browser tab and nowhere else. Sample rows that were already there will survive a refresh too, which is why this check is not enough on its own, pair it with the next one.
2. Unplug it on purpose. Find the setting for your database connection or your API key and break it. Rename a table, revoke a key, whatever is easiest. Then load the page again. A real connection fails loudly and immediately, usually with an error or a blank spot. If the page still looks completely fine with the backend broken, nothing was ever actually talking to it.
3. Watch the network tab for ten seconds. Open your browser's developer tools, click the Network tab, then load the page. Real data means a request goes out to fetch it, you will see it appear in the list. No request means those rows were baked into the page itself, not pulled from anywhere.
Empty is honest
Here is the instinct worth building: a brand new app, one you have not entered anything into yet, should look bare. An empty calendar. Zero bookings. A dashboard with nothing on it. If a fresh app looks full before you have put anything into it, ask where that fullness is coming from. It did not come from you.
This is also why the person who finds these bugs first is almost never the one who built the app. You have been staring at the demo, admiring what it can do. The first real user is not admiring anything, they are trying to actually use it, and they touch the one path that was never really connected within minutes. That is not bad luck. That is the difference between testing as the builder and testing as the customer, and only one of those two ever finds the real bugs.
If you already shipped something and are not sure
Run the three checks above on it today, before anyone else does. It takes less time to run them than it took to read this.
If you run them and something is wrong and you are not sure how to fix it, that is a normal place to end up, not a sign you did something wrong. We do free diagnoses for exactly this: send us the app, we look at what is actually happening under the surface, and tell you straight whether it is a five minute fix or something bigger. No pitch, no obligation. rescue.ticassociation.com
Top comments (0)