Feedback for ListenDock

Really insightful post! I've been thinking about similar challenges in my own project. The approach you're taking makes a lot of sense - would love to hear how it evolves over time. Thanks for sharing! 🙌

Interesting direction — async voice is powerful, but I’m curious about the specific use case you’re seeing traction in.

In most products, users default to text unless there’s a very clear advantage to switching to voice.

What’s the moment where users feel ‘this is better than typing’?

The core use case is clear — PDFs are painful to read, audio makes them accessible. One thing I noticed: the landing page has two competing identities. The logo says 'PDF TO MP3' but the headline says 'Listen to Your Documents' and the tagline goes further with 'Bite-Sized Audio Episodes.' For a first-time visitor it's slightly unclear whether this is a converter tool or a podcast-style learning app. Picking one and leading with it consistently would reduce the hesitation at the top of the page.

Cool project, especially the evolution from PDFTOMP3 to a broader audio platform.

A few things I noticed on the landing page:

Your headline says "Turn Documents Into Bite-Sized Audio Episodes." This describes the mechanic (converting files), but not why someone would care. Your best line is actually buried below: "Get the key insights from any document in minutes, while driving, exercising, or relaxing." That's the outcome. Lead with it.

A stronger headline: "Read less. Absorb more. Turn any document into audio you can listen to anywhere."

The difference: "turn documents into audio episodes" is a feature. "Read less, absorb more" is a benefit your visitor already wants.

Two other things:

1. Your CTAs compete with each other. "Upload file", "Drop link", "Ask", "Buy credits" all appear near the top. A first-time visitor doesn't know which one to click. One primary CTA ("Try it free") with everything else secondary would reduce the friction.

2. No social proof visible on the page. You mentioned you have users. Even one quote like "I use this every morning on my commute" with a name would make a real difference. Right now there's nothing that tells a visitor anyone else actually uses this.

Love the evolution from PDFTOMP3 to ListenDock! The pivot from pure converter to "bite-sized audio episodes" is smart.

One observation: the existing comments already nailed the positioning feedback (lavinia_negrea and ferdbons made great points about the headline).

From a technical standpoint, I'm curious about the audio quality. Are you using TTS or human narration? If TTS, which engine? The listening experience will make or break retention for this type of product.

Also, have you considered adding speed control? Some people listen at 1.5x or 2x for productivity content.

Congrats on shipping! The fact that you're iterating based on usage is the right mindset. 🚀

Happy to share feedback I’m an app tester and I focus on usability, onboarding flow, and overall user experience in apps like this. ListenDock is a great idea, especially for consuming content on the go. I’d be happy to test it and provide structured feedback on the listening flow, clarity, and any friction points if you’re open to it.

great question. for me the answer was content — specifically writing about the build process on IH. 45 posts later its my only channel with any traction. cold email got my gmail restricted. the irony.

nice execution. shipping fast is a superpower early on. my biggest regret was spending 3 weeks building an API before validating demand. you seem to be moving in the right direction. keep us posted on traction.

this is exactly the kind of honest post that makes IH valuable. most people only share wins. the struggle is where the real learning happens. what one thing would you do differently if you started over tomorrow?