WebVox

I recently launched WebVox, an open-source Android app that turns web pages into a clean reader mode and reads them aloud using Android text-to-speech.

The idea started from a pretty simple frustration: I consume a lot of long-form content on my phone, especially articles, blogs, and web novels, but most “read aloud” apps I tried felt bloated, subscription-heavy, or overloaded with AI features I did not actually need.

I mainly wanted something that could:

• open an article quickly

• remove distractions

• let me listen while commuting or walking

• continue playback with the screen off

• feel lightweight and calm to use

• auto-play next chapter without touching your phone

So I built WebVox.

What WebVox does

WebVox lets you:

• share links directly from your browser

• convert pages into a cleaner reader mode

• listen with Android’s built-in TTS engine

• control playback from notifications and lock screen

• continue where you left off later

It is designed more like a reading/listening companion than a generic TTS utility.

Why open source?

I wanted the app to be transparent and privacy-friendly.

There is no account system, no subscription, and no unnecessary tracking. Making it open source also makes it easier for people to contribute ideas, report issues, or adapt it for their own needs.

GitHub:
https://github.com/aminusia/WebVox

Current challenges

One interesting challenge is web extraction quality.

Different websites structure content differently, so building a reader experience that works consistently across many sites is harder than I initially expected. Right now, WebVox still does not perfectly remove all headers and footers automatically, although users can choose where playback starts and skip sections manually.

I am currently focusing on:

• improving article extraction

• smoother playback UX

• better reader typography

• offline caching

• accessibility improvements

Launching the app

I published the first version on Google Play recently and have been sharing it in Android and indie communities to collect feedback.

One thing I learned very quickly is that people respond much more to honest problem-solving than marketing language. Explaining why I built the app and what frustrations I had worked much better than trying to make it sound like “the future of AI reading.”

What’s next

Some ideas I want to explore:

• better automatic content cleanup

• smarter article navigation

• cross-device sync

• browser extension support

• EPUB/PDF support

• improved voice customization

If you enjoy reading/listening workflows or have thoughts about improving the experience, I would genuinely love feedback.

Google Play:
https://play.google.com/store/apps/details?id=app.alkyo.webreader