Yesterday a solo builder dropped an app that turns almost anything into a podcast episode. Web pages, Substack posts, PDFs, even a photo of a page from a physical book. No editing, no fuss, just point at text and listen.
The creator, a Redditor who goes by OneMoreSuperUser, spent the past few months building it and shipped it to r/PromptEngineering this week. The app is called Frateca. It’s built on React Native for mobile, with a NodeJS and React web version already live, and a Framer landing page tying it together.
Here’s the twist: it asks for zero permissions by default. Most apps that touch your files, your camera, or your storage ask for everything up front. This one stays quiet until the moment you actually choose to share a file for conversion. That single design choice says more about the builder’s priorities than any feature list could.
And the feature list is genuinely worth a look:
- Converts webpages, Substack links, and Medium links straight into audio
- Reads PDFs and plain copied text out loud
- Snaps a photo of any printed page and extracts the text through OCR before narrating it
- Plays in the background, so it works like a podcast or audiobook while your screen is off
- Runs on iPhone, Android, and now in any browser through the web version
Why does this matter? Most of us have a graveyard of tabs we never finish. Long Substack essays, saved Medium reads, PDF reports from work that sit in a folder collecting digital dust. Turning that pile into something you can listen to on a walk, a commute, or while doing dishes changes whether you actually get through it.
A few commenters compared it to NotebookLM, and that’s fair as a reference point, but the two solve different problems. NotebookLM builds a research assistant around your documents: summaries, chat, cross-referencing multiple sources. Frateca skips all of that. It’s not trying to be a research tool. It’s a straight line from “I have text” to “I’m listening to it,” and that simplicity is the actual selling point for anyone who just wants their reading list read to them.
Here’s the mini-workflow if you want to try it this week:
- 📄 Paste a link (Substack, Medium, any webpage), upload a PDF, or drop in copied text
- 📸 Or snap a photo of a printed page and let OCR pull the words out
- 🎧 Hit convert and get clear, natural-sounding narration back
- 🔊 Play it in the background like a podcast, headphones in, screen off, and go about your day
Pro tip: this is built for your backlog, not your inbox. Load up the articles you keep meaning to read and never do, then burn through three or four of them on your next walk. That’s the actual use case, turning “read later” into “already listened.”
Second pro tip, specifically for the photo feature: good lighting and a flat page beat a rushed phone camera every time. OCR mistakes show up as mispronounced or garbled words in the final audio, so a clean, well-lit photo saves you from weird stumbles mid-listen.
Now for the caveats, because the comments raised real ones. A few readers, including RadioactiveMurukku and Euphoric-Way-1899, asked which text-to-speech engine actually powers the voices. That detail wasn’t in the original post, and it’s the single biggest factor in whether narration sounds natural or robotic. Worth asking before you commit to a daily habit with it.
shaggyhun86 also flagged something practical: the difference between the free tier and the premium tier isn’t spelled out anywhere. No word on daily conversion limits, voice options, or what’s actually gated. If you’re the type who hits a paywall mid-article and gets annoyed, check that before you build a routine around it.
On the upside, betterengland’s early read lines up with what the feature list promises: onboarding is smooth, navigation feels intuitive, and if you hate reading but love listening (a surprisingly common combination), this fills a real gap that most audio apps don’t cover.
The web version is the easiest way to kick the tires without committing to an install. Drop a link in from your desktop browser and see how the narration sounds on something you were already planning to read. If it clicks, grab the mobile app for the background-play trick on your next commute.
Worth checking the original Reddit thread too. The builder’s been answering questions in real time, and the TTS engine and pricing details will likely get clearer as more people ask. 🚀
Frequently Asked Questions
Q: What text-to-speech engine does Frateca use?
It’s Kokoro. You can tell from the voice names in the app. Users who’ve tested it think it sounds natural and clear, which is why the developer chose it. Solid technical choice.
Q: What kinds of text can I convert to audio?
Pretty much anything: PDFs, web articles (Substack, Medium, blogs), copied text, and even photos of text. So if you have a book page, just snap a photo and it’ll extract and read it aloud. Works for whatever text you throw at it.
Q: Is it really private?
Yeah. It doesn’t ask for permissions by default. It only asks if you choose to share files from your device. No forced access just to use the app. It’s actually designed with privacy as a priority.
Q: Is there a web version?
Yes, it’s already live at app.frateca.com. Works in any browser on desktop or mobile, so you can try it out before downloading the app if you want. No install needed if you just want to test it.
I built an app that converts any text into high-quality audio. It works with PDFs, blog posts, Substack and Medium links, and even photos of text.
by u/OneMoreSuperUser in PromptEngineering