I cannot get over how bad the new #Mastodon UI is. I was quite positive on the mockups they shared previously and do like the fact that the compose window is floating and so I can see the post that I’m replying to. Except I can’t move or resize it. And, when I type a lot, the text field doesn’t get a scroll bar, it just pushes the top of the popup off the screen.
But it took me several minutes yesterday to find the reply button. That is not an exaggeration. Why? Two reasons:
First, I have been using Internet-connected computers now for over 30 years. In that time, almost everything I’ve used that has a ‘reply’ button (including the previous version of the Mastodon web UI) has used some variant of an arrow to the left to mark the reply button. I was looking for a left arrow and there is no such thing anywhere in the UI. Do not break established UI conventions for no reasons.
The other reason is not unique to Mastodon and is a result of ‘UX designers’ pushing everyone who had a basic knowledge of cognitive and behavioural psychology out of UI design. There is no visual cue about which things are click/tappable UI elements. Except when there is. For example, this compose popup has a blue border on the thing I can type text in and a button of the same colour for the publish button. But every other thing I can interact with in the popup is the same white-line-drawing-on-a-black-background style, whether it’s an indicator or a control. The reply button is also the number-of-comments indicator and there’s nothing to tell me that it’s a button. Note that UIs from the early ‘90s didn’t have this problem, it isn’t that we don’t know how to do this well, it’s that some muppets at Google decided to ignore decades of usability research and other people decided to copy them. If Google ran off a cliff, you’d follow them, wouldn’t you?
On top of all of that, the UI on my iPad screen (web browser full screen) now uses less than 60% of the width for the content. The side bar is massive, can’t be hidden, and is mostly empty space. It’s a web UI. I haven’t done web design seriously for 25 years and I know how to make them scale down to small devices. The only way you’d ever ship something like this is if you’ve never hit the ‘responsive design’ menu item in the developer menu and asked ‘what does my web layout look like on a small display?’ It’s literally under a minute to test a variety of display sizes.
A load of common operations now require additional taps (for example, marking all notifications as read, a thing I do multiple times a day, now requires a … and then another tap, whereas previously it was a single tap). This is what happens when you don’t actually measure UI use.
But, worst of all is the reason why this was inflicted on me. My instance admin did an update to get a security fix. Never, ever, ever ship security fixes and UI changes (even UI improvements) in the same release. Any UI change will negatively impact at least some users in the short term. By combining them you are training users to not apply software updates for security because they may break usability. After you’ve done that, every exploit of one of your users as a result of running an unpatched vulnerable version is your fault (big tech companies are guilty of this repeatedly. Don’t copy the worst of big tech).
EDIT: Oh, and a bunch of UI elements are now smaller than my fingertip, which makes hitting them on a touchscreen hard.
EDIT2: Oh, and the ‘share’ button is now using the icon other apps use for ‘forward message’ and not the icon that everything else uses for share.