VoIP users face confusing setup and clunky calling interfaces
People using VoIP—including parents who want an easy calling experience and people configuring their own service—run into frustrating interfaces and protocol-heavy setup. Requests for browser-based self-hosting and RCS support are adjacent interoperability needs, but they are harder to solve in a single MVP. A standalone client can simplify calling and onboarding, but it cannot make providers support RCS.
For voIP users and nontechnical callers. Mentioned from May 2024 to Apr 2026 on Hacker News and Stack Exchange.
4 different people described this problem in 4 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 5.0/10
- Momentum
- 5.0/10
- Who pays
- Consumers
- Competition
- Medium
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
The value is in the app for the parents. I would pay $10 not to deal with shitty VoIP interfaces
The only knock on using voip.ms is the initial setup is a little tedious and you need to understand the basics of how they are working with each part of the VOIP protocol
abctx on Hacker NewsOct 2024
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks