Own product · Taxi dispatch SaaS
TaxiDex
My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
Freelance · WebRTC
I am one senior engineer who builds in-app calling on WebRTC. TaxiDex has voice calls between drivers and passengers with native call screens through CallKit, and I host the coturn TURN server myself. SessionBird, a Flutter app, also calls over WebRTC. I work remotely on the app and the call servers.
Direct connections are blocked by the network, and without a working TURN relay there is no fallback.
The phone needs a native incoming-call screen and a push that wakes the app, not an in-app banner.
Microphone permission, audio routing or a media format mismatch, and each shows up differently in the logs.
A proxy between client and server closes idle live connections that carry the call set-up.
The step-by-step fixYes. The calling in TaxiDex and SessionBird is in Flutter apps, with CallKit for the native call screen.
Yes. I host coturn for TaxiDex on my own servers and can set one up and look after it for your product.
Yes. I check what your app and server already do, then add the call flow in steps, each one tested.
Usually a relay is missing or unreachable. I host coturn for TaxiDex and set up TURN for this reason, so I check that path first.
Proof
Own product · Taxi dispatch SaaS
My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
SaaS · Customer engagement
An omnichannel engagement suite in Flutter: campaigns, chatbot, tickets, analytics and live calling.
Month by month
Next step
A discovery call within 48 hours, and a kickoff typically inside two weeks.