Or, in business terms, beauty has terrible ROI.
Look at almost any premium product and the premium that is being paid for is in the beauty. Rarely is it in the actual quality of the product.
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.
Even a Rolls Royce is a vehicle (and a damned fine one to boot) before it’s an art piece.
When functionality is a given like it is for a kitchen toaster, we can argue the presentation and style is more important.
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.
Beautiful, not in the least. Thanks to the cameras (a functional feature) I need to have a fugly case wrapping the entire thing.
It feels like a variation of learned helplessness, watching someone fumble with a Stripe terminal.
> 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 make 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.
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.
Everything has terrible ROI if you don't understand the "I" and aren't tracking the "R".
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.
That’s not the definition of UX.
UX is multi disciplinary, an umbrella term for many things, eg design research, IA, HCI, UI Design, …
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.
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.
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 think that a lot of software is inherently low (or even negative) value and thats why shiny wins.
Could easily be dreaming tho
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.
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’ve gotta push back: Design is also how things look
To synthesize these two comments: How it looks is a huge part of how it works.
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.
It's a contradiction to what I "should" want as a developer and I'm very aware of this.
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)