I feel like it might be an issue with the smartphone device or carrier performance, though…
If it’s no good on a Pixel 9a, isn’t that pretty rough?
I think asking them to do something about errors that occur when switching connections might be asking a bit too much.
Rather than waiting for a technical solution from the dev team, I think it’s better for users to take workarounds on their own.
It’s strange that it isn’t designed to account for network switching,
even though communicating on a mobile phone on the go means cell towers are constantly changing.
To put it simply, addressing this is probably almost impossible. In the first place, the lag that occurs the moment the connection switches isn’t an issue on the server side, but on the network side, like Wi-Fi or 4G (5G). This is because whether it’s Wi-Fi to 4G (5G), vice versa, or between Wi-Fi networks, the process where the connection becomes unstable before switching, searches for a destination, and logs into another network happens on the device side, completely unrelated to Now’s servers.
To begin with, the connection is already unstable before switching, there’s no guarantee the new connection will be stable, and the time required for authentication depends on the network. It wouldn’t be unusual at all if the network happens to be congested and authentication takes 5 seconds.
Because of these circumstances, device performance has almost nothing to do with it. If lag bothers you, manually switch to cellular before you start walking. Worried about data usage? If you’re going to play mobile games outdoors, sign up for an unlimited plan.
Also, cell towers keep changing because you keep moving. Stop in an area with good reception, make sure it’s safe, and then play.