Agree.
Also: tooltip help when you hover over an icon.
Also: menus (for discoverability)
Also: manuals/help files (yep, most software shoudn't need one, but now we are in a worst-of-all-state: new software is not self explanatory, doesn't use familiar designs and the manual is gone :-/)
If something looks like a button and they try to push it, is because in real life buttons have a certain look and feel.
But I'm pretty certain that if you teach them at an early age to discern what does what in a flat UI, they'll have no problem switching from one UI to the other (I actually learned _from her_ that in the Android YT app you can swipe those pesky lower right corner videos to make them go away). And we're still to try flat in real life ;)
Plenty of appliances have electronic buttons, which are close to flat (though definitely not flat) and commonly paired with a flat visual style on top of them. They work pretty well, in that context.
And now plenty of appliances have capacitive controls, which are in my experience normally a disaster and literally never good (I exclude situations where a screen is involved; those are hit and miss). To take an example, microwaves: almost without fail, I find that the newer it is, the harder it is to use—though the old dials were only easier to use in certain ways, lacking precision. I now have one with a capacitive touch surface, and it’s very hard to use unless the room is brightly lit, at which point is’s merely quite painful unless I want to turn it on for exactly 30 seconds.
Decide for yourself whether these things are “real life”.
But I think that analogy falls short in one major way, which is that these buttons are logically grouped and evenly spaced across a surface that consists of _nothing but_ buttons. If there's silkscreened text there, you can press it and do something. The visual display of information happens in an LED display set aside in a well-defined area, so things to look at and things to press are 100% clearly delineated. In a desktop/mobile/web app, where content and interactive elements are interspersed, you lose that obvious context clue. That inevitably adds cognitive load, even if the interface is still technically usable.
Not only do they not work, no only do they sometimes trigger adjacent controls, but to get function back I now have to dry both my hands and the control surface.
I will never purchase a kitchen device with capacitative controls, but I run into them enough when traveling to experience this frequently. It's a mess.
The buttons are capacitive but they're very responsive and it's easy to wipe down.
Old microwaves had a clear, directional knob with a start point, an end point, and markings for the values they represented. Barring the question of precision (which could be more or less solved with a more strikingly non-linear dial), that’s positively superb. My ideal microwave has only the following controls: such a dial (you could do some pretty fancy active magnetic design on it to improve it and make it precise, over the old knobs), probably another dial or slider (I’m open to trying it out) for power level, and that’s it. I’d be willing to discuss a +30s start button which moved the knob into the right place for you, and some sort of digital timer for potentially easier reading from a distance. No start button or stop button or open button, because the door opening and closing is better than the old microwaves.
Now it is possible for an unanchored knob to be good; I have in mind a tuning knob from a fairly expensive radio from fifty or more years ago, where they had clearly put a lot of effort into its friction profile. But I’ve never seen such a thing in the digital age, only ever in the analogue world. (Hmm… I wonder whether sound boards count. They may be an exception.) In the digital age, knobs are normally just glorified less/more buttons with very coarse quantisation.
My microwave is similar to yours, but a cheaper model, with most notably a capacitive touch strip instead of the knob; it’s awful.
Sometimes I twist the knob until the display shows the desired time—in this respect it works like an iPod.
And when I want to defrost bread, I know it's Defrost program 4. Or if I want something else, the list of programs is helpfully silk-screened behind the door.
Maybe my expectations are low, having owned a Panasonic for the previous 9 years. But I'm genuinely happy with it. It works for me.
(I did see the capacitive touch strip model and actively avoided it. I knew I'd hate it without even trying it.)
As a silly example, I just opened the Google Maps app. Basically everything is clickable or swipable, but there is no visual consistency whatsoever. I suppose “everything is a control” is a viable model, but it breaks down if you want to show content, too.
You could say the same for early iOS apps that just used the default Apple widgets and style. I think ~every app I use know has its own style.
Funny enough, this is less true on computers. Except games.
It's often ludicrously bad.
It turns out the same types of optimizations that you make on a landing page are good UI/UX features for past-middle-aged people to use. Computers don't have to be hard, we just put everything on the screen and have the user sort through what each thing does and whether it's in or out of context for the current action.
Especially with landing pages I aim for the 'mum' test. She's in her 60s and is petrified of computers. If someone like her understands what has to be done / the messaging is clear / the flow of the page directs her to do what I want, it'll probably be a success.
Anecdotally I remember being on a call with my dad (in his 60s) trying to talk him through downloading and installing some antivirus software from download.com (or whatever it was back a few years back). Frustratingly it kept going wrong - "I'm pressing to the download button, but it's just not working!" Except he wasn't. Eventually we figured out he was clicking a banner ad because it "looked like a button," far more so than the flat, actual download button. On a site like that, I often wonder whether it's entirely by design. Happy advertisers get more clicks (albeit probably with shitty conversion), happy site owners get to charge more knowing they provide more clicks. Everyone wins. Except my 65 year old dad.
Most certainly yes. In fact, recognition of "false download buttons", and almost instinctively and subconsciously ignoring them in the same manner as banner ads, comes with experience such that there have been times when I've been confused by pages where the real download button looks exactly like the bloated fake ones that I've become accustomed to mentally filtering out. I find that when I'm looking to download something, I tend to go towards direct links that actually show a destination URL when you over over them, vs. buttons that don't.
Implementation would be interesting and most likely quite hard to achieve, though.
Having worked on a number of platforms (MVS, CMS, VMS, Unix, plus the usual desktop kit), I'd come to recognise signatures of those platforms. Under Unix, recognising the original X11 Xt, Athena, Motif, Tcl/Tk, gtk, Qt, Java, and Gnome toolkits is largely second nature.
No, all applications don't look and behave the same. (Xt scrollbars FTFW!!!).
But: if you do recognise the toolkits, you've got a pretty good idea of the provenance of the application, and how it's going to behave and what quirks it will have. At least up to a point.
I do still prefer button-resembling-buttons.
Obviously, the majority of computer users aren't toddlers, but I think there's a lesson here. I really miss the old Windows 3.1 / 95 / 98 days when controls were more or less standardized and you could reliably tell which were buttons, which were radio buttons, which were okay buttons, etc.