We reached the point (some time ago) where the save icon being a floppy disk makes absolutely no sense to anyone born after a certain time. We could choose a more modern media format and use an icon of that instead, but we would run into the same problem once that media becomes obsolete.
What is a good icon for the function of saving something that can easily be understood by anyone regardless of language or the march of time?
Edit: I know it’s not really an answerable question and is hard but the question is what would you come up with if tasks to design an icon. Given the constraints of the question, what are your best shots at coming up with something that fills the requirements and why do you thing it would work?
Floppy disk. Fight me.
Agreed. It’s the tried and true icon.
It’s like on discord, what’s the symbol to make a call? An old school telephone handset. People know what it means. It’s a universal symbol
People have stopped recognizing it as a disk (which is good because that meaning was always pretty confusing in terms of saving vs loading) it is now the save symbol and will continue to be the save symbol centuries after the last floppy disk has crumbled into ash.
Similarly, the folder icon has now been enshrined as load.
Why is the disk save and the folder load? It’s completely fucking arbitrary, both worked just as well for each context. But someone somewhere (probably in the MSFT internationalization and standards team tbh) made that choice once and thus it is that forever.
Yeah there is no reason at this point to change it as we just teach people that the floppy disk means save. I was wondering if we could come up with something that the user, at a glance, would generally identify as saving. What would that glyph look like. In other words, the arbitrary and established icon is what it is but with hindsight and thinking ahead what would be a better icon we could design. One that would convey “save” to the most people the first time they see it.
The act of loading necessitates a selection, so the folder makes more sense.
No more so than saving. Either saving and loading use free filesystem browsing interfaces, slots that are embedded into a single file/non-descreet location on disk, or they save into a limited scope of files/folders on disk. The last system seems to be the most common in modern UX within non-compatible apps with the first system being preferred for apps dealing with common files (like a text editor).
Also, there is a whole thing with Save As vs. Save - though with a new file/profile/whatever Save can often trigger a Save As action.
Most saving is done on files that already exist.
That’s a fair answer. There is nothing saying the floppy disk can’t work. By sticking with a symbol that has no actual bearing on function (from the perspective of the future people) you’ve abstracted the concept of saving away from natural language. However, you still place a computational burden on those future people/aliens/whatever where they need to be taught what that icon means.