But it's not all bad; you can't put heaps of buttons on a mobile interface because of the limited screen size and lack of precision with pressing them, so some amount of 'magic' and hiding is necessary imo.
In contrast to my father, who gets off work and tries to do something with his computer and has an issue. It's simply faster for him to call me from my room and have me, whose invested tens of hours poking through all the pokable things already to solve his issue. Simply put, between working, commuting, being an adult, etc, my father had no real time to invest this time in pure discovery, when what little precious time he had as an adult had to be divied up in the most valuable way.
I see that now as an adult, free time is precious. You don't have the time to learn like you did as a kid, when you could just throw 8 hours at something. I barely find the time to play my guitar for a half hour a day between working and being exhausted after the working day. I can't imagine having to learn how to use a computer, at this age. I simply have no free time to invest in such with all the other things life throws at you to prioritize, and what free time I do have I'm mentally tapped at that point, and I fully expect in a few decades at this rate to become a technology dinosaur just like my parents and grandparents were.
These things have huge resolution now and the user can pick their language; would it really kill them to write words over the little icons? If in English, perhaps "ANSWER", "HANG UP", "MUTE" and so on, but the magic of words is that it doesn't have to be those exact words ("HANG UP" and "END CALL" are completely different sets of words yet in the context of a phone call, mean the same thing to almost everyone - magic).
Words. They carry so much information. So much. I know, people want to find some magic picture that carries full meaning to all cultures, but there simply ain't no such picture and there never will be; there's no shame in using words. Please. Use words. I'd even happily take them in a language I don't even speak, so long as it used an alphabet I could read (or even not - I can read some common software related words in Japanese simply through having sounded them out a few times). For me at least, words are easy; the ever-changing mist of icon-style-du-jour is not.
But each time it gets updated while you're editing a field, it gets rid of the keyboard, and maybe of the info you just added.
It's extremely painful to use.
Having said that, text has an annoying feature of needing to be localized, and localization of button texts is tricky because you want a very short string, in order to not overflow, because you have very small screen estate on mobile.
(It doesn't also help that some native built-in components have APIs that show the icons only, without text)
There is no creativity any more. Everybody is too busy following apple
I want ugly buttons with clear text on them.
What I definitely don't want is four almost identical icons with nothing to tell me what any of them do, or swipe gestures that are impossible to discover, or (the worst) swipe gestures that expose icons.
And then, the absolute worst of all, the useless "upgrade" that offers zero additional functionality, but changes the location or design of all the icons of an app that you've already learned.
I had assumed you'd just tap the "answer" button, but that failed more often than not. It never would have occurred to me to swipe a minimum of 3cm, starting with the answer button, and I must assume this knowledge has spread to users by osmosis rather than discovery.
Typically it is a tap and drag in some direction, but the direction to drag for answer vs hang up is always different between OEMs.
So that's fun. :/
This[1] is what it looks like when the alarm goes off. (Swipe left to the "zzz" snooze icon or swipe right to the off icon). I can't always rely on muscle memory because I am not always consistent in which direction I put my phone down on the nightstand. This is not the best UI for a person who has just been woken out of sleep and still groggy.
1. https://www.androidpolice.com/wp-content/uploads/2015/07/nex...
Phone interfaces are a minefield for me for some reason. It's too easy to accidentally push a button you didn't realize was a button when you were trying to scroll down the screen but pressed it too hard when you did so. I run into lots of pitfalls like this. I grew up in the era where the OS interface was a "READY" prompt, so I've seen most of the paradigms out there over the years. Nothing has annoyed me as much in recent memory as having a touch-sensitive interface on a slick, compact phone with rounded edges that I desperately don't want to drop.
The solution is:
1) Publish Human Interface Guidelines that detail a rich set of standard gestures, how various tappable elements MUST be marked, and how they SHOULD be arranged.
2) Publish abridged HIG for end-users as a part of user manual for the device/platform. Aim for closed-world reasoning, i.e. the user must be able to build a mental model of, "if I can't see this functionality here, here or here, it does not exist", and not "it may be hidden somewhere else".
3) Tell app developers to stick to the HIG or GTFO.
I know, wishful thinking.
The decay started long, long ago. The other day, someone commented on HN with a link to a piece of old Microsoft WinAPI documentation, I think Windows 95 era or older, where there was a side note on window styling and "escape hatches" that unfortunately had to be built in, because marketers are marketers and desperately want to fuck up usability to put branding on things. Back then, platforms already gave away too much control over styling to software vendors (where originally this control resided with end-user).
It's interesting that nowadays, with all the work gone into sandboxes and frameworks, nobody seems able to do that.
- Swipe from bottom to wake. - Swipe from bottom whilst inside an app, peaks all open apps, once let go it fully minimizes the app. During a peek you also see the number of unread notifications on the left. - Swipe from left to go back. - Swipe from bottom, then to the right to access the BlackBerry hub, which aggregates ALL emails/IMs/notifications in a single list (can be customized into groups). - Swipe from bottom left corner towards center hides on-screen-keyboard. - Top swipe displays app specific option/help/misc links. - 2-finger swipe from top revealed quick settings (wifi, flashlight, etc). No notifications here (they're in the hub)! - Not swiping, but it had a clean, single unified location for all app notification/permissions/etc which feels much easier than Android.
I feel if BlackBerry released the Q10 2-3 years earlier we would have had a totally different phone ecosystem today. I still miss it.
It's a pity more haven't experienced the useful aspects of BB10's interface (10.3.2 IIRC was when it received a much appreciated UI appearance update, fwiw).
I've tried Android, iOS, Windows Phone and BB10 is still my favorite. Windows Phone in particular was surprising in how unintuitive various of the gestures were in comparison.
As a side note, on their phones with a physical keyboard (which featured touch detection on the surface of the entire key array) text interactions were much improved. Finessing text selections was particularly easy compared to using the touch-screen. Double-tapping the keys (without depressing them) brings up the loupe and from there one can hold down Shift while gliding around the keys to adjust the selection, much like a laptop with a touchpad.
Swipe left to go back worked anywhere (you didn't have to start from the edge of the screen) and dynamically showed the page being pulled off the stack, so it was super discoverable. All of the swipe gestures worked this way—"peek" was core to the interaction model because it made users feel in control, and let them cancel an action by just dragging back to where they started.
The two-finger swipe from top was only to bring the system quick settings while in an app (the two-finger gesture was also only added late in the OS's life, at the behest of power users); the quick settings were available on the home screen with a single swipe. While in an app, a single swipe brings up the app's settings.
The only non-discoverable gesture was swiping the corner of the keyboard to dismiss it, and it was also totally useless. The advertised way to dismiss the keyboard was by long-pressing the space bar (there was an icon showing this).
On the home screen, swiping down gave you the system quick settings, and in an app it gave you the app's settings, so the two-finger gesture was just a power-user shortcut to the system quick settings while in an app.
Swipe left to go back was very discoverable, and worked differently than iOS or Android, because the entire OS was built around the idea of stacks of pages. Swiping left was just pulling a page off the stack (fluidly animated and cancellable, and you could start anywhere on the screen). There was also a back button on the left-side of the toolbar that you could tap to do the same thing.
Swipe up and to the right to go to the notifications Hub was also discoverable. The Hub was the left-most page on the home screen, so "up-right" simply combined the gestures into one fluid gesture; it was also totally optional.
512 x 342 x 1 bit color created some pretty fantastic usability.
I've wanted a modern consistent, monochrome interface for a while as a general computing interface.
I've been looking at the e-ink devices for inspiration.
Forced contrast, forced visibility, it all has to be apparent. I've been hacking lua for this holy grail for about 6 years now, before that in perl, then in C since around 2001 or so.
I've got foot pedals, midi controllers I use for general computing, lots of little hacks. Multiple 4k monitors in portrait mode, lots of hacking with arduino sensor packs. Still not there yet.
Interfacing is the current limitation in computing. I've got 128 cores, hundreds of gb of ram, and no good way to use it other than the current paradigms. There's gotta be something better
Spotify on Android is pretty awful at this point. Now I can't tap and hold to get to the context menu anymore, now I have to use the triple dot button. Why remove that? Usability is also pretty terrible. Why can't I load the list view of an album I have saved? What the hell. Same with entire playlists that I have saved and downloaded.
Snapchat (I wish I didn't have to use it, but it's the main for of communication a lot of my peers use) keep changing things constantly when nothing was every broken. Over the past three years, they've changed the order and number of tabs they have at least four times.
Google Photos on Android is also annoying separated IMO. Give me an order by date and an order by album/folder. Please just load the folder structure. I assume they do things the way they do to maximize use of their cloud storage, so it is likely intentionally awful for local images.
The official Reddit app is absolutely awful and slow. Reddit Is Fun (third party app) is, and always will be, my favorite Reddit experience. Clean and fast.
That was kind of ranty, but I just wish UI's were simpler on mobile.
A couple of examples getting in my way at the moment, the android (or nokia) phone app added a full screen "call your favorite contacts with just one tap" image to the favorites screen. I could do this until they added the obnoxious message, now I have to scroll down to even see them. The other would be netflix constantly AB testing me on whether to show the next episode button or jump back to the home screen, just make a decision, the constantly shifting interface is worse than either option.
The problem with flat UIs is that they're also in the middle of abandoning any conventions on what's interactable as well.
Ironically Windows circa 3.1 and definitely by 95 had this nailed: is it greyed out? 3D? You can interact with it. Not 3D? You can't. 3D but greyed out? It is contextually disabled.
Simple and clear at a glance. What that interface got wrong was the MDI motif - multiple document interface never really worked as well as Microsoft wanted, although if they'd made the leap of making it tiling by default they would've got there.
In my opinion, my interfaces are getting worse rather than better. I feel like a few years ago, a lot of the major companies hit a tipping point with UI optimization and realized a LOT of what they were doing was unnecessary (and perhaps even costing the business money). Anything that didn't clearly serve a purpose got removed - streamlining for a few core usecases.
I recently got an Android 10 phone, from a vendor I had never heard of: Ulefone.
I was coming from a Sony Xperia compact running Android 8 - roughly the same hardware, except not rugged. I presume Sony polished Android a little bit more than Ulefone did, but even taking all that into account, Android 10 was full of shockingly bad UI "decisions".
First: the Do Not Disturb icon in the pull-down thingy is a but when enabled a appears in the top bar.
Second: Pulling down the pull-down thingy once displays a row of 6 icons with no labels. Pulling twice displays 5 columns of icons with labels. It takes extra planning to rearrange the widgets in 5-column mode such that I get the 6 I want in the first row but also a logical grouping in 5 columns.
Maybe these are Ulefone-isms, but whenever I trip over them I imagine how hard Steve Jobs would have fired someone who put this stuff in front of him.
Just yesterday, I wanted to make a normal voice call to someone I usually contact via WhatsApp. When on their contact page, I couldn't tell which icon would make a WhatsApp call and which would make a PSTN call. The WhatsApp phonecall option appeared with the phone's "phone" icon, and the PSTN option had no icon at all. Both had text saying "voice call".
Oh, and don't even get me started about my Android TV. FFS.
I noticed a lot of UI problems like this when my parents changed from Windows Phone to Android and I had to help them. There are a lot of small actions that make sense if you used Android in the past (since they've been slowly introduced) but are completely bonkers to anyone picking it up now:
- To reject a call, swipe the "Accept call" icon down (this one is particularly horrible); - To enable Wi-Fi, bluetooth, etc. swipe from the top; - To dismiss a notification, swipe it to the side.
- most of those apps with the hidden interfaces have no business being on a pocket computer in the first place
If we stopped playing the game of maximising engagement, and returned to "practical usefulness" as the primary driver for application design, we'd probably make better apps.
We don't have to go back to skeuomorphism of the old iphones, but whenever I use my phone I have no idea what's tappable and what's not. There's even this trend now of not making it obvious what's even a text box or what's not. It /looks/ nice, but it's infuriating to use. And then you have the weird gestures that are completely undiscoverable. Like pulling down from the top right to get the utility menu thing. I mean, yeah, I know it's there, but I never would have actually discovered that on my own. Also now there's this trend of just hiding everything to make an app look minimalistic and simple even though it's not. So I have no idea what it can even do when I look at it. And I /still/ have no idea how to properly line up apps side by side on my iPad. I mean I kind of do, but I constantly forget, and worse, once I do have them lined up, it's hard to get rid of them. It's all insanely undiscoverable.
I wish UX designers would realize it's not all about being pretty, you have to actually give people an idea of what things actually DO. All the clunky old interfaces with the bevelled buttons and huge scroll bars and stuff might have been ugly as sin, but at least they weren't a constant confusion.