


WhiteHelmet came with a working product and its own developers and DevOps team, so we worked inside the client's existing Android app and Laravel backend, and sign-in, accounts and organizations stayed as they were. The hardest part was keeping a long 360° stream alive and sharp on an ordinary Android phone, often in the heat. We proved the path with two proofs of concept, then moved the backend and web app, then Android, checking each step against transition criteria.
The phone receives the camera feed over USB and sends it as one RTMP stream to the LiveKit ingress, a service that re-encodes the stream and adds it to a video room as a live track. Browsers show that track in a 360° player, and everyone in the room also talks by voice and webcam. The backend creates rooms, issues access tokens, sends invitations and closes rooms nobody uses anymore.


The phone has to stitch the camera's two lenses into one panorama, encode it and push it over a mobile connection, often on sites at 45-50°C. The client's brief described sessions that dropped within 10-15 minutes under load on the previous setup and set a target of 90 stable minutes. We removed the causes of those drops one by one:
We measured the viewer's delay and the server load, on the test setup and in the client's field runs.
The client runs the streaming in its own cloud: we moved it to self-hosted LiveKit and packaged the media servers as a Helm chart (an install package) for the client's Kubernetes cluster. The client's existing backend issues the LiveKit access tokens and runs the rooms. The setup includes:


Viewers get a feed sized to what the phone really sends: the app measures the frame rate each quality level delivers and reports it to the backend, which sizes the server's re-encoding of the 360° feed to match:
The operator can switch between High, Medium and Low during a tour. The viewers' browsers get a restart signal, the backend applies the new settings only after the old stream has stopped, and the phone resumes on the new level:
If the server does not confirm in time, the backend keeps the old settings rather than cut the stream. Every step has a time limit, so the operator is not left waiting.


On a hot site, a phone can throttle or shut down in the middle of a long tour, so the app watches Android's thermal forecast and lowers the load itself before that happens.
A loose cable or a dead spot in coverage does not end the tour, because the app brings the camera and the connection back on its own.


Android phones differ widely in what they can encode, so the app reads the limits of the phone's hardware encoder and hides the levels it cannot handle. The stream starts on Medium, or on Low if Medium is out of reach.
Viewers drag to look in any direction in a 360° player built on A-Frame and three.js, and the picture stays on screen while the stream changes underneath.


The web app covers the steps around a tour, from creating a room to joining it:
Problems on a site are hard to reproduce in an office, so both apps record what happens during a tour.


The same code serves two branded editions. The Android app is built as WhiteHelmet and as Salama, a second edition under its own name. The Android and web apps are available in several languages, and the web app switches to a right-to-left layout for Arabic. The Android app checks for new versions and prompts the operator to update.
The stack below covers our part of the work.
Yes, with the camera plugged in over USB. The phone stitches the two lenses into one panorama and sends it as one stream, so the app fits quality to the phone's hardware encoder and lowers the load when the phone gets hot.
Yes. In Live Virtual Visit, LiveKit runs on the client's own Kubernetes cluster, installed from a Helm chart, and the client's backend issues the access tokens.
No. Sign-in, accounts and organizations stayed in the client's existing backend, which now also issues LiveKit access tokens.
The tour goes on. The app reopens the camera and restarts the stream after a pulled cable, rejoins the room after a lost network, and the room waits three minutes for the operator to return.
On an ordinary phone in the field, the stream comes back by itself after a pulled cable or a lost network, quality fits what the phone can encode, and a hot phone lowers its load before Android throttles it.
We build the same kind of software for other products that stream live video from a phone or camera to remote viewers.
