Why does Zwifts app seem to be such a massive data hog, especially considering how many users are likely to be streaming the app on their home Wi-Fi networks where data caps arent typically a concern? Is it really necessary for Zwift to be constantly uploading and downloading data in the background, even when the user is just riding in a solo session or not actively interacting with the app?
Some users have reported that Zwift can consume upwards of 5-10 GB of data per hour, which seems excessive compared to other streaming services like Netflix or YouTube. Is this due to the apps reliance on real-time graphics rendering, or is there something else at play here? Shouldnt Zwift be optimized to use less data, especially for users who are on metered connections or have limited data plans?
Its also worth noting that Zwifts data usage can vary greatly depending on the type of ride or activity being done. For example, a social group ride might require more data bandwidth than a solo ride, but is this really necessary? Cant Zwift just use a lower quality stream or reduce the frequency of data updates to conserve bandwidth?
What are some possible solutions to this problem, and are there any plans to optimize Zwifts data usage in future updates? Should users be forced to choose between enjoying a seamless Zwift experience and blowing through their data caps, or can we find a happy medium that balances performance with data efficiency?
Some users have reported that Zwift can consume upwards of 5-10 GB of data per hour, which seems excessive compared to other streaming services like Netflix or YouTube. Is this due to the apps reliance on real-time graphics rendering, or is there something else at play here? Shouldnt Zwift be optimized to use less data, especially for users who are on metered connections or have limited data plans?
Its also worth noting that Zwifts data usage can vary greatly depending on the type of ride or activity being done. For example, a social group ride might require more data bandwidth than a solo ride, but is this really necessary? Cant Zwift just use a lower quality stream or reduce the frequency of data updates to conserve bandwidth?
What are some possible solutions to this problem, and are there any plans to optimize Zwifts data usage in future updates? Should users be forced to choose between enjoying a seamless Zwift experience and blowing through their data caps, or can we find a happy medium that balances performance with data efficiency?