You're Overthinking It
engineering.gomiso.com
You're Overthinking It
1–10 of 55 posts
Re: You're Overthinking It
#2Re: You're Overthinking It
#3[...] it also depends on where you are on Maslow’s hierarchy of needs. The lower on the pyramid your product is, the crappier it can look. If your product is core to helping people make money, pirate movies, or sell your useless couch, you don’t need a designer. But if you’re high on the pyramid, ugly/clunky UI makes it impossible to for people to see your vision.
Never heard this advice in reference to Maslow, but it's truth! I should print this up on cards and give it to a load of my tech and designer friends.
The entire "It's like [Craigslist/Amazon/eBay]... but with a beautiful design/UI!" fallacy falls to its knees with this paragraph.
Re: You're Overthinking It
#4Re: You're Overthinking It
#5It's a good point but there's a huge field of potential software and opportunity out there that we programmers are not the users of. Who should build it then?
Re: You're Overthinking It
#6Re: You're Overthinking It
#7http://www.forbes.com/sites/nathanfurr/2011/11/18/nailing-th...
Clay Collins also advocates for a similar approach that he calls the "interactive offer":
Re: You're Overthinking It
#8Re: You're Overthinking It
#9It's a good point but there's a huge field of potential software and opportunity out there that we programmers are not the users of. Who should build it then?