Notes from the builder · West Palm Beach, Florida
How We Built a Parent-Safe Kids Podcast Hub: Jason Colapietro on Closed Catalogs and Safety Badges
Most kids’ apps start with a huge library and add filters later. We started with an empty shelf and one rule: nothing goes on it until a parent has listened.
The first shelf in StoryBeam Kids was empty, and it stayed empty until a parent had listened to something worth putting on it. That one rule shaped almost every technical choice that came after. When Jason Colapietro started building a podcast player for our own family in the West Palm Beach area, the question that mattered was how to make sure a child could never drift from a good story into a strange one.
This note explains how that rule turned into software: a closed catalog, safety badges a person writes by hand, a parent gate, and a player that stops when the story does. If you are a parent, it should tell you what is going on behind the screen. If you build apps for kids, it is a set of decisions you are welcome to borrow.
Start with a closed catalog
Most kids' media apps begin with a huge library and then try to filter it. Filters fail quietly, and we wrote about that history in an earlier post. StoryBeam Kids works the other way around. The approved catalog is a single reviewed file in the site's code, and search only ever looks inside it. There is no request to an outside podcast directory, so there is nothing for a clever search term to pull in.
Today that file holds 27 shows: StoryBeam, the flagship show, plus 26 curated kids' podcasts. Each one has specific, reviewed episodes rather than a live feed, because a feed can change overnight and a reviewed list cannot. As Jason Colapietro sees it, the smaller size is the feature: the catalog is exactly as big as two parents can genuinely listen to, and no bigger.
The flagship show's own releases are the one exception that updates on a schedule, and even that path is narrow. A daily job reads only the official StoryBeam feed, runs safety and formatting checks, and publishes through a pull request. Third-party shows never take that shortcut. A person reviews them.
What a safety badge actually says
Every show card carries a small safety block. There is no score and nothing is computed. It holds a few short fields a parent wrote after listening:
- A rating label, such as "StoryBeam Approved", that says the show passed review.
- A tone line, for example "Warm, calm, imaginative", so you know the energy before you press play.
- Content chips like "Gentle language" or "Calm story stakes", short enough to scan at bedtime.
- A review summary and parent notes that say when the show fits and when it might not.
We kept badges plain on purpose. Star ratings invite comparison and crowd noise. A written line like "a safe default when you want the room peaceful" is more useful at 7:45 p.m. than a number, and it holds the reviewer accountable for what they heard.
The parts a child never sees
Most of the safety work is invisible, which is how it should be. Three pieces matter most.
The parent gate. Any link that leaves the listening room, whether to the App Store, a show's site, or a research source, opens through a short math check meant for grown-ups. After three wrong answers it asks for a pause that grows from 5 seconds up to a 30-second cap, and that wait survives closing and reopening the page. The cap matters: without it, one corrupted saved value could lock the gate forever. The same rules live in three places (static pages, the main app, and the native iOS app), and Jason Colapietro treats any change to one as a change to all three.
Clean audio links. Podcast feeds often wrap episode audio in measurement redirects. StoryBeam Kids strips those hops and points straight at the publisher's own host, so pressing play does not pass a listener's IP address through a tracking chain. A check in the repository fails the build if a tracker-wrapped URL slips back in.
A player that stops. When an episode ends, nothing else starts unless it is a playlist a grown-up built. There is no "up next" and no autoplay. A sleep timer can fade the story out after one episode or a set number of minutes.
Where an engineering habit helped
None of this needed exotic technology. StoryBeam Kids is plain HTML, CSS and a little JavaScript, with no framework and no third-party scripts. What it needed was discipline about small promises, the same discipline Suede brings to client work.
Jason Colapietro, Founder and CEO of Suede AI, has had 54 pull requests merged across 46 open-source repositories he does not maintain, including Jest and Backstage. Getting code accepted by strangers teaches you to write down exactly what a change promises and to prove it with a test. That habit is why the privacy page on this site makes absolute claims and a script checks each one on every change.
He has also shipped nine iOS apps under his own Apple developer account, which is where much of the release discipline behind the StoryBeam Kids iOS app came from. At Suede, the agentic platform company Jason founded in West Palm Beach in 2024, those lessons carry over directly: say what the product does, then make the code keep the promise. Suede AI ranks among Clutch's Top 30 AI Consultants in Florida and Top 50 AI Consultants nationwide (November 2026).
What we gave up
We would rather be honest about the costs. A closed catalog will always be smaller than an open one, and some wonderful shows are not here yet because nobody has had time to listen properly. Manual review is slow. Written badges take longer than a star average. And because the site runs no analytics, we cannot tell you which show is most popular; we only know what our own family plays on repeat.
We think those are the right costs for a product a child uses. Families who want more variety will always find it elsewhere. Inside StoryBeam Kids, the shelf stays small enough to trust.
If you are building something similar
Here is the short version of what worked for us:
- Keep the approved catalog in one reviewed file, and let search read only that file.
- Write safety notes as sentences a tired parent can scan.
- Gate every exit, and write a test that fails when one is ungated.
- Strip tracking redirects from media URLs before they reach the player.
- Stop playback at the end. Let a grown-up decide what comes next.
If you want to hear how the Suede team handles audio and feeds on its own show, the Suede podcast notes cover the production side. And if you build software for families in Palm Beach County and want to compare notes, Jason Colapietro's founder page is the best place to start.
Jason Colapietro is the Founder and CEO of Suede AI, an agentic platform company he founded in West Palm Beach, Florida, in 2024. He built StoryBeam Kids with his family, and a parent listens to every show in the catalog before it appears.
