Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I want people to talk to each other inside my app

Short answer

A call feature is more than a button. Two phones often cannot connect directly, so most call setups need a relay server, and the app also needs permission to use the camera and microphone. Decide who calls whom, in what situations and with what recording rules first, then ask for a written scope.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • My customers keep asking to talk to the driver, the doctor, the tutor or the seller inside the app.
  • Right now people leave my app to use WhatsApp or a phone call, and I lose the record.
  • I want video visits or voice support, but I do not know if I should build it or buy a ready-made service.
  • A developer told me it is easy, another told me it is huge, and I cannot tell which is true.
  • I have a demo from a call library that works in the office and I am afraid of what happens in real use.

Why does this happen?

  1. Calls between two phones usually need a relay

    The WebRTC project, which most in-app calling is built on, says a direct socket between two clients is often not possible, so a server is required to relay traffic between them. The exception is clients on the same local network. A demo that works in your office can behave very differently for customers on mobile data.

  2. The relay is a server you have to run or rent

    The relay is called a TURN server, and the app has to be given its address and credentials. That makes calling a small backend feature as well as an app feature, with its own hosting, monitoring and running cost.

  3. The call is only part of the feature

    Someone has to decide who is allowed to call whom, how a call is started when the other person has the app closed, what happens when a call drops, and whether anything is recorded or stored. These are product decisions, and the build cannot start well without them.

  4. Ready-made call services and custom builds are different trade-offs

    A hosted call service is faster to add and the provider runs the relay. A custom build gives more control and more to maintain. Neither is always better, and the right choice depends on how many calls you expect and how much you need to control.

What can I do about it today?

  1. Write down who calls whomOne page: customer to staff, staff to staff, or customer to customer. Say whether it is video, voice or both, and whether it happens during a booking or at any time.
  2. Decide what happens when nobody answersA missed call, a busy line and a dropped call each need a clear outcome for the user. Note what you want to happen in each case.
  3. Decide about recording and privacySay whether you want any call stored. If the answer is yes, ask a lawyer in your country what you must tell users. I cannot give legal advice.
  4. List the phones your customers really useCheck your analytics for the main phone brands and the share of iPhone and Android users. Testing is done on those.
  5. Do not buy a call service on the first sales callAsk for the pricing model in writing and for what happens to your data if you leave. Compare two options before you commit.

When should I bring someone in?

  • You have a date by which calls must work, and nobody on your side has built one before.
  • A call prototype exists but fails for customers on mobile networks.
  • Your app handles medical, financial or other sensitive conversations.

How do I handle it?

  1. Agree the call flow on paperI write the scenarios with you: who calls, when, what the other side sees, and what happens on failure. You approve it before any code.
  2. Choose build or buy with youI compare a hosted call service with a custom relay for your expected usage and tell you the trade-offs, including what each leaves you to maintain.
  3. Build the smallest working call firstA first call between two real phones on different networks, using a relay, before any polish is added.
  4. Test on real networks and devicesCalls are tested over mobile data and Wi-Fi, with permission refusals and dropped connections, because that is where call features break.
  5. Hand over what runs itThe relay, its settings and the credentials are documented and sit in accounts your company owns.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can the app just use the phone's normal call?

It can open the phone dialler, but the call then happens outside your app and you get no record of it. In-app calling keeps the call inside your product.

Do I need my own server for calls?

Usually something has to relay traffic. WebRTC says a direct connection is often not possible. That relay can be a hosted service or a server you run, and I explain both.

Can I add calling to an app that already exists?

Yes in most cases, as a new feature. I first look at how the app is built and where the login and user records live.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.