←back to thread

917 points cryptophreak | 1 comments | | HN request time: 0s | source
Show context
squeedles ◴[] No.45761639[source]
Good article, but the reasoning is wrong. It isn't easy to make a simple interface in the same way that Pascal apologized for writing a long letter because he didn't have time to write a shorter one.

Implementing the UI for one exact use case is not much trouble, but figuring out what that use case is difficult. And defending that use case from the line of people who want "that + this little extra thing", or the "I just need ..." is difficult. It takes a single strong-willed defender, or some sort of onerous management structure, to prevent the interface from quickly devolving back into the million options or schizming into other projects.

Simply put, it is a desirable state, but an unstable one.

replies(22): >>45761688 #>>45761787 #>>45761946 #>>45762556 #>>45763000 #>>45763132 #>>45763419 #>>45763515 #>>45764215 #>>45765589 #>>45766183 #>>45766281 #>>45768514 #>>45769691 #>>45771196 #>>45771307 #>>45771846 #>>45772026 #>>45773411 #>>45773951 #>>45776266 #>>45779651 #
PaulDavisThe1st ◴[] No.45761946[source]
Good points, but to add to the sources of instability ... a first time user of a piece of software may be very appreciative of its simplicity and "intuitiveness". However, if it is a tool that they spend a lot of time with and is connected to a potentially complex workflow, it won't be long before even they are asking for "this little extra thing".

It is hard to overestimate the difference between creating tools for people who use the tools for hours every day and creating tools for people who use tools once a week or less.

replies(2): >>45762164 #>>45764070 #
galagawinkle489 ◴[] No.45764070[source]
And why exactly should free software prioritise someone's first five minutes (or first 100 hours, even) over the rest of the thousands of hours they might spend with it?

I see people using DAWs, even "pro" ones made by companies presumably interested in their bottom lines. In all cases I have no idea how to use it.

Do I complain about intuitiveness etc? Of course not. I don't know how to do something. That's my problem. Not theirs.

replies(1): >>45765044 #
Qem ◴[] No.45765044[source]
> And why exactly should free software prioritise someone's first five minutes (or first 100 hours, even) over the rest of the thousands of hours they might spend with it?

Well, if people fail at that first five minutes, the subsequent thousand hours most often never happens.

replies(2): >>45766524 #>>45770238 #
array_key_first ◴[] No.45766524{3}[source]
The inverse is also true. If you prioritize the first five minutes, your software is worthless in any industry that matters.

And that's why designers are using Photoshop and not Microsoft paint.

replies(1): >>45769618 #
csin ◴[] No.45769618{4}[source]
See, I feel this is where programmers just don't "get" good UI design.

Photoshop is good UI design. A normie can use photoshop the same way they use MS paint.

Albeit it just loads slower.

A normie doesn't need all the bells and whistles. They can just use photoshop like a glorified MS paint.

You can't do that with GIMP. It's actually really fucking annoying, if you try to use GIMP to do a MS paint job.

replies(2): >>45770897 #>>45776464 #
array_key_first ◴[] No.45776464{5}[source]
> Photoshop is good UI design. A normie can use photoshop the same way they use MS paint.

This is just straight up not true. You're only saying this because you, presumably, have used Photoshop.

It has a million buttons, layers are a thing, there's a million tools, etc. No, they can't just pick it up because it's complex software for a complex problem domain.

Maybe you disagree. Okay. Pick a different example. 3D Max? Why aren't studios using Microsoft Paint 3D instead of 3D max?

replies(1): >>45779733 #
1. csin ◴[] No.45779733{6}[source]
"It has a million buttons, layers are a thing, there's a million tools, etc. No, they can't just pick it up because it's complex software for a complex problem domain."

See this is the thing that software devs don't "get" about UI design.

It's the exact thing the original author is trying to communicate.

You CAN have a powerful tool. And still have it be user friendly for normies!

You hide away it's complexities. So it's not INDTIMIDATING for new users.

You know what. I'm going to reinstall gimp. Just to prove my point.

Let's compare photoshop with gimp.

Before I begin, let me preface. Modern photoshop is an enshitified piece of garbage. I would never use it.

But this is nothing to do with enshitification. That's a whole different thing.

Ok let's start:

- I grab a random image from imgur. Copy paste. Ctrl-V. Both apps passed the test. I was a little worried gimp couldn't even do this.

- On load this is what photoshop looks like: https://imgur.com/a/3uYsm2h

- On load this is what gimp looks like: https://imgur.com/a/DnPcRTc

First impressions:

- GIMP is ugly as fuck. It looks outdated. There's information overload on the left side. Too much shit happening. Too much text squashed together. INTIMIDATING.

- In contrast, photoshop has a more minimalist look. There is a "Layers" window on the right. New users don't need to touch it.

- There is a "Size & Position" window. This is key. Notice how there's only 3 things inside that window. Notice how it's not squashed with all the other shit on the left. Think about that. Why did the designer do this? Because those 3 things are what 90% of normies are looking to do.

- This is exactly what the original author was talking about, with the TV remote. The most common operations should be sectioned off at the top of the remote. Similarly, the most common operations in photo editing should be sectioned off, in clear view.

Ok, Step 2. Let's try and crop this image. A common operation:

- Photoshop. Click the crop button. Shows you a bit more complexity in it's settings. You don't have to touch it. It gives you a helpful grid UI: https://imgur.com/a/tLjL6en

- And then it has a blue "Done" button at the bottom. Finished easy.

- GIMP. We start with a brush by default??? Whoops I accidentally drew on the picture. I didn't want to do that. Thank god I know ctrl-Z.

- So it's that cross thing right? That's the move button. Nope that's not what I want to do :(

- It must be the one next to it. The rectangle. Ok, some random corner thingies appear in the corners. I click on one of the corners. The image gets split into two. But now what? WTF do I do now: https://imgur.com/a/f7TTHJs

I can go on and on and on and on, criticizing gimp's terrible UI design. I hope, the little I have demonstrated, is a tease into what UI design is really about.