There's Still Fake Demo Data and Lorem Ipsum in My App, Does It Matter for Launch?
5 min read
Yes, clean it up before real users see it. Leftover Lorem Ipsum, "John Doe" sample names, and fake demo rows are the fastest way to tell a first-time visitor that your app is half-built, and they will not stay to find out otherwise. The good news is that placeholder content is easy to find once you know where to look.
Why this happens
When you and an AI agent build a screen, you need something on it to see if the layout works. So the agent fills the space with the standard filler: a paragraph of Lorem Ipsum, a testimonial from "Jane Smith," three fake products, a dashboard seeded with invented numbers. That is completely normal during building. It only becomes a problem because nobody circles back to remove it.
The agent built exactly what you asked for, which was "a working screen." You never asked it to strip the scaffolding out again, so it stayed. The filler is invisible to you now because you have seen it a hundred times and your eye slides right past it. A brand-new user sees nothing else.
How to check
Search your whole codebase for the usual suspects. From your project folder:
grep -ri "lorem ipsum" .
grep -ri "john doe\|jane doe\|jane smith\|test user" .
grep -ri "placeholder\|example.com\|l/dummy\|sample" .
grep -ri "TODO\|FIXME\|change me\|your text here" .
Then click through the app with fresh eyes as if you have never seen it:
- Open every page while signed out, and again as a brand-new signed-up user.
- Read the empty states, tooltips, email templates, and error messages, not just the headline copy. Filler hides in the corners.
- Check the data itself. A dashboard or list seeded with demo rows will show your invented records to a real user unless you clear the table.
The fix
- Replace the real copy. Every heading, button, and paragraph should say the true thing, even if it is short. "Add your first project" beats a paragraph of Latin.
- Remove seeded demo rows from the database. Delete the sample records from your Supabase or Firebase tables so a new user starts genuinely empty. If you have a seed script, stop it running against production.
- Fix placeholder images and avatars. Swap grey boxes and stock "user 1" faces for real assets or a clean default state.
- Update the transactional emails. Welcome and reset emails often still say
"Your Company" or point at
example.com. Send yourself one and read it. - Re-run the greps above until they come back empty, then walk the app one more time as a new user to confirm.
The trap to avoid
Do not just delete the visible filler and leave real empty screens behind. A page that showed three fake products and now shows nothing at all looks broken, not finished. Every place that used to hold demo content needs a proper empty state that tells the new user what to do next. Removing the placeholder and designing the "nothing here yet" moment are the same job.
Where this fits
Placeholder content is a trust problem, not a bug, which is why it survives right up to launch: nothing crashes, so nothing flags it. The free Readiness Report walks your real app the way a first user would and points out the filler, dead ends, and empty screens you have stopped noticing. While you are in there, it is worth checking for buttons and links that go nowhere, another thing that quietly signals "unfinished." When you want the whole list fixed in order rather than found, that is what the Finishing Pass is for.