App creators are given an API and ways not to break support for your device; it’s on them to do device testing of all their app’s corner cases. This doesnt seem unreasonable to me. What else should apple do?
Apple can share the blame, because they didn't test the app like they should have to verify that the app was in fact compatible with the hardware the dev claimed. Or maybe the dev did everything right, but Xcode had a bug.
But mainly, just let me download whatever previous version I want.
Maybe Apple doesn't have a spare iPad just lying around; they're hoping that the devs have bought all their extras, to test software updates in different platforms...
Why not let the user download any old version? Let the users mark newer versions as broken for their hardware, so that the last-known-working-version is not reset?
I mean, they have a platform, but the feedback loop seems kind of broken.
Honest question here about the risk of being “unique”...:
If my unique identifier changes with each browser version + os version + timezone + build id + fontpack + screen size... am I really trackable through this vector? Those things change all the time for me at least. Seems like a very short term method of tracking at best. Why should we be afraid of these things? I had the same question about panopticlick (or whatever EFF called it).
Yes, but that only works in local networks and after connecting via USB once – and the backup is always stored on a single computer. So it may be acceptable for personal usage, but not suited for an enterprise environment where you want to centrally manage hundreds of devices and provide some redundancy for your backup system.
I guess I don’t understand this point. This is exactly what ios mdm backup is for. Relying on users backing up their personal icloud accounts for work seems highly problematic. If they are work icloud accounts... usb should not be a problem since you are probably provisioning the devices, and the itunes backup approach over your intranet seems actually ideal.
