Both Google and Evernote offer an online tool for managing notes. This isn’t a review of each product’s capabilities, but an observation on their UIs. Evernote commits way too much real estate to administrative UI debris. I get a full 10.5 lines of writable space on a 800px high display. The rest is taken up by browser chrome and the note’s title, date, attributes, action bar, source, and terms of conditions.
Compare the following pictures showing the vertical space of each. In each, the usable real estate is highlighted. Both show the most fully maximized view that each offers.
Evernote:
Google notebook:
But that’s an unfair comparison you might say–the Google notebook is clearly taller.As I mentioned earlier, I was giving each the benefit of the doubt, showing the largest online view possible. Google offers a breakout version that strips off the unnecessary chrome and actions, leaving more space devoted to supporting the core function–taking notes.
On May 20, 2008, Todd posted this entry in User Experience, Information Architecture, Usability, Interaction, Interface.
I just came across this on www.dusteddesign.com. In their tag navigation, the length of the link tag is proportional to the number of articles it contains. I can’t say this works, or that I’d employ it, but it’s interesting and I applaud their thinking.
On March 9, 2008, Todd posted this entry in User Experience, Usability, Interaction.
When people asked me what a “user experience” designer was, I usually gave them the following answer: “I try to make software easier to use.” Simple and approachable, and without the arm-waving, chest-puffing that we UXDs use to justify what we do.
After reevaluating that canned response, I realize I was wrong.
As a UX designer, what I’m really after is trying to make software more pleasurable, which is not the same as easier. Pleasure is larger than that, and includes wonder, exploration and serendipity. Sometimes, easier isn’t always better.
Case in point, I like espresso. Scratch that–I have a real problem with it, in the way that addictions can creep into and start to change a person’s life. I’ve invested in $200+ coffee grinders. I go out of my way to buy beans in small batches from people who roast it that day. I adapt my grind for humidity and time my doppios to hit the 25-27 second mark. I’ve measured my tamp pressure to 30lbs using a bathroom scale. I’ll probably start roasting at home unless someone stops this sordid affair.
For god’s sake, I’ve watched YouTube videos showing shots pulled through naked, bottomless portafilters.
Making espresso is not for the impatient or half-assed. If you want to make it yourself, you’ve got to fully commit. No espresso-head, I argue, would consider pulling a good shot an easy task. All the elements have to be in place. Anything awry–old beans, bad water, weak tamping, too fine or too coarse grind–can lead to swill. I know because I’ve choked it down, and still do so frequently.
But I’m learning.
I love the process simply because it is not easy. Actually, it’s the opposite. It’s a wonderful challenge, with a delicious reward. The learning curve is part of the fun, in a way that mastery of an art should be. If easy was what I was after, I’d head down to the local indie coffeehouse and plunk down my 2 bucks.1 If I was conducting a usability test on the process, I’d have to conclude that it completely fails. But that disregards the other intangibles, such as the thrill of mastery.
So, to say that “user experience” is always about making things easier isn’t the whole story. User efficiency is definitely a factor, but not singularly so. Delight and engagement–often the byproducts of ease of use–are higher objectives to work toward. It all depends upon the context; ease of use is simply one factor to consider.
1 This is hypothetical. I haven’t found a place nearby that does a decent job of espresso. I won’t name names, but let’s just say that I’m underwhelmed with what I’ve received at the ITB Raleigh coffeehouses.
On March 7, 2008, Todd posted this entry in Design, User Experience, Usability, Interaction, Interface, Development, methods.
A few days ago, I wrote a post on the Capstrat blog about this idea I’ve been working out. It’s called Pidgin, which is a diagramming tool to accomplish two goals in tandem. One, Pidgin is aimed at providing definition to what a UI needs to encompass. Second–but in unison–it needs to be less prescriptive of the visual design. So basically, it’s trying to situate itself in the pre-design phase, when requirements are solid but the design is still fluffy and unbounded. Check it out here. Manners dictate that I don’t cross post.
On September 7, 2007, Todd posted this entry in User Experience, Information Architecture, Usability, Interaction, Interface.
Just wanted to post an update on some of the recent events that have occurred in the Phoenix usability community.
Christopher Brya has been hard at work assembling interested members and putting together the paperwork to create a UPA chapter in Arizona. In case you’re not aware, UPA
…supports usability specialists, people from all aspects of human-centered design, and the broad family of disciplines that create the user experience in promoting the design and development of usable products.
He’s even started a blog at arizonaupa.blogspot.com. Head over there and sign up for the mailing list. If you’re interested, leave a comment on the blog about what you’d like to see the group tackle.
Theo Mandel has started putting together the framework for our local World Usability Day Event. In his words,
I would like to announce the Phoenix event for World Usability Day 2007 on November 8, 2007. The Applied Psychology Program and Cognitive Engineering Research Institute at ASU’s Polytechnic Campus have graciously agreed to host the event on their campus in Mesa. The event will take place from 6-9 p.m. on the evening of Thursday, November 8, 2007. There will be no cost to participants to attend the event.
For more information, check out the full message at the PHX UEX Google group. If you’re interested in presenting (or sponsoring of course!) definitely throw your hat into the ring.
On April 5, 2007, Todd posted this entry in Design, Information Architecture, Usability, Development.
Today, April 5th is CSS Naked Day. That means that the site you’re seeing today has been stripped of all css, rendering the site in all its non-styled glory. Why do this?
The main reason is to draw attention to the the underlying markup of a page, and to demonstrate how people with screenreaders might be seeing the site. In particular, it calls to attention the structure of the xhtml and the benefits of using semantic markup.
What’s Wrong
It’s been since dev that I have really looked at my site unstyled. I’m fairly pleased with how it renders but I’ve noticed a few problems that I want to mention.
What’s Right
Overall, I think the presentation degrades decently. I don’t have any problem reading or navigating the site. But I’d really like to hear your opinions. So far, the good points that I see are:
There are probably a number of other things that are positive and negative about my design. Please voice your opinions because, well, my time is up and I have to go to work.
At work, I’m tied to Lotus Notes–that plucky little groupware client that refuses to die. I dare say that a single day passes where I’m not surprised by its brusque nature, awkwardness, and overall “unapproachability.” Today, I share with you the following dialog box that I received while trying to comment on a meeting request.
About two words into my comment, I decided that I really didn’t have anything useful to say. So, I tried to cancel out. If you look at that dialog, you’ll realize that Lotus has committed me to sending a message whether I like it or not.
On February 4, 2007, Todd posted this entry in User Experience, Information Architecture, Usability, Interaction.
I’ve just started a Meetup for people interested in user experience design in Phoenix. Having just arrived here a little over 3 weeks ago, I’m surprised that there wasn’t a community for local Phoenicians to get together and discuss this discipline. That said, a bit of trolling of LinkedIn, Meetup, IxDA, and Google revealed that there is a nascent group of like-minded individuals.
So, this is a call to arms. If you’re interested in things like:
…then I entreat you to check out the group. In the future, I’d like to bring this group toward a full chapter status of the Usability Professionals Association. That’s still a ways down the road, I suspect. For now, I’m super excited about drawing together people from around the valley to discuss everything from “rules and tools” to war stories. Bring it!
Oomblog is a stream of thoughts, ostensibly focused on user experience.
