Remember the computer UI in Minority Report? Yeah, they can do that now.
When you can afford a personal secretary to keep track of your every need, a mobile phone is basically a piece of jewelry, much like a wrist watch or pocket watch of by-gone days. These are single-purpose devices that are a fashion statement, more form than function. Taking this approach, focused on the voice aspects of mobile phones, Aesir, a design firm in Copenhagen, has designed the phone to go with your Rolex.
Fitted with a sapphire crystal, metallic-coated ceramic antenna, and keys that are individually screwed on by jewelers, designer Yves Béhar (his SF-based fuseproject firm designed the Jawbone headset) give you a phone as a work of art. No camera, no email, no internet browser, just a simple object of desire, purpose built to receive hush-toned murmurs from your Swiss banker or to whisper sweet nothings to your mistress in St. Tropez.
While they have stayed away from anything as gauche as a Facebook or Twitter client, you do get bespoke icons, original typeface, and ringtones composed by Vietnamese-Danish ‘master of the upright bass’ Chris Minh Doky.
Please pass the Grey Poupon.
The money shot from yesterday’s Yahoo Research’s Like Log study is the social activity graph below showing how this activity drops off a cliff after the first 24 hours.
Looking at over 100,000 articles across 45 big media sites over the course of three months, Yahoo researcher Yury Lifshits found that a vast majority of the Facebook Like and Twitter Retweet activity. Broadly, 80% or more of the activity takes place during the first 24 hours following the posting of a story. No surprise here, News is about New.
The conclusion from Yury makes is that sites that put out more than one story a day actually run the risk of splitting their traffic if they can’t double it. Each additional story/day diminishes the return and may contribute to burnout of your audience. This runs counter to the leaked AOL way memo pushing for quantity over quality.
Gawker Revisits the Front Page
Gawker famously underwent a redesign that reinforces the conclusions made by the Yahoo research. Look at the redesign before and after and you can plainly see. The image below is their traditional “blog” output which presents the latest story at the top with newer stories pushing the older ones down the page. The default Popular Now column on the right gives some counter-weight but otherwise it’s the standard, reverse chronological layout.
Now contrast this with their new look below. Notice how much more emphasis is placed on the images. This view is called their “Top Stories” view and they’ve taken away all timestamps on the stories as that is not the point of how things are laid out. This layout has an editorial touch to it, the Gawker editors are putting stories in front of you they want you to see.
Nick Denton, the founder of Gawker, posted at length on the thinking behind the redesign.
We need a few breakout stories each day. We will push those on the front page. And these exclusives can be augmented by dozens or hundreds of short items to provide — at low cost — comprehensiveness and fodder for the commentariat. These will typically run inside, linked by headlines from the blog column, so the volume doesn’t overwhelm our strongest stories.
A prominent “splash” slot on the home page — taking up the two-thirds of the page — can promote the most compelling gossip and scandal. But it also provides the opportunity to display our full editorial spectrum. The front page is our branding opportunity. It’s a rebranding opportunity, too, a way to demonstrate intelligence, taste and — yes, snicker away! — even beauty.
Back when I was selling the idea of blogs to media companies, I remember saying to them that the front page is dead and that people were coming in the side door to their sites via shared links and pointers from the search engines. This was why it was important for them to make sure each page could stand on it’s own as its own front page for their business.
It seems as we have come full circle with the larger blog sites now focused back on the front page, picking favorites to be their star headline stories for the day. Are we giving up on social mediation to solve the information filtering problem? Are we going back to a world where we start each day with a collection of bookmarked top sites we visit daily? Are we going back to appointment television? Do we abandon the firehose feed and stick to just the top stories?
Stumbled across a quick and dirty side project that uses Facebook’s social graph api to pull your newsfeed and present an alternate display. Try it yourself at Facebook-me.com.
Sometimes it’s the simple things. Why not a dual purpose phone charger, phone mount for your bicycle? Stay above 7.5 mph and you’ll charge your phone at the same rate as if you plugged it into the wall and you’ll be able to enjoy free turn-by-turn navigation.
Launching first in Kenya where it’s really needed but also coming to the first world sometime hopefully soon.
My wife just got back from Japan and picked up the latest brochure from NTT Docomo. As a member of the very desirable young female demographic, she’s always been pestering me that Nokia should focus less on whiz-bang geek features and more on the phone as a fashion statement.
I would agree and, in that vein I present to you this year’s Summer collection from docomo, part of their “style” series.
Up first is the Emilio Pucci phones featuring the trademark geometric shapes of that famous Italian designer. These phones are made by Sharp. Check out the video where the announcer is impressed with the front-facing camera that can be used as a mirror!
FrancFranc is a Japan-based interior designer. Their phones are made by NEC. The main features of this phone are a keypad with a unique LED lightshow when you flip it open and custom designer wallpapers that come pre-installed which you can see on the video.
NY handbag designer kate spade makes an appearance with the signature two-tone finish on the outside. This phone is made by Panasonic and features an “eco-mode” that turns down the display lighting and increase battery life. A squeeze on the sides of the hinge opens the phone and a unique pink LED “illumination” on the front cover activates when you fold the phone shut. The bubbly Tokai Walker reporter is once more on the case.
OK. It kills me that this isn’t a Nokia but I guess Sharp is going to see what they can do to interpret the marimekko brand as a keitai. The phone features the signature Unikko pattern with matching wallpaper inside and colorful treatment on the buttons inside. Sharp has also taken the time to outfit the animated sheep that walk across the screen into marimekko patterns. Our video announcer pronounces this phone, kawaii.
British interior designer Conran burst onto the Tokyo designer scene a couple of decades ago with a splashy book launch and showcase store in Shinjuku’s hip Park Tower complex. The brand holds sway and LG has worked with Studio Conran to produce this phone. This phone goes out on a limb by not going with the flip-phone form factor deciding instead to look at the ergonomics of the phone. It’s gentle curve is so that it can easily fit in your back pocket and hug your face. Coming in Brown, Black, and Dark Red, I’m thinking this phone is targeted for the older, thick rimmed glasses type that tends to prop the phone on their shoulder while sketching notes. The Tokai Walker crew spends most of the video analyzing the design before they even turn it on.
I’m a big believer in hacking together a working prototype to demonstrate product ideas. Powerpoint mocks basically put a shiny gloss on a paper sketch and because it’s not real, generate endless debate where no one is really speaking on authority because the product doesn’t exist.
Once you have a prototype the debate becomes substantive. Prototypes trump PowerPoint every time. Building a quick prototype is a way of sketching an idea – the emphasis should be on quick on dirty – get the pieces working with real data to see how things move, that’s it. Expect reactions and expect that you’ll need to tear it apart and redo things, that’s ok – expect that people might hate it and you’ll throw it away. Because of that, don’t invest too much time or ego into your prototype either, it will change, guaranteed. In this sense, churn is good.
This is why I really enjoyed Paul Buchheit’s post Communicating with Code where he writes about how both GMail and AdSense came together.
Of course none of the code from my prototype ever made it near the real product (thankfully), but that code did something that fancy arguments couldn’t do (at least not my fancy arguments), it showed that the idea and product had real potential.
The point of this story, I think, is that you should consider spending less time talking, and more time prototyping, especially if you’re not very good at talking or powerpoint. Your code can be a very persuasive argument.
GMail & AdSense were born from working prototypes, not PowerPoint. Whenever possible, try and avoid PowerPoint for product design, unless it’s for art.
What follows are notes from a session I attended at the last Web 2.0 Expo. While a few months old, the notes here are still very relevant. As a Nokia employee, some may think it strange for me to blog about how to develop for the iPhone but I think not, the priciples I share here apply to all mobile developers.
The presentation was given by Toby Boudreaux. Point of clarification before we begin. For those unfamiliar, an anti-pattern is a play on design patterns which are re-usable design components that emerge to become commonly understood elements used in User Interface design. A common user interface anti-pattern is the hover text box that obscures an otherwise important part element of the user experience.
On to the iPhone UX Anti-Patterns from Toby’s talk
Billboards & Splash Screens
While it your logo may look cool in all it’s glory and scrolling credits for everyone on the team including the office dog is also seems like a nice thing to do, your users will tire of it after a few times and will get down right annoyed if they use your app with any frequency. Best to tuck this stuff down as a sub-menu off the About menu. In short, “don’t put branding ahead of users.”
Sleight of Hand
Do not use the same area for different or conflicting functions. Think of muscle memory and make sure that the same gestures are related. Toby illustrated the problem with the iPhone’s slide to unlock and decline functions.
A quick and easy way to avoid this anti-pattern is to print out wireframes of your design and overlay each screen on top of each other over a lightbox and to be careful where your exit or quit button is going to be, assuming that your users may add an extra tap by mistake.
App as OS
When the app is running in a mobile environment, it tends to take over the screen giving the user the impression that the application is the OS. Rather than attempt to mediate the entire experience of the device through your app, defer to specialized apps which are designed to handle those functions. Use the YouTube player for videos, the browser for web pages.
Tone down any loud notifications. You can provide a setting to make them louder but remember, you’re embedded into a mobile device which is going to be carried everywhere. If possible, avoid pop-up error messages and embed your error message into the interface.
If your app requires a user account, make sure every screen that can be accessed without a login has a link to registration or sign-up. The last thing you want to do is have a potential registered user land on a login screen with no link to a page where they can register.
The High Bar
Allow for progressive degradation of your application. Remember, you’re app is operating in a mobile environment. Assume that connections will be flakey, the phone not running the latest OS. Remember the guy on the bus that’s just gone into a tunnel. What about the one-handed user on the subway? Can he they use your app effectively?
Make sure your application is able to persist state. There’s nothing worse than having to step back through to get back to where you were. The illusion of fast task-switching, pausing and unpausing, requires state persistence.
Take care not to take over and re-define a popular gesture. It’s a balance because you also don’t want to try and be too clever and introduce a new behavior that has too steep a learning curve.
Don’t rotate the screen for the heck of it. Fancy UI elements to be used in moderation.
Don’t hijack audio that is already playing. This is a common one. How many times have you been listening to music and then start playing a game that requires you jack the volume way up. When you quit out of the game, you blast your ears off as your music player comes back on.
It’s much better to blend the sounds so the user can take care to switch to the background app and shut it down or pause it.
Apple has done a lot of careful thinking about interface design on the iPhone expanding their work on the Human Interface Guidelines to the mobile environment. The iPhone HIG is a good resource for anyone designing for the mobile environment.
Hope these iPhone UX Anti-Patterns were useful. Can you think of any others?
For various reasons I was unable to attend the Open ID Design Summit. Thankfully, the talks were very well covered so it’s possible for anyone see what happened and the current state of discussions around what’s being called the “open stack”
Live-blogging the openid design summit – John McCrea from Plaxo did a great job of live-blogging the event. This is the best place to start because his post also embeds all the presentations. Thanks John!
Chris Messina just posted a bunch of video clips:
More below the fold: