Design is how it works, not how it looks. This article seems to mainly be talking about the "polish" of a design. There are more important principles which don't have anything to do with polish, such as not putting the Cancel button next to the Ok button.
After over a decade of people jumping into these discussions with this line, I’ve gotta push back: Design is also how things look, and how things look can be important.
Consumers care about how things look. If we dismiss presentation and drive people towards UX stuff every time it comes up, then the people we talk to are going to end up having good ideas that no one buys because the packaging is a mess.
Yes: If you have a pretty modal but it can’t be dismissed by clicking outside of it, that’s Bad Design. But when you’ve hammered in all those errant nails and built something that works well, often you look at it and go “I wish it weren’t so ugly”. And we do need books/resources to give people the building blocks they need to make an app that people will agree is “basically good-looking”. (And then hopefully more advanced books/resources about particular styles so people can develop their own stylistic voice)
More specifically there can be no separation between how something looks and how it works, they're bonded (and for good reason). There is no scenario where you can actually fully break the two apart. Any attempt to try harms one side or the other or both sides. How it works and how it looks go in tandem in all cases, they heavily influence eachother, either making the whole better or worse depending on how you go about creating for that reality.
Anybody telling you different is arguing from a pretty severe bias. If you're designing on the basis of how something works, and not also on how it looks at the same time, you're going to create a subpar outcome.
I'd also note that despite Jakob Nielsen's prominence nobody designs like he suggests. We should be open to the idea that beauty and delight may be more important than usability or features.
This reminds me of expert systems where use is so intense that discoverability is trumped by speed of input. Old DOS/ASCII based retail systems were often optimized for speed.
I imagine that because of the churn of people doing cashier jobs, there is little incentive for businesses to design pos systems that reward expertise over getting someone up to speed quickly.
Must be a complete and unfortunate coincidence then, that the richest tech company on the frickin planet rose to that prominence through "beauty", at least as their critics still like to call out.
If you’re selling a premium produce, then beauty can be justified by the premium price. But us should never be more important than the functionality. Never.
Even a Rolls Royce is a vehicle (and a damned fine one to boot) before it’s an art piece.
In B2B it's usually ease and speed of operation that's more important
SAP (everything), Workday (HR), Service Now (help desk), Archer (compliance), SailPoint (compliance), and other applications that have been inflicted on my miserable existence over the last 25 years of corporate IT; all B2B enterprise applications that I guarantee did not consider either speed or ease of use to be remotely important.
Your pain only proves my point. You know it is supposed to be better, regardless of how it looks. There are outliers who neglect the end users, usually because they are too big or well connected to be replaced.
I don't know if it actually does, maybe in theory, we would assume these companies would be incentivized to optimize for speed and experience but you can't use "the exception that proves the rule" when the majority would fall into the exception category. There have been countless diatribes about how in B2B the purchaser is not the user, so speed, user experience, and functionality are all at best second order priorities. The apps I name checked above all probably provide the base level required amount of functionality that covers the needs of a lot of large privately held and all publicly held US companies, they are looking for the corp equivalent of Wal-Mart shoppers not Nordstrom shoppers (this dove tails into penny wise/pound foolish quarterly earning mindset, corporate America is dumb AF.)
I wish more businesses would treat beauty as a function of a product just like all other “actual” functions of it, a valid part of the whole package. I know it won’t probably happen anytime soon, because “ROI when???”, just been thinking about it a lot after reading Beauty by Sagmeister and Walsh.
> How much of a premium are you, as a customer, willing to pay for the beauty?
Depends on the category of goods, but if I can afford it then I will probably choose something aesthetically pleasing to me most of the time. I can easily get by with an ugly screwdriver if it works well, but I would not like wearing bad-looking shoes.
Generally if I use something often, be it tools, clothes, guitars, utensils and whatnot, I try to find something appealing to my eye. Some people seemingly don’t care much about that, but it just so happens that I do. Paying a premium for the beauty relieves me from being very irritated about something I might not like.
Also, in my opinion, aesthetics, ergonomics and beauty sometimes all are side products of working hard on one of them. Beauty in tools and architecture and interfaces is not to be discarded since it makes our life more pleasing and tolerable. We could live in the holes in the ground, you know, if pure application of things to their intended purpose was all that mattered to us.
> How much functionality will you give up for the shinies?
I’m not sure something has to be given up at all, that’s the point.
If you've visited factories or other work places dominated by men, many of them go by the philosophy of zero attendance to neatness and cleanliness. Those are miserable places to work and even visit. Everybody working there are usually grumpy and miserable, including the boss.
Working all day in ugly software is like a mini version of this.
I don't think anybody considers beautiful software ad a premium, more that ugly software will not be considered at all because it can't be trusted.
Feel free to tease apart beauty and functionality to a roomful of engineers. I'm always up for the debate because everyone has their own perspective and it's usually interesting.
Everything has terrible ROI if you don't understand the "I" and aren't tracking the "R".
Alternatively, functionally doesn't matter if you miss a sale due to someone not liking the design. The first time someone uses/sees something is the most important time for them to like it.
It depends. For typical software and websites, beauty matters every single time: when you like something more and more and more every time you use it, to the point of increasing usage, recommending it, spending money and so on; and when you hate something so much that functionality is effectively reduced by avoidance, distraction, fatigue, rage quitting etc.
In all of this it's a matter of scale.
Products with 100 million users can amortize the costs over a much larger number of deployments. Even the smallest details become valuable at that point. Conversely, at a certain level of deployment, usability is not worth the time investment. Machine Learning researchers can frequently get away with a loose collection of Python scripts with a basic set of instructions that probably worked on their local setup.
Are they really an outlier, or just the best at what they're trying to do? I mean I guess you could always say that the best is an outlier since only one can be the best.
They're the best at what they aim to do. Again, if everyone did it or they were less unique then it would be less exceptional.
The point is, it's hard and rare to get into such a position. Yes, eventually there will be a new Apple, but not yet. So anyone *today* looking to perform well should probably be more practical.
How long is it since any vendor cared about usability and features? HCI is dead. The only thing that matters now is UX: optimising the software to maximise sales. And you're right. Beauty sells. But this is not an insight. It's been standard practice for years. And as an end user it sucks.
This is the first time I’ve seen someone on HN argue against usability in favor of aesthetics the form vs function design debate.
There is so much to say on the topic, books have been written arguing at length even. I would never argue for worse UX if I had a choice, there should be a baseline “good” visual design, but poor UX can and will sink your product in most metrics that matter in the business world.
> We should be open to the idea that beauty and delight may be more important than usability or features.
Oh, please no. We already have more than enough of that line of thinking. In software, especially, we see far too much pretty stuff that is horrendous to actually use.
I'll take the ugly thing that makes my life easier over the pretty thing that does the opposite every single time.
It was a long time I looked in that book but I hated it. Not because it was ugly, I like ugly. But the advice didn’t make sense. It’s been years sincy I thought of Nielsen, maybe I should give at a peek again.
Design like most words has a definition that’s generic so it can be applied as needed. There is no immutable rule when to use it.
The cone of shame my dog has right now “looks cool”; very sleek and streamline for a disposable thing, the designer surely was paid a premium, but the fasteners mechanics were poorly designed; vet tech said even she struggles with them and she puts them on dogs all week.
Design is how it looks and works as “designers” come up with both. The whole idea we can just put our foot down regarding definitions is not at all how reality works since nothing works on divine mandate. It’s relative.
"We talk about design often. At some point during any human lifetime, they will use the word design, and that's a big deal. Aside from 'the' and the 'a' and the 'an' in various languages, design is the fourth most popular word used. Before design was constructed we had the Mesopotamian era, and we all know how that was." -Reggie Watts, 2011
Conversely, A lot of time something looks good "because" it works well.
I had one old structural engineer spend a great deal of time trying to convince me that beautiful bridges were stronger than than ugly bridges. because our ideas of beauty are so tied to what works well. I am not entirely convinced, I have seen the sins some of these so called designers do in the name of "looking good" but I do see his point.
Many people (including me mostly) don't understand why their eyes feel something as "good-looking" or "beauty". It boils down to symmetry being a big part of it, and sometimes symmetry creates working solution. A bridge being the perfect example for that since you need to balance the weight between both sides of the bridge it's easy to get this while also "looking good". But I believe symmetry is not the only thing our brain accounts to beauty. I would love to know more about that topic.
I’d argue that the elegance of a design solution—engineers design things—is what the structural engineer was referring to. The next question is what is elegance in regards to a solution to a problem? Simplicity? Economy, both financial and technical? Aesthetic? The difficulty we have is that few people agree. When I studied industrial design in the early nineties, we were taught that design is merely the process of solving a problem. In fact, when dissecting a brief, the first goal is to establish the problem that needs solving is. The aim of a designer (or indeed an engineer) should be to incorporate all three elements that I mentioned. Sadly, those that struggle with the aesthetic, dismiss it’s importance out of hand.
People judge apps by how they look more than how they work.
If it looks professional and good looking they give it more credit and chances than it deserves. If UX is good but looks are not airbnb/apple wannabe they tend to distrust it.
I've worked as both a designer and developer and for the life of me I can't help but gravitate towards prettier looking applications even at times over more functional ugly ones.
It's a contradiction to what I "should" want as a developer and I'm very aware of this.
Form and function. The intersection is the qualitative property of subjective taste, an intelligence quality of designers who must balance engineering with art.
This criticism feels fairly ironic, since the first guideline at lawsofux.com is the “Aesthetic–Usability Effect: “Users often perceive aesthetically pleasing design as design that’s more usable” (https://lawsofux.com/aesthetic-usability-effect/).
No, it is not. If you're Steve Jobs then yes, but otherwise how it looks and how it works are usually two different job functions. People who are good at visual design are not usually knowledgeable enough to do functional design, and people who are good at functional design are not necessarily good at visual design.
Bold statement for something subjective. I think you are confusing design and art (from your own experience or misfortune). The processes of visual design have informed (or formalised) the design as a process in other fields. Artists have a style as a function. Designers (visual or not) have process. No one is great at everything. Mediocre designers are either too visual or not at all (especially the latter), in my experience. Good to great designers grasp both and have breath. Even the ones that don't have art as a function can direct, steer and brief the art of a project (or be resourceful with it.) But you can't have design without process.
My comments are based on experience working on projects where some designers (who went to art school) heard Steve Jobs say "design is how it works, not how it looks" and then decided that they own the "how it works" part. The result, from what I have seen, is disastrous.
Functional design (how it works) and visual design (how it looks) is really two different job functions. You don't need an art degree or even be good in art in order to design the functionalities or even interactions of a product. At the same time, being good in art and designing cool looking UI doesn't make you qualified to design the functionalities or interactions of the product. Not even close.
Both job functions are needed to build a good product. In rare cases one person may be able to do both.
"In most people's vocabularies, design means veneer. It's interior decorating. It's the fabric of the curtains of the sofa. But to me, nothing could be further from the meaning of design. Design is the fundamental soul of a human-made creation that ends up expressing itself in successive outer layers of the product or service."
Design is not just one thing or another. It happens at each layer. From deciding how many options you want to present to the user, to how they will be presented. Or deciding how to deal with errors in the backend, versus reporting them in the front end. Design decisions are made the whole way through.
I think this is visible with lots of Apple products because some people complain that they aren’t flexible enough. But reducing configurability is as much a design decision as the colour of the icons. (And sometimes more challenging)
> Design is not just one thing or another. It happens at each layer.
I think we are in agreement. "How it works" is design. "How it looks" is also design. Sometimes, but not usually, one person may be able to do both types of design.
UX often involves research and customer interaction. UI is more straight up visual design, informed by the UX research. The same person might not do both. Do you think they should?
Yes. Yes, they should. A person who does UI and doesn't have first-hand experience on what customers want and do is not a UI designer. That person is a dribbble illustrator.
I remember clearly the first time I ever heard the term “UX”. It was condescending explained by some guy from Google to a quite technical audience of telcos, many years ago. For reasons I couldn’t explain, it pissed me off.
Apple famously did many years of intense user testing to develop their HIG (and maybe still do?). I’m pretty sure xerox did too, and all the other UI researchers many years ago. Maybe even Microsoft did :)
In any case, it contradicts your claim, since all this user research was way, way before UX was a thing.
Honestly I just got the feeling that the phrase UI had become stale and UX was just seen as a way for a new generation to put their mark on the world.
The 1985 edition "includes e.g. case studies (useful!), and an extended discussion of Jung's theories of intuition and how they should influence your designs (!!)"
The dictionary says it means "a plan or drawing produced to show the look and function or workings of a building, garment, or other object before it is built or made."
So it is both "Look" and "function". Claiming looks aren't part of it is incorrect.
But if you skip the looks in your design, you'll end up with a product that works worse. It may not look rational, but then humans do not have a 100% rational behaviour.
Any product designer is expected to be knowledgeable about both visuals and ux. There are huge benefits to having people on the product team that can research, assess and design solutions.
Odd, when I first clicked that second link it opened a page that was virtually unreadable on a mobile device (Android Chrome) - the text literally curved off the left hand edge of the screen. Which made the first sentence "The following principles are fundamental to the design and implementation of effective interfaces[...]for[...]mobile devices..." suggest there was little point reading on. But on reloading in another tab it was basically fine (though I'd argue still not optimal).
Well yes, and worse, after opening it on a desktop browser, it still looks pretty average, and the way the background brightens as you scroll down is very distracting.
I think it's both. Interior designers are primarily interested in aesthetics. Same for the majority of famous fashion designers, who are usually not focused on making utilitarian clothes. It seems like most peoples' definition of design would include the work in those fields. UX is a better description of the aspect of design that cares about functionality and not aesthetics.
I think we're getting confused by fuzzy and overlapping definitions of different scope.
Absolutely, design is also how it works. However, how it works is also very much engineering. In fact, I'd argue that the overlap is even stronger there.
More like this:
https://lawsofux.com
https://asktog.com/atc/principles-of-interaction-design/
https://www.nngroup.com/articles
I recommend prototyping the flow/feel of the app before working on the polish, or the functionality:
https://principle.app/