Image uploading - poor customer experience, waste of storage and energy

Hi Zwift team.

Having used Zwift for years on a PC, in the last few years I’ve been using it on ios occasionally, and now am using it more and more.

Coincidentlly I’ve also been tidying up my photo library on OneDrive, and my storage (as images take up a lot of space). I noticed a few months ago that I was seeing a LOT of Zwift images on OneDrive, which was annoying and thought ‘I’d better deal with that some time’.

Now I’ve discovered that it’s not me missing a setting - apparently there’s a known issue with Zwift forcing customers to save images to their devices. I was stunned when I read that. Actually insisting we save a minimum of one image to device folders (when you remember and go and untick as many as possible on the small iphone interface), which is of course then replicated across storage facilities too (e.g. OneDrive in my case).

That is poor coding practice/design decisioning in my view (and experience). Forcing the user to untick things they don’t want to upload (when they never asked to) is daft, and then not allowing us to completely untick them all is even more strange.

And sadly for the world at large, this means huge amounts of storage will be being used up, which in turn requires resources and energy to maintain, just for pointless image saving.

There should be a way of stopping this, and from what I can see on previous threads in 2023 and 2022 about bugs, there’s been no activity around resolving this

  • customer user experience is bad
  • customer resources are used without asking
  • globally, just a waste of storage and energy

Would be good if the default could be the other way round, and then we choose if we want to, rather than forcing something on customers

Yeah, I find it odd that on iPad you have no way to uncheck all screenshots or default them to off like you can on PC. You always need to have at least one image uploaded regardless of your image settings. I often have to go into strava and delete the image after upload.

Somewhat surprised they haven’t fixed this.