There’s a good reason that these two icons are currently different.
Not really, it’s just legacy, the same reason the save icon is still a floppy disk in most programs. That’s what it’s always been.
You may make the distinction between saving a document and downloading a document, but most people don’t pay anywhere near that amount of attention, and don’t care about specifics.
When you’re working on a document in the cloud you have the option to save it (in the cloud) or download it (to your device). Those are two actions that can exist at the same time.
Downloading data and saving data are two separate and distinct functions that describe a different process. While they may have a similar result, they are not the same thing.
You may not understand that, even after I’ve explained it a second time, but they’re not the same thing. They work differently, occurring different contexts, and a single icon should not be used to communicate two distinct concepts. That’s why there are two separate icons.
Whether the save icon is that of a floppy disk or not, doesn’t change that.
And your argument basically amounts to that people are too stupid to care.
But you raise a good point: why would it need to be changed? It’s everywhere, everyone already knows it, it works. Why change it? After all, you seem to think that people are too stupid to care.
You may make the distinction between saving a document and downloading a document, but most people don’t pay anywhere near that amount of attention, and don’t care about specifics.
Covering “Most people” but not all cases is where most software goes awry. We should probably try to avoid that for something as universal as saving a file.
One could make the same argument about creating a more complicated solution when a simple one solves it for 99% of users. Especially when the remaining 1% will know the difference based on what they’re doing, regardless of the icon used.
(See, I can simplify stuff too. Now there’s a chance that a certain amount of people are wondering if I’m having a stroke instead of linking it to a well-known English saying.
That’s why you’re not actually “simplifying” anything.)
Why does it need to be separate? The end result is the same, the file on your device. Where it is coming from makes no difference.
99% of users won’t care at all.
It’s infinitely more accurate than a floppy disk icon.
They need to be separate because saving and downloading are two separate things.
When I’m in Photoshop, I don’t download the file I’m working on. I save it.
There’s a good reason that these two icons are currently different.
Not really, it’s just legacy, the same reason the save icon is still a floppy disk in most programs. That’s what it’s always been.
You may make the distinction between saving a document and downloading a document, but most people don’t pay anywhere near that amount of attention, and don’t care about specifics.
When you’re working on a document in the cloud you have the option to save it (in the cloud) or download it (to your device). Those are two actions that can exist at the same time.
No, that’s not it at all
Downloading data and saving data are two separate and distinct functions that describe a different process. While they may have a similar result, they are not the same thing.
You may not understand that, even after I’ve explained it a second time, but they’re not the same thing. They work differently, occurring different contexts, and a single icon should not be used to communicate two distinct concepts. That’s why there are two separate icons.
Whether the save icon is that of a floppy disk or not, doesn’t change that.
And your argument basically amounts to that people are too stupid to care.
But you raise a good point: why would it need to be changed? It’s everywhere, everyone already knows it, it works. Why change it? After all, you seem to think that people are too stupid to care.
Then why do you care?
Covering “Most people” but not all cases is where most software goes awry. We should probably try to avoid that for something as universal as saving a file.
One could make the same argument about creating a more complicated solution when a simple one solves it for 99% of users. Especially when the remaining 1% will know the difference based on what they’re doing, regardless of the icon used.
You could make that argument, but you’d be wrong.
I really shouldn’t have to keep explaining why.
Something something assumptions, asses, etc.
(See, I can simplify stuff too. Now there’s a chance that a certain amount of people are wondering if I’m having a stroke instead of linking it to a well-known English saying.
That’s why you’re not actually “simplifying” anything.)