I own LiveTourAudio, and we are building it around a deceptively hard field problem: a guide speaks into one phone while guests listen through their own phones and earbuds as the group moves through real streets.

The no-install browser flow is the easy part to explain. The harder questions are what happens when an Android listener locks the screen, a device changes networks, the route passes through a weak coverage area, or a guest joins late. Low latency matters, but a stream that quietly stops is worse than one that is a little delayed.

Our testing has pushed us toward measuring the things a guide can actually feel during a paid tour:

- time from scanning the QR code to hearing the guide