Butt adding a major new feature - Advanced Privacy - in v1.0without testing it in v0.nn betas? Who thought that was a good idea? Seems like marketing (“We want/need to be able to say we have this, for the big launch announcement”) won, over technical (“We really should test this functionality properly before we include it in a major release”). It caused the overall quality - and the appearance of quality - of v1.0 to be significantly worse than v0.23: location “doesn’t work”, issues with accessing the network, battery draining, etc.
Really disappointing for users, and if I were a developer, I would be really angry
I think the sweet spot would have been to ship advanced privacy in eOS 1.0 but turn all its features off by default (at lest for me, it was active after installing eOS 1.0). So it is there and everyone who wants to can use it, but it would not impact the user experience in cases where the users are not even aware that this thing exists.
In my experience so far, advanced privacy does exactly what it should do, but choosing to use it makes some apps not work anymore, and this cannot be resolved by more testing. Instead, everyone needs to learn or be taught what it is and when to use it.
Yes - that would have worked, and would have been a sensible approach. But unfortunately they enabled it, and as a result, they shipped an OTA update which appears to have effectively broken many users’ installations. Unforgiveable IMHO