Most people are familiar with WYSIWYG- What You See Is What You Get- a computer user interace that displays things in a format that fairly accurately displays on screen what the final output will be, so that (as a simple example) rather than a bit of code:
<b>this text is bold</b>
this text is bold
I’ve spent several hours of my life recently trying to find out why a program I have to use daily was refusing to email people. Here’s the UI:
Skeumorphic twice over? A web app emulates a phone emulating a slider switch, badly.
You’ll notice the option to email two people, controlled by sliders. These are a skeuomorph: soemthing that icorporates design features of something it emulates- in this case, a slide switch. In fact, it’s a double skeuomorph: it’s a web interface impersonationg a smartphone impersonating a slide switch.
I’ve got two problems with it. Firstly it’s unneccesary frippery and animation, and secondly, it plain doesn’t work. It’s distinctly What You See Is Not What You Get. I’ll grant you there’s a certain amount of PEBCAK here on my part, but the control is broken.
If you click on the left-hand side of the control, and swipe accross, like you might with the control it imitates on a smartphone, the control changes to YES. It does the same if you click the right-hand end, or if you click and drag, keeping within the boundaries of the control. The difference is that if you use the first method, like I did, it shows YES, but registers NO to the back-end software, and gives you a several-hour troubleshooting session to work out why the email didn’t send. An older version of the software has a simple check-box here, and I suspect that this is a simple case of layering a bit of wankery over the top for effect…
Opinions differ on skeuomorphs: some consider them to be problematic, and some think them great, for the same reason: they imitate familiar technology, and so either make people confused, or make then feel at home. This one definitely left me confused.