Tag Info

New answers tagged

1

I think it's your second choice explanation for why everyone doesn't save automatically. . . "It's technical or technology limitations of the specific job and code language and architecure already in place. " Saved buttons are still used because lots of back end programers haven't learned to program auto saves well and haven't had experience with new ways ...


2

Usage of auto save button is great but it should not be forces to user. It works like a charms in google doc, email etc scenario. But I'd never implement it with forms because 1: It takes control from user 2: Auto saving data will fire lots of server calls 3: With auto saving forms a false alarm might send to user that some one is storing data without ...


4

It really depends whether we're referring to Save as simply an action which persists the users data without any wider impact, or whether this could also apply to other scenarios. If my Save action has an impact on something wider (e.g. applying some settings that cause significant changes to a system), then losing manual control over this action could be ...


2

This reminds me of a discussion a while back about the current save icon, the floppy disk. The OP thought the floppy disk was outdated and youngsters didn't recognize the metaphor. The discussion consisted of people trying to come up with an alternative. My opinion on that matter was to remove the save button all together. Documents and such should be saved ...


1

The auto save is a great idea. Agree with you that Google docs and Gmail using the auto save are the best examples to save data/progress automaticaly. But this may not be ideal for every application. Imagine trying to play a game which autosaves every couple of minutes, it would be annoying. This would be more annoying if the saving time is more. Google docs ...



Top 50 recent answers are included