Live data from Hacker News

Material Design Color Tool

material.io

51–60 of 95 posts

Re: Material Design Color Tool

#52

Earlier quoted context omitted.

Rational, practical people have always been quick to dismiss aesthetics in favour of functionality, but it turns out it's actually pretty important. People will use the ugly, functional thing if they have to, but they'll leave if they get a chance. I think this dynamic alone explains a large part of the success of a number of SaaS apps priced as is often advocated here to allow individual managers to buy it on a corp…

I've seen the opposite as well: ugly looking terminal or DOS based but very productive software was replaced with spiffy looking windows or web based software that was slightly slower or unable to keep up with the type-ahead of the users and this led to huge disappointment. I'm firmly believe if it doesn't work it doesn't matter how good it looks and if it works but looks bad that's better than the reverse. Then once…

It's not a dichotomy. I'm arguing for the importance of both, not either-or. Obviously, a thing that doesn't work, doesn't work, regardless of how pretty it might be.

> Then once you've figured out what to build you can always make it look pretty.

That's a lot harder than it sounds. No, of course you don't commission a big fancy design before you know what the thing should do, but you equally can't just build an ugly, but functional thing and throw lipstick on it five minutes before shipping (or after - activities schedules for when the thing is 'done' have a nasty tendency to not happen). Both, in parallel, at its time, not either-or.

Re: Material Design Color Tool

#53

Earlier quoted context omitted.

Rational, practical people have always been quick to dismiss aesthetics in favour of functionality, but it turns out it's actually pretty important. People will use the ugly, functional thing if they have to, but they'll leave if they get a chance. I think this dynamic alone explains a large part of the success of a number of SaaS apps priced as is often advocated here to allow individual managers to buy it on a corp…

I've seen the opposite as well: ugly looking terminal or DOS based but very productive software was replaced with spiffy looking windows or web based software that was slightly slower or unable to keep up with the type-ahead of the users and this led to huge disappointment. I'm firmly believe if it doesn't work it doesn't matter how good it looks and if it works but looks bad that's better than the reverse. Then once…

You're comparing apples with oranges.

Terminal/DOS-based software isn't ugly, it's just a different interface (GUI vs. non-GUI).

Of course some technical people that know what they're doing will enjoy using the command line because you don't have a GUI that gets in the way, but using this fact to "prove" that people like ugly software better doesn't make sense—it's just a bad example.

Re: Material Design Color Tool

#54

Earlier quoted context omitted.

Rational, practical people have always been quick to dismiss aesthetics in favour of functionality, but it turns out it's actually pretty important. People will use the ugly, functional thing if they have to, but they'll leave if they get a chance. I think this dynamic alone explains a large part of the success of a number of SaaS apps priced as is often advocated here to allow individual managers to buy it on a corp…

I've seen the opposite as well: ugly looking terminal or DOS based but very productive software was replaced with spiffy looking windows or web based software that was slightly slower or unable to keep up with the type-ahead of the users and this led to huge disappointment. I'm firmly believe if it doesn't work it doesn't matter how good it looks and if it works but looks bad that's better than the reverse. Then once…

It hugely depends on the target user group: admins don't mind about an 'ugly looking ... but productive software', but non-IT users mind a lot, and for them it has a significant effect on usability. It can only be '_very_ productive' for the target group, when it is also well-designed for them.

Re: Material Design Color Tool

#55
post #30

Earlier quoted context omitted.

take a look at the drink buisness. the look of the bottle is very important. you can argue its actually more important then whats in it.

That's confusing branding with functionality.

No, he's right.

It's perception.

If you have an ugly bottle it doesn't matter if your wine is good, because most people won't get to try it.

Re: Material Design Color Tool

#56
Really cool.

The only problem I have with material design is that lots of apps just look the same, and some people _do_ confuse Google stuff with apps that use material design, thinking they're from Google.

Much better than all apps looking like Bootstrap's default theme, though, which is a popular alternative to loading a material design theme with a palette you picked.

Re: Material Design Color Tool

#57
post #26
post #20

Earlier quoted context omitted.

As a user it's super un-intuitive, though. At least how gmail, calendar, maps and other google apps are on Android at the moment. I mostly click and pray.

It's interesting that lots of people on HN say the same thing: I don't know how to perform an action; there are no affordances in the UI. But Google is a data driven company and they must, surely, have scads of data on this. They must know what their users are trying to do and how they're trying to do it, so why are Google interfaces so hard to use?

They still use their mighty data to show me ads for things I've literally just bought, I do sometimes wonder if all data is even.

Re: Material Design Color Tool

#58

Earlier quoted context omitted.

That's confusing branding with functionality.

No, he's right. It's perception. If you have an ugly bottle it doesn't matter if your wine is good, because most people won't get to try it.

The very best wines and the $2.95 stuff are in essentially the same bottle.

Re: Material Design Color Tool

#59
post #48

Earlier quoted context omitted.

Rational, practical people have always been quick to dismiss aesthetics in favour of functionality, but it turns out it's actually pretty important. People will use the ugly, functional thing if they have to, but they'll leave if they get a chance. I think this dynamic alone explains a large part of the success of a number of SaaS apps priced as is often advocated here to allow individual managers to buy it on a corp…

Would you buy WinGrep?

For myself? No. For a non-technical end-user that for whatever reason needs grep-like capabilities? Yes.
Post reply on HN