Redesigning the Save Symbol
branch.com
branch.com
Similarly, the D-pad from a NES controller -- or worse, an Atari 2600 joystick -- is often used to represent or signify "video games".
"Home" is based on tract housing from the 1950s; yet even if home to you is an apartment, condo unit, palace, or boat, that icon still means "home".
There's another example. I just recently bought a Moleskine with an abstract graphic image of an audiocassette on it. There's no real reason for this; it's very hipster. It's sort of "celebrating the audiocassette" because to an entire generation of people, the cassette -- and its shape -- meant music (especially music on the go, like in a Walkman). Youngsters connect to it too, in a "retro" way. The same will be true of the floppy disk icon. No one uses it now, but it was ubiquitous that -- like the audiocassette or the distinctively shaped horn of a Victrola phonograph -- its shape has become semi-permanently associated in our culture with its intended use.
Icons don't have to keep up with the actual technology whose function they represent... they just have to be immediately recognizable.
http://sl.reddit.com/r/funny/comments/1b22bl/i_was_cleaning_...
Internet Comment Designers seem to think that skeuomorphism (a word they love using to tell the world 'LOOK, I KNOW BIG WORDS SO I MUST BE GOOD AT THINGS') must always be a bad thing...as if using the icon to save as a floppy disk is somehow less confusing to the average person than a circle with line, space, longer line, space, shorter line, space, rest of circle is somehow more intuitive.
People use & all the time and don't know what it means. Hell, @ doesn't even have a clear definition! But people know what it means, and that's what matters.
How come people don't use a hard disk as a save icon? How come the icon of a CD didn't catch on as a "Burn" action?
Its not because these actions are any less actionable than "saving" to a floppy disk. Its because you can clearly tell WHAT a floppy is compared to other donut looking objects, and that is what matters!
You don't need to flatten the UI or make something you think looks like an IEC symbol (protip: the symbol you all use for on/off is IEC 5009 symbol for "standby"). All you need to do is make sure that the symbol is unique enough that it can't be confused for anything else. Having the added back story that it used to "be" something else makes it trivia fodder in 50 years.
Yes, Apple is stupid for making their calendar look like a book. No, I am not a knuckle-dragging cave man for thinking a floppy disk is a good symbol for "commit to disk."
Get off my damned lawn.
The short answer is "No."
The long answer is that the skeumorphism is bad argument is generally that trying to imitate some kind of physical analog of the computerized process you are doing isn't an effective way of presenting a UI, in part because it imposes additional constraints that aren't native to the medium you are using (limiting your ability to fully utilize the medium you are using) and that it relies on experience with the particular physical analog to provide user understanding of the UI.
An icon that is functionally abstract because it references something that is outside of most users experience would be an example of the problem, not something that somehow flips it on its head and so becomes good.
(OTOH, the use of the floppy-disk-image-as-save-icon is so ubiquitous in software that it is probably a useful image that is well recognized, but that's neither because it originates as a skeumorph or because it is abstract now, but because it is ubiquitous in the digital realm, independent of its origin or current relation to user's non-digital experience.)
In fact, the Windows 8 machine I'm on (shudder) actually represents "Shut Down" using the standby icon.
To be fair, I did just go back and search and anachronism had been used but skeuomorphism was not. Looks like I've been spending too much time on HN and Reddit!
I'm not a designer, but I think most of the ideas on display here are fashion-forward dead ends.
This... It seems like these are "design for the sake of design", and doesn't take into account that the vast majority of users really don't care, as long as they know what the button does--which these examples don't really convey.
Usually when people use save, they actually want to take an action. (ie: exporting the file somewhere, sending it to someone, etc.)
This thread should focus on identifying those actions and finding more universal ways to make them ubiquitous.
What if there was a universal "send this" or "invite someone to collaborate" button?
Though you would need to worry about atomicity when having a file open in two editors constantly "auto-saving" the document; you'd need some way to synchronise state. Probably easiest to make file write access exlusive by default.
Are you talking about the "share" button? On Android this is three dots in an equilateral triangle, with two of three sides connected by a line.
Oh god please no. Apps that save automatically are the worst idea ever. I want to be able to make exploratory modifications, and then commit to disk AT A TIME OF MY CHOOSING. The computer doesn't know what I'm thinking, and it can't tell the difference between "messing around" content vs "serious" content.
I can see it now: I hit undo a bunch of times to get back to a previous state, copy some content that I wanted to bring back, then redo a bunch of times to get back, except I fatfinger it and hit paste by mistake. Now my whole redo path is gone, and I can't even reload to the state I was at before hitting undo thanks to the braindead program that "helpfully" saved my document behind my back.
Or even worse: I make some exploratory changes, then decide after changing a LOT of things that it won't work. The app crashes/the computer dies, whatever. I reopen the app and it's saved all the changes I don't want anymore. Maybe if I'm lucky it would have saved an undo path (unlikely), but even then, how far do I have to undo to get back to the sane state I was in?
Save means "I'm sure this is what I want. Persist these changes".
Turns out, these guys just did that. Except with documents [2] and clouds [3] instead of folders. Guess iOS did away with those.
[1] - As seen in https://en.wikipedia.org/wiki/File:Lotus_1-2-3_9.8_Windows.p... , upper left corner
[2] - http://branch.com/b/redesigning-the-save-symbol-let-s-do-thi...
[3] - http://branch.com/b/redesigning-the-save-symbol-let-s-do-thi...
(I certainly do)
The load icon's arrow is bright green, while the save icon's arrow is teal. Which is downright impossible to see at 1440x900.
...I think the idea might have been better than the implementation.
Which makes me think... if I'm coding and the project is in git repository, why am I still manually saving all the time? Why not automatically save every change I make as a revision, and provide me with endless undo (even if I quit the IDE). "Save" could now instead do a git rebase & squash to produce a neater commit from the many intermediate revisions.
Back to the original topic, I think auto-save and undo obsolete the save button.
[1] https://developer.apple.com/technologies/safari/developer-to...
[2] this site has chrome screenshots, but it's what safari 5 dev tools looked like: https://developers.google.com/chrome-developer-tools/docs/ov...
Saving is often used by non-developers as a poor man's branching and version history.
I used to have vim autosave every time I changed focus. This worked really well, until I edited something which wasn't in revision control. That time I just cancelled the experiment, but maybe I should restart it and just autodetect if I'm in a repository or not.
everyone is only 1 billion people with a USA influenced cultural history and a Microsoft influenced PC history.
FirefoxOS stands a good chance of reaching a new billion people, and some mobile device will, and what will the chinese-ubuntu choose for save? There are going to be 10bn people alive in 2050 (I hope!) and 9bn of them have not seen a floppy disk icon.
It might be that we stick with the icon and everyone starts spelling skeuomorphism wrong. But is it likely?
So I quite like the discussion shown here. There are a couple of good ideas. And the new devices, then new mental models of synching local and remote storage, are going to need new iconography. Will these guys do it? Only if they buy a domain, produce high quality glyphs with open discussions, make it free and blog about it incessantly - then maybe when the next big thing comes along, they might just reach out and take the easy icon set. That would be nice.
... which I suppose one can see coming from a mile away, but I really hope it doesn't become ubiquitous.
If you're talking about representing a change of state (volatile to non-volatile), then borrow from Chemistry where a change from liquid to gas is represented by an arrow up, and a change from liquid to solid is represented by an arrow down. You could use the Unicode character U+21DF, a symbol that's already on every computer. Inversely you could use U+21DE to indicate "Load".
It doesn't matter where icons, words, or any identifier comes from so long as everyone understands it. If you're creating a new icon then it's a good idea to make the design intuitive as this improves its chance for adaption, but doing so to an ubiquitous icon such as "save" is just counter-productive.
Here I am, screaming at my screen "Why can't you whipper snappers just leave it the way it is! I like the floppy disk icon! This is the devils work I tell you! You're going to ruin the internet!!"
Also most apps save automatically and usually use an animation of something spinning, so you're already a tad too late.
If you have a universal cultural idiom, I think it means you won the war of conveying a concept.
Computers should never lose your work, you shouldn't have to instruct it.
Remember - it has to work for non-technical users, so saying "just make it work like Git" won't fly.
Why?
How about by picking a form that will always be in the past, and already well-documented and broadly understood, instead of trying to guess which of today's fads will be remembered?