Lessons from a Design Legend (a before-and-after)
giftrocket.com
giftrocket.com
I have one major issue, though. Their original "Redeem" button was ugly and garish, but it looked like a button. It screams out "click me. CLICK MEEEEEE".
The new "Redeem" button is gorgeous, but it's actually a step backwards in terms of usability. First of all, it doesn't look like a button. Am I supposed to click? Where? Are the little circles also buttons? Speaking of the little circles, they really steal the show. They're so colorful and attractive, that you don't even notice the central circle - and, critically, you don't read the text that says "Redeem". I had to look at the pre-overhaul image to get a reminder of what I was supposed to be doing at this screen.
1. It's very de auteur. If you watch it in contrast with every other Mike Kus design as beautiful and awesome they are you'll see that this design is not that original and looks just every other Mike Kus design. 2. The mobile app looks like a giant bueautiful useless splash screen. It has a lot more graphics and details and yet it conveys a lot less information that the 'before' design. For starters, that the damn button is clickable and it will redeem something from Mario's Pizzeria.
Or am I just becoming an old cranky designer?
1. For us, that's exactly what we wanted. It's Mike Kus' style applied to our product.
2. The mobile app actually looks quite different. If you visit www.giftrocket.com on your phone, it's a functional version of our website. The phone app comparisons were of one specific screen within the redemption flow.
As a user I quickly get suspicious when there is a lot of style. I quickly pick up the difference between the veneer and the inner wood, so to speak, and as a user, the first thing I look for, perhaps subconsciously, is the way through the veneer. I need to use buttons and fields and read the important stuff, all the way trying to ignore the style -- the baroque embellishments, the clever icons, the careful colour balance -- which is functionally superfluous.
The main problem with style is that it obscures and dimishes the value of information. Good UI design is functional and elegant and avoids stylistic embellishments. The old design was simple and to the point. The new design is very busy and unsimple. It reminds me of the kind of excessively flowery, explosive embellishments typical of indie festival poster designs that was in vogue the last 2-3 years, but has been going out of fashion, like this one: http://bit.ly/nzJaR3. Another problem with style is that it's easy to seem derivative and as though you are trying too hard. Nobody could fault the simple, apparently genuinely sincere ambitions of your old design. Now your design is ambitious in a kind of pompus way, and easier to shoot down.
Yet another problem with style is that it can seem to imply a level of information quality. It's difficult to articulate, but look at the third section of your article, the way restaurants are presented. Instead of the old, close-to-the-database look, we now have something out of a coffee table book. The level of polish seems to imply that the information itself has been carefully harvested, edited, quality-checked and polished. But in your case (I'm presuming), some entries are probably more rougher than others, and the surface polish is not representative of the actual content.
Just my few humble cents.
Simple and to the point designs often lack personality. And if you're trying to build a brand your site design needs to have a point of view.
For example, the minimalistic Japanese "no-brand" (it's very much a brand) MUJI has very little actual style, but lots of design. It's simplistic and function-oriented. And yet the personality is often immediately recognizable. IKEA is often minimalistic, but has a significant brand presence without applying a whole of style.
Style is like makeup. You're not making a cake, so you have to be careful about how much you apply. Too much makeup and you come across as desperate or insincere. Too little and your wrinkles will be showing. I don't know how far one can stretch this metaphor -- you get the point. :-)
(Iconography is hard. These days kids are probably asking about those weird icons in toolbars that they don't recognize, and moms and dads need to explain how back in the day we used quaint things like floppy disks and clipboards and stuff; soon they will have to explain about envelopes and magnifying glasses. Apple, meanwhile, just moved iCal back a decade by introducing a leather-bound framing metaphor for the entire app.)
OTOH, it is amazing that some designers just repeat the same motifs in every work they do, and make a career out of it. Another one is Michael Schwab. I love his work but it is all very samey: http://www.michaelschwab.com/portfolio_posters.html
And while I wouldn't call Mike Kus a design legend (I'd reserve that for peeps like Jonathan Ive, Dieter Rams, the HFJ duo... basically those who have a profound effect on the industry, peoples lifestyle and/or the craft) he definitely is one of the best web designers out there.
My takeaway: Don't go to Designer News to read opinions about Hacking.
The issue here (at least on the front page and mobile screen) is the Information architecture. Putting the graphic first before the tagline pitch is not very effective (the graphic is a visual aide not the other way around) and a form instead of a call to action button doesn't also work. The next set of info is too far below the fold, etc.
I can see that its layout is inspired by the Facebook logged out home page. But this is not a household-known social network but an app that does one thing and a bunch of extras so the goal is not to dazzle then cause action but to inform to cause action.
In my humble opinion this exercise took some important aspect of the product backward in terms of informing users more efficiently and I would imagine the load times (for the website) also adversely affected. Im not saying you should scratch this redesign but refine this version more and hopefully iterate to one that is pretty and informative (and faster!)
A few specific examples...
1. I find the point about contrast in the article to be completely false. There is a more muted palette but I disagree that brown on black is higher contrast than red on white.
2. The mini-circles around the redeem button are just distracting from the primary call to action on that screen, do they do anything? Why would you trade the location name for buttons that don't do anything?
http://o7.no/pwkxA9 [png]
3. The homepage no longer has a single clear call to action ("send a giftrocket"), if you increase the number of possible users paths on a page it will almost always lead to reduced conversion. Your homepage has 19 things I can click on above the fold. (For point of comparison Square and LivingSocial have 5, Groupon has 4). Does anyone give a GiftRocket by clicking on the categories and browsing?
background-color: #F7F2DD;
color: #4F5354;
Uh huh.(Kind of ironic for a post which includes the emphatic lessons "When it comes to contrast: go big or go home!" and "Pay attention to typography".)
Enabling Javascript for the page helped; perhaps that's how the "text-shadows [Mike applied] to nearly everything" so that "the text felt more vibrant" were implemented?
So I would add a lesson #7: don't rely on fancy Javascript effects for something as basic as readability.
It's a good discussion of how to re-see a site, though - definitely something that is important to do from time to time.
The second design did make some good changes, particularly larger pictures of food, however it comes off as too design heavy and lacking clarity in several areas.
Overall I feel there is more clarity with what you want me to do in the first design.
Edit: You have to view the work as a whole when comparing the designs side by side. There were several important parts of Mike's design that were cut out to fit the blog post that actually bring a ton more clarity.
Here's a litmus test for those who like the newer design better: would you want your OS to look like that? Not everything should look like an OS UI, of course, but take a few moments to think about why you wouldn't want your OS and most of your other day-to-day applications to look like the "after" design.
FYI, I'm not running anything particularly unusual, and I have never seen that kind of effect on a page before with this browsing set-up. Either (a) you've been "0wn3d" or (b) you really need to tone down the scripting to an acceptable level or (c) you're probably going to put off a significant number of people who might otherwise be interested in your site.
I have not heard of them. Also, their blog site layout is quite flawed. The text hits the left edge of the page at 1000px width. First, text should never hit the left side of the page. There should absolutely always be a margin of no less than 8px, but nearly always should be at least 0.25". Second, 1024px is more than half of a 1920px width screen and the site only looks proper at about 1280px width. This is too wide.
We (people using computers) have been forced into wide screen aspect ratio displays because of the need to show movies. Fine, that is the way it is. But this means that common use is to have two pages or tasks side by side. Full screen for tasks of reading produces lines that are much too wide to scan properly. Web pages should not require more than 960px for basic reading. The 960px includes the window scroll bars and frame if present, so the actual page text should be slightly smaller.
Do not design windows that expect 1024px or 1280px width, and do not design windows where the text crashes into the page edge when resized. Both these are very amateur hour mistakes. Therefore, it is inconceivable that the people at this firm are "design legends".
Is this common? I've never known another person who does this outside a dual screen setup.
1. What is the width in inches of your display and how many pixels.
2. How many inches from your eyes to the screen in a normal working position?
3. Is your browser set to full screen width right now?
4. How many words per line are there across the screen in this page of hacker news on your set up?
It's why I've considered adding j/k support to my blog. It wouldn't be worth the effort for most things other than a tech blog.
http://psychology.wichita.edu/surl/usabilitynews/72/LineLeng...
I think they are calling Mike Kus a design legend, who taught them these six lessons.
Black on weird textured background for the body? do not use textures for background - like - ever - if you're going to write text on it
Then gold text on cream again.
Design legend much?
The rest is ok and there's some actually good tips but what I listed is totally noobish.
the reason startup websites look like the 'before' is because for whatever reason, everyone's told that there's this certain blue that projects confidence and whatever. the background is white and the text is #444 because of another mandate from heaven (h&fj) and so forth.
The reality is that while maybe black on 'weird textured background' may be technically harder to read than black on white, it's nonetheless legible. Somebody made the point that what really matters is whether this new site converts better. Whatever.
At some level, design is a matter of taste. They like their new site, you don't. Agree to disagree, but it's not like these things are 100% set in stone. I mean, everyone used to think fraktur was highly legible but something (tschichold?) eventually changed. Who knows.
It's all fashion (subjective).
What matters for readability is value contrast, not hue contrast. In fact, in extreme cases, too much hue contrast can make for less readability because different colors have different wavelengths which can cause them to be slightly out-of-focus on your retina:
http://amazing-space.stsci.edu/resources/explorations/ground...
Websites like this are really design products. If it's not graphic design, it's service design. The technical stuff is comes second.
Brown background.
Presents!!!
Brown sky.
Brown favicon.
Spot the odd one out.