Industry
Video Calling App Development
Calling looks like an SDK integration until you hit relay costs, background handling and the first network that blocks you. Those are the parts worth planning.
The short answer
Video Calling Apps — what actually matters
Haqto builds voice and video calling into applications — consultation and telehealth products, education platforms, customer support tools and communication features inside larger products.
We have no published video calling product to point to, and we will not invent one. What we will do is be specific about the parts that usually go wrong: relay infrastructure cost, mobile background behaviour, and regulatory constraints in markets that restrict voice over IP.
Where it goes wrong
Common challenges
If several of these describe your situation, the problem is usually structural rather than cosmetic.
- Relay traffic is higher than defaults assume, and relay is the line item that scales with usage
- Mobile background and lock-screen behaviour differs enough between platforms to need real work
- Incoming calls must behave like calls, not notifications, or users miss them
- Group calling changes the architecture entirely — mesh stops working at small numbers
- Network quality varies enormously; adaptive behaviour is required rather than optional
- Some markets regulate voice and video over IP, which is an architectural constraint not a legal footnote
- Recording introduces consent, storage and retention obligations that reach beyond engineering
What it needs
Digital requirements
Signalling layer
Call setup, negotiation, state and presence. Abstracted from the media transport so the transport can change without rewriting the product.
STUN and TURN infrastructure
Relay for the sessions that cannot connect directly. Sized from your expected concurrency, because this is the cost that grows with success.
Topology chosen deliberately
Peer-to-peer for one-to-one, a selective forwarding unit for groups. Mesh stops being viable at surprisingly small participant counts.
Native call integration
CallKit on iOS and the Android equivalent, with push wake-up, so an incoming call behaves like a call rather than arriving as a banner.
Adaptive quality
Bitrate, resolution and codec adaptation to real network conditions, plus a defined degradation path to audio-only rather than a frozen screen.
Recording and retention
Where required: capture, storage, access control, retention rules and consent capture. Scoped as its own piece of work because it is one.
Capability
What we build for video calling apps
- One-to-one voice and video calling
- Group calling via selective forwarding
- In-call chat, screen sharing and file transfer
- Native incoming-call handling on iOS and Android
- Adaptive bitrate with audio-only degradation
- Session recording with retention controls
- Waiting rooms, scheduling and calendar integration
- Per-minute or per-session billing integration
- Admin controls, session logs and quality reporting
Worth being clear about
Compliance and data
Examples
Typical projects
Telehealth consultation
Scheduled appointments, waiting rooms, in-call notes and recording where the sector requires it, with consent captured properly.
Paid expert consultation
Per-minute billing tied to session state, including correct behaviour when a call drops or a party never joins.
Remote teaching
Group sessions with screen sharing, materials and recording for later access, sized for classroom rather than meeting concurrency.
In-product support
Calling embedded inside an existing application rather than sold as a standalone communication product.
Related
Services that apply here
The services most often involved in this kind of project.
Mobile App Development
Android and iOS applications, plus the backend, APIs and admin tooling that make them work. Built once in Flutter or React Native where that suits the product, natively where it does not.
Custom Software Development
Internal platforms, portals, dashboards and workflow tools modelled on how your operation actually runs — not on how packaged software assumes it should.
Cloud & DevOps
Infrastructure, deployment pipelines and monitoring set up so that shipping is routine. If releasing makes your team nervous, that is an engineering problem with a solution.
UI/UX Design
Research, information architecture, interface design and design systems. Decisions we can explain and you can defend — not decoration applied at the end.
Questions
Video Calling Apps — frequently asked
Can you just integrate an existing calling SDK?
Often yes, and where a managed provider is the right answer we will say so rather than building infrastructure you do not need. The decision turns on volume, cost at scale, control over media paths and whether your market restricts voice over IP. We will show the arithmetic rather than assert a preference.
What does relay infrastructure actually cost?
More than most estimates, because the proportion of sessions that cannot connect directly and must be relayed is higher in real networks than in the textbook figures. We size it from your expected concurrency and deliberately err high, since this is the cost that grows exactly as the product succeeds.
How many people can be in a group call?
It depends on the architecture chosen. Peer-to-peer mesh degrades quickly beyond a handful of participants because every participant sends to every other; a selective forwarding unit changes that, at the cost of running infrastructure. The participant count you need is an architecture input, so we ask for it early.
Why do incoming calls need special handling?
Because a call arriving as a push notification gets missed. Native call integration — CallKit on iOS and the Android equivalent — makes an incoming call ring and appear on the lock screen like a real call. It is fiddly work and it is the difference between a calling feature people use and one they abandon.
Can calls be recorded?
Technically yes, and it is a larger piece of work than it sounds. Recording brings consent capture, storage cost, access control and retention rules, and the consent requirements vary by jurisdiction and sector. We scope it separately rather than treating it as a checkbox.
What about markets that restrict voice over IP?
Several markets, including parts of the Gulf, regulate voice and video over the internet. In those cases the permissible approach has to be established with your counsel — and where relevant a licensed local operator — before an architecture is chosen. We will not design around an assumption and hope it holds.
Have you shipped a video calling product?
We have no published product in this category and will not claim one. What this page describes is capability and the specific failure modes we would plan around. If you need a reference client in this exact category, we are not the right supplier and we would rather say so now.
Start here
Building something in video calling apps?
Tell us what you are trying to achieve and what you are working with. We will come back with an honest view of scope, approach and whether we are the right fit.