This is a user expectation to not lose work and also not have temporary edits commited without saving them. And besides, it doesn't save everything anyway either! Citing Windows UWP patterns as the fault of the user is disrespectful to the trade of user experience design. If you had tested this with experienced designers you would have discovered this earlier, before you released it to the world and cost us all a bunch of time (and yes money) trying to recreate or uncreate temporary work that UWP may have decided to commit or not. The request is to give us control of save, not some random cloud backup process that is dependent on internet connections etc.
Sadd Kustimer
supported this idea
·
This is a user expectation to not lose work and also not have temporary edits commited without saving them. And besides, it doesn't save everything anyway either! Citing Windows UWP patterns as the fault of the user is disrespectful to the trade of user experience design. If you had tested this with experienced designers you would have discovered this earlier, before you released it to the world and cost us all a bunch of time (and yes money) trying to recreate or uncreate temporary work that UWP may have decided to commit or not. The request is to give us control of save, not some random cloud backup process that is dependent on internet connections etc.