Use case B44 · Business
Have AI record a 30-second screen-share demo of something you built, with the private details hidden
- Marketing
- Advanced
- Playwright, X
- I use this · X post
The short version
What I do
I was building several apps in parallel and it got hard to keep up, so I built Ledger City: one factory per app, with live status from Notion and GitHub. To show it on X, I had AI record a 30-second video of it on my always-on Mac. There were two takes of the same run: a full one and a screen-share version. The screen-share version hides pull request titles, commit messages, branch names and next-step text, and still shows pull request numbers, check and deploy status and product stage. I picked the screen-share take and posted it on October 13.
What it gets me
I got a short, real demo for a post without screen-recording it myself or blurring things by hand. Because the hiding is built into the screen, I could share the actual app instead of a mockup.
Prompt
I want a short screen-share demo of an app I built. It runs at [local address], and the screens to show in order are [list]. Use [demo dataset or screen-share mode]. The recording length is [30 seconds], size is [1600x1000], and output folder is [folder].
1. Write and run a browser-recording script for that path. Before recording, hide [private names, titles, messages and other details] while keeping [approved numbers and status] visible.
2. Save the video and one still frame for the poster.
3. Review the recording for private text, including tooltips and tab titles. List any timestamps that need my inspection.Give a short plain-English summary of what was recorded and what you couldn’t check. Don’t claim the video is clear of private text without review. Don’t upload or post it.
Do it yourself
These are suggested steps for you, not a copy of my exact setup.
What you need
- Your app running on your computer with demo or fake data.
- An AI coding agent that can write and run a browser-recording script with a tool like Playwright.
- A screen recorder as a backup.
Start simple
- Load your app with fake data only. Make up the customers and numbers.
- Write down the three or four screens you want to show and in what order.
- Ask the coding agent to write a recording script for that path and run it.
- Watch the video frame by frame for anything private before you post.
Take it further
- Add a screen-share mode to your app that hides names and free text, so every demo is safe by default.
- Record two takes, full and screen-share, and choose after you watch both.
- Keep the recording script in the repo so you can re-record after the app changes.
Check your work
- Pause on every frame. Private text hides in tooltips, tab titles and notifications.
- Check that “simulated” or demo data in the video is labeled as such if your post describes it.
- Strip location and device metadata from the file before uploading.
I use this. My own setup. I use it in my own work. Prompt adapted for this library, inspired by the case. Business size: One-person firm. Results are quoted as the source claimed them and never improved. Spot an error or a broken link? Email charlie@cbarmorecpa.com.