Windows Live Gadget SDK - Gadget Design Guide

These high-level guidelines concern Windows Live gadgets and should be used in conjunction with the Live.com gadgets SDK. Once you learn the basics of assembling your gadget you can start thinking about the higher level design of your gadget. You should consider how the user will interact with the gadget.

Gadgets are compact, mini applications that surface focused single-task services and information to users in a simple, concise interface.

A Gadget:

Focuses on a single task or user goal
Is compact, simple and purposefully limited in its functionality
Surfaces essential information and features
Presents information that users can easily understand
Fits well into its surroundings yet unique in its look, feel and behavior
Creates a cohesive experience for the user
Does not replace an application

A gadget is not a container for multiple, diverse functions. If you've used instructional text to explain your gadget then you've probably made it complex.

Example:

Clean UI
Intuitive
Compact
Focused on a single task or goal

Follow these guidelines as you design your Gadget:

The design of your gadget should revolve around its primary purpose.
A user should be able to easily use the gadget with minimal explanation or configuration.
The gadget should make effective use of its space. A gadget should take <= 200 pixels (height) in its default state with the option of growing no more than 400 pixels in height.
The gadget is focused on a single task. A gadget does not replace an application. It should in fact complement an existing app or feature. Gadgets give you the chance to get your product/service or feature in front of users on their homepage.
Be responsive and display information immediately. A user should not be waiting for content to appear. In the event that the user must wait for content, the gadget should provide the appropriate feedback to the user.

Launch

This mode shows the gadget icon & name. This will be displayed in "my stuff" and "my stuff". Be as descriptive as possible since this is one entry point into how the user will discover your gadget.

Launch Mode

Collapse

This mode consists of the name of the gadget and an icon; optionally it can also convey some information such as the weather gadget seen below.

Collapsed Mode

Expanded

This is the standard, most common view of a gadget. The gadget should take <= 200 pixels (height) in this state.

Expanded Mode

Using the Title of the Gadget

An URL can be set in the title of the gadget. Clicking on this URL will open a new browser window and follow the link.

Using Tile of the Gadget

Most gadgets are mash-ups and take advantage of existing data feeds. Some things to keep in mind when accessing external data:

Ensure information accuracy.
Take necessary steps to contact the data provider so they are aware of how their data is being used.
Use the attribution section of the gadget to credit your data providers.
Your gadget should respond accordingly if a data feed suddenly changes/becomes unavailable/etc..
You should have permission to use the content from the data provider.

If a gadget requires authentication beyond what is provided by the following guidelines are suggested:

Keep your user informed. If you need to ping another server to authenticate provide feedback to the user indicating progress, status, etc.. The gadget should never look like it's hung and unresponsive.
Require authentication when absolutely necessary. Don't make a user jump through the authentication hoop if the resulting information does not provide valuable user-specific information.

Some gadgets have a limited lifespan. For example, a team produces a Super Bowl Gadget and a few weeks after the game it no longer works. The gadget should not just stop working or have stale content. In these cases the gadget should include some form of RSS to message the user to remove the gadget.