I’m going to be honest here. I don’t think a web app is well suited for something like this. I say that because it requires an app to be open and active on the screen at all times. Turning the screen off or switching to a different app on your device is going to kill that connection, so drivers would not be able to use their device for anything else or be able to turn the screen off. Plus, for it to work with the native location component, it would require constant and rapid updates to the table, which I’d guess is not something glide would like.
I’ve dabbled a little bit with location in some personal apps. The location component is more suited for getting a location once or using it while actively interacting with the app. I don’t think it was ever intended for something like live user tracking although it can technically do that to some degree. In my experience it’s never been fully reliable for live tracking. In this app below, I store the location in a user specific column in an app I’m not signed into just to prevent unnecessary writes to the table. Fun to play with, but not something I’d use in a production environment.
Outside of Glide, I’ve built a simple HTML page that can continuously monitor my location and draw a track on the screen as I move. It’s not something I can embed in a Glide app because location info is not accessible within an iframe web embed for security reasons, and there is no way to directly integrate it with Glide tables unless you start using the Glide API which will chew through update real quick. However, as soon as I turn my screen off or navigation away from that page (which runs locally on my device), it’s no longer tracking.
I’ve also dabbled with websockets in a page that I have embedded into a Glide app. This is for a music app I made that lets me remote control it from another device. Websockets allow for a somewhat direct connection between devices or multiple devices and allow for rapid fire updates to be shared between device. Again, these pages need to be active on the screen to reliably maintain that connection, which can sometimes drop. Plus I need to be mindful of the number of data packets I’m sending since I’m limited with the service I use.
With all that said, based on my experience, it’s difficult to track live location and share it with others, especially with a web app. Possible…yes, but in a web based app, I don’t think you will ever have a reliable long term experience. I honestly think something like this is only going to work well with a native app that can better run in the background of the device and have access to GPS data and a server that can handle the rapid fire traffic.
You mention transport, so I don’t know if that means long haul over the road travel or something more like a local in-town delivery service. I think you might have better luck having check-ins where a driver presses a button or edits a row periodically as they do their deliveries. Amazon delivery for example only updates locations at each stop, so I never see real time location… just location of the last stop.