Developer launches interactive AI history-podcast product
A developer introduced an AI history-podcast product that turns a topic, period, or person into a two-host narrated story with synchronized artwork. According to the developer, users can interrupt playback to ask questions, access memory of previous episodes, take an optional quiz, and inspect episode sources and subtitle tags. The product reportedly searches the web, prioritizes reference-grade material, and directs hosts to disclose conflicting historical accounts.
The launch demonstrates how multiple models can be combined into an interactive, source-aware audio experience, although the product’s capabilities and model comparisons remain based on the developer’s own presentation.
| History is something I’m quite passionate about and at work I have experience with software development and LLMs. So I thought how can I bring these things together and built something that I would actually use. This is the results of many months of hard work! You type any topic, moment or person. About a minute later, two hosts are telling you the story with artwork that follows along. You can interrupt mid-episode with a question; they answer and pick the story back up. They also remember what you’ve listened to in the past and can refer to it. At the end there’s also a optional quiz to test what you learned! Quite a lot of emphasis was put into the research part. It searches the web and gathers notes on the topic, prioritizing reference-grade sources (encyclopedias, museums, archives, academic pages) over blogs and also searches in the language of the place or person, so a story about Japan or Peru isn’t told only from English sources. When the sources disagree, which in history is constantly, the hosts say so instead of quietly picking a side. Every episode links the pages it used and tags the subtitles. Under the hood it’s not one model. A single episode is about a dozen calls, each pinned to the model that won its bake-off: research, writing, artwork, voices, sources, quiz, etc... Finding the right balance between quality, speed and cost was where a lot of the work went. The Claude part: Claude Code did roughly 80% of the development, the front end came out of Claude Design. I steer the idea and the design, it codes, I review, and we go back and forth even on small features. Review is where the time goes For the models inside the app, I ran bake-offs across GPT, Claude and Gemini for each job, and a few things surprised me: Mainly looking for feedback on the idea and how to make it better! Happy to answer any questions! You can try it here: historai.ca submitted by /u/Goldenchild123 [link] [comments] |
#Claude Code#Claude Design#Claude Opus 4.8#Claude Opus 5.5#Claude#GPT#Gemini