Microsoft demoed Windows Live Messenger (WLM) beta on the show floor. (Snapshots coming soon.) Better looking than MSN Messenger 7.5 (lots of cutesy user interface removed, panes better organized) but it's a small point. One rep claimed the Messenger Beta is better than Skype because:

• audio quality ("we played with the codecs"),
  
• integration of identity and contacts across the Live family (hotmail/live mail),
  
• third party apps delivered through the system, and
  
• having more users (about 200 million) than anyone else.

How do you open up your software's user experience to outside parties?

It's distressing to hand your hard fought, crisply crafted, sophisticated design to imperfect strangers.

But you must.

It's key to learning new things. To multiplying the value you create by the curious, concerned, and committed. To meeting more customer needs. To lock-in.

So what's the best way to do it?

Prior art includes plug-in standards, high level human-computer interaction specifications and browser based methods.

With plug-ins, you parameterize everything within a few fixed guidelines. Think about Adobe Photoshop plug-ins, all looking more-or-less the same, but packaging different calculations in one consistent set of controls.

Sometimes a plug-in definition restricts too much. Kai's Power Tools went outside the Photoshop client to create user surfaces that better served user goals than anything possible within the plug-in UI spec.

"An interface is about hiding complexity from the user, It's about guiding a process, without cognitive understanding of what goes on beneath. Interface design is the art of enveloping the observer in an enticing, "try this" exploration with ever-new elements and designs as the tools to triumph in new territories." - Kai Krause

Ever wonder why it's easy to learn a new Macintosh program? Apple's famous UI specs for the early Macintosh OS guided the design of Mac apps.

Enter the AJAX era [wikipedia], a universe of loosely coupled, thoroughly decentralized, OS-independent applications. Where 14-year-olds can create toolbars for Firefox that produce new navigation of Flickr's photo site. Where users record and share Greasemonkey scripts that rewrite web pages so phone numbers become clickable SkypeOuts. Where Vonage users write and share desktop widgets to show Vonage status, minutes used, and performance. Where a weekend hack shows a Google map of a Craig's List of apartments renting near you.

Ten years' ago users were putting up words and pictures on the web.

Five years' ago users were storing them in databases.

Now we're creating applications, in a wave of design riding atop existing data, databases, and services.

The elements are straightforward, even if creating an effective platform remains an art.

So here's my first cut wishlist to open Skype's UI.

1. Open up your embedded browser to users
2. Let us open arbitrary web pages
3. Open up your tabbing and menuing navigation, subject to to
4. Expose its document model
5. Add JavaScript
6. Add Java
7. Support the web2.0 protocols: RSS, Atom, XML-RPC, SOAP, etc.
8. Support Flash
9. Open up the messaging/alerting system
10. Open up the help/documentation system
11. Build a toolbar system, so I can configure feature sets
12. Docking of external UI components/widgets with or within the main application
13. Skin the UI, so I can distribute my enterprise's branded skin or my Natasha Lyonne fan club skin.

Let

• engineers add functionality,
• designers adapt function to specific purposes,
• partners to channel their content, and
• users to make their copy of Skype their own.