←back to thread

263 points bigmicro | 2 comments | | HN request time: 1.484s | source

Hello HN community,

This is bootstrapped/indie hacker-ish. Would appreciate feedback.

What it is: You create a link (e.g. onair/yourname), and anyone can call you from it. Caller uses a web browser to make the call (not dedicated app). You can create as many links as you want, and can direct calls to colleagues in a round-robin or escalation manner.

In a way, it's like the "opposite of Calendly"; whereas Calendly is about meetings in the future, OnAir is about immediate meetings.

Motivation behind it: One of our SaaS products was struggling to grow. We believed that if we provide more "hand holding" to visitors on the landing page, it will increase conversion. It's like speaking to the guy behind the counter before making a purchase. That idea/experiment, over time, became OnAir.

Feedback: Identifying the perfect use case / customer has not been easy. E-Commerce store owners, which I thought would be ideal customer profile, are not responding as expected (e.g. "why use this instead of a WhatsApp button?"). The value of branded links, round-robin, recording/transcription, lead capture, etc does not seem to matter much to them. Ideas are welcome.

Show context
cess11 ◴[] No.42148904[source]
Is it built with Ruby? Looks like the landing and login page are.

Should probably consider moving to Elixir, if that's not what you're using on the server already.

replies(1): >>42150995 #
1. mfkp ◴[] No.42150995[source]
What's wrong with ruby in this case? Ruby in 2024 can easily handle an app like this.
replies(1): >>42156314 #
2. cess11 ◴[] No.42156314[source]
Let's flip the question. What is it that Ruby does better than Elixir for this domain?

I can't think of anything. One could argue that Ruby might have a larger package repo to pull in dependencies from, but this being a telecom adjacent domain you'll find that Elixir and OTP solves some tricky problems rather well that mainly object oriented languages tend to struggle with.

You'd also get out of having to skip between your application language and Golang down in Livekit, since the Membrane folks have built a standalone WebRTC platform: https://github.com/elixir-webrtc

In production Ruby code bases also tends to degrade over time. The team will sometimes find itself under duress and push magic tricks that Ruby allows to prod. Perhaps it's a matter of taste or whatever, but I've found most of the Rails applications I've come across somewhat hard to learn and debug. Similar to annotation driven applications in Java things can get really weird and brittle. These things are harder to accomplish in Elixir, which also seems to get a rather clever gradual typing system.