Liso

Highlight text on any page and turn it into audio.

Productivity

Books

Audio

Visit WebsiteSee on Product Hunt

Turning highlighted text into audio is a nice fit for newsletters and long reads. How does Liso handle inline code, tables, or footnotes in an article? Those usually either get read out literally or dropped, which breaks the flow fast.

I personally will not use this because I do not wear airpods or headphones when I work. BUT when I saw the description, I was IMPRESSED! This is super cool! I would use this if was more conversational. Like if i asked something about the page and it responded.

the highlight-to-audio idea is clean but I'd worry about the TTS quality on the actual highlighted snippets - people usually highlight the dense, jargon-heavy sentence, not the easy one. does the voice engine handle stuff like code terms, acronyms, or a string of numbers/stats gracefully, or does it start mispronouncing things once the text gets technical?

Congrats on the launch @evgeny_timofeev , happy that we are launching in the same day as you!

Question: have you thought if Liso can be used for accessibility?

the read-later graveyard bit hit close to home, mine is mostly long threads I bookmark and never open. question that hasn't come up - what happens with non-English content? if I highlight a French or Japanese article, does it detect the language and switch voice/pronunciation automatically, or does everything get read in one fixed voice/language regardless of the source text

@evgeny_timofeev Congratulations!! Products like this usually come from a personal frustration. Curious, Was there a moment where you thought like, "I wish I could just listen to this instead of reading it," and decided to build Liso?

Turning highlighted text into audio on the fly is such a natural extension of how people already read online. Does it work across any website, or are there certain page structures/paywalls that trip it up?

Audio removes the lag of sitting down to read, which is usually what kills the backlog. That makes this interesting.

How do you handle content that relies heavily on visuals or formatting to communicate meaning, tables, charts, heavily structured docs. That is where most text-to-audio tools lose fidelity. Is Liso doing anything different there?

This is such a relatable idea. My saved reading list keeps growing, but I would happily listen to many of those articles while walking or doing chores. Turning selected content into a personal audio queue feels much more intentional than relying on a generic podcast feed.

Congrats on the launch! I like that you're focused on a very specific workflow instead of trying to be another generic text to speech app. Turning articles and newsletters into an audio queue is great for people trying to stay ahead of industry news and research. Curious what surprised you most after people started using it. Was there a use case that emerged that you didn't originally design for?

The thing rotting in my saved for later pile is a long technical deep dive on RAG architecture I bookmarked months ago and have opened maybe twice. It is exactly the kind of dense, code heavy writeup that never survives the jump from eyes to ears well, since it leans on diagrams and inline snippets that don't translate to audio. So my honest answer to your own question is Liso probably would not have saved that one specifically, but it would have saved the surrounding context and explanation, which is most of what I actually needed anyway. On the actual product, my real concern is anything code heavy or with tables and diagrams. A lot of what ends up in a reading pile is technical writing, not narrative prose, and text to speech tends to either skip that content awkwardly or read it in a way that makes it meaningless out loud. How does Liso handle a highlighted article that has inline code blocks or a table in the middle of it, does it narrate around them, skip them, or attempt to read them as if they were plain sentences.