Yesterday Opera announced 100% compatibility with the Acid3 test on a private build. Followed suit by WebKit (you may call it Safari) that announced 100% compatibility available on nightly public builds. Rob Sayre from Mozilla calls Acid3 “basically worthless.” But regardless of who hit it first, or whether it is relevant, yesterday the race was clearly on.

We need these small bursts of innovation to keep moving browser technology forward. It is interesting to see how Opera maintains their status of trying to hit these milestones first, and how Safari is keeping up better than other browsers (like Firefox) do. It is important to mention that IE8 is supposed to come packing with standards support as well, as announced at MIX08 earlier this month. Exciting!

Mike calls it a massive win for the project and I agree - OpenID just scored bigtime when Yahoo! opened openid.yahoo.com this morning. If you don’t know what OpenID is, check the OpenID homepage at Openid.net, but for the non-technical people, Openid is a decentralized authentication system that allows you to share login credentials across multiple sites (in theory, this could be any website, in the future). Actually, Yahoo! has a great explanation:

Are you tired of creating a new account on every web site you use? Do you avoid new web sites because they come with yet another username and password? Do you paste stickies with password hints all over your computer monitor?

OpenID is an open technology standard that solves all of these problems. The OpenID technology will allow you to use your Yahoo! account to sign in to hundreds of web sites! And this list is growing every day…

So Yahoo! officially joins the ever-growing list of Openid providers - honestly, I can’t see how players like Google won’t follow this move as well. OpenID makes sense both from a user experience perspective (at least to keep users from having to remember login and password for their websites) as well as a portability and security perspective. Since you can effectively “carry” your personal identity between providers and transparently change providers if you think you can’t trust your current one, it puts control into the hands of the users - which is definitely something we need more of.

Evan Williams has a very good post on evaluating product ideas based on his previous experience (launching Blogger, Odeo - pretty much forgotten in that article - and Twitter). I’ve been thinking about a couple of products as well (have been for a while, actually), so the whole article sort of fell into place with my own criteria. Here are Ev’s:

• Tractability: How difficult will it be to launch a worthwhile version 1.0?
• Obviousness: Is it clear why people should use it?
• Deepness: How much value can you ultimately deliver?
• Wideness: How many people may ultimately use it?
• Discoverability: How will people learn about your product?
• Monetizability: How hard will it be to extract the money?
• Personally compelling: Do you really want it to exist in the world?

To these I would add two other characteristics that I believe have a great impact on a product’s success: cleverness and trustworthiness. You know when a product is clever because you get the feeling of empowerment and delight. And trustworthiness (although perhaps difficult to assess initially) defines how people look at your product or service - if users can trust it, it is more likely that they’ll become engaged and use it often. People are often skeptical about things that dip into their personal affairs (think Facebook’s Beacon and why it sucks), but will feel at ease to engage and discover new things about a product if they trust it.

Ultimately, it isn’t easy to determine the likeliness of a product being successful by putting it to the test against a series of attributes - but it may help. I’m still a big fan of entrepreneurs following their gut and seeing where it takes them, but depending on the person, that might not be a good plan to stick to.

I definitely recommend you give Ev’s article a read if you’re an entrepreneur - you’re still here so chances are you’ll be interested. Unfortunately Evan still doesn’t allow comments on his blog, because I would imagine the discussion on such an article would be interesting.

What a difference a small change makes. Gmail launched what has probably been my #1 wanted feature since I’ve started using it: colored labels. Labels were useful already if you wanted to archive content meaningfully, but without a visual cue their impact on the inbox wasn’t really significant.

Colored labels however, make a huge difference. If you’re smart about the way you use labels, you can create a system for your email to prioritize conversations, organize a task list, or go all out and build a proper GTD system out of it - all with the visual cues of colored labels, because they allow you to at a glance understand what email belongs where without reading the subject or even the label text.

What to take away from this

Minor differences like these visual cues are some of the things that define application experiences, and frequently (and unfortunately) are forgotten by developers and people building products. Products that are meant to help people manage assets in their daily life in particular deserve this special caring eye on them.

People building web applications need to ask themselves “How can I provide meaningful cues to help my users?”. These things (like the need for cues) are not found by chance - people do express the need for cues and helping paths all the time, we just need to care enough to listen and make changes.