W3C home > Mailing lists > Public > public-bpwg@w3.org > March 2009

ISSUE-291: widget best practices [Mobile Web Applications Best Practices]

From: Mobile Web Best Practices Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 19 Mar 2009 13:23:18 +0000 (GMT)
To: public-bpwg@w3.org
Message-Id: <20090319132318.2DAF9C6DB0@barney.w3.org>

ISSUE-291: widget best practices [Mobile Web Applications Best Practices]

http://www.w3.org/2005/MWI/BPWG/Group/track/issues/291

Raised by: Jonathan Jeon
On product: Mobile Web Applications Best Practices

A widget is an interactive single purpose application for displaying and/or updating local data or data on the Web, packaged in a way to allow a single download and installation on a user's machine or mobile device. 

Generally, widget is one of important application style in mobile. Many mobile web applications are very similar to widgets. So we need to consider the widget best practices as one of mobile web application.

In section 3 of MWABP, we propose to add the section 3.8 about Widget BP statements as follow.

----------------------------- start ------------------------
3.8 Widget

This section covers some specific Best Practices related to the use of Widget in mobile Web applications. Use these best practices as a guide to designing and developing your mobile widget so that you can deliver the most personal and targeted mobile Internet experiences to your customers.

3.8.1 Keep the widget simple. 

3.8.1.1 What it means

A widget’s purpose should be immediately apparent to the user. To achieve this, be sure you understand the user's mental model of the task your widget performs
Choose functionality and content that is useful for people on the go. Design it to perform one main function.

3.8.1.2 How to do it

3.8.2 Have a license agreement 

3.8.2.1 What it means

You should have a license agreement for any logos, trademarks, or branding that you use but do not own. And, you should have license agreements for all of the content (text, images, news feeds, and so on) your widget displays.

3.8.2.2 How to do it

3.8.3 Make globalizing and localizing

3.8.3.1 What it means

You need make a plan for globalizing or localizing the features, look and feel, and content your widget displays.

3.8.3.2 How to do it

3.8.4 Provide visual feedback 

3.8.4.1 What it means

You should provide visual feedback while the widget is connecting to the web or if it loses its connection.

3.8.4.2 How to do it

3.8.5 Use larger fonts, buttons, and controls

3.8.5.1 What it means

Using larger fonts, buttons, and controls are easier to see. 

3.8.5.2 How to do it

3.8.6 Keep interaction lightweight.

3.8.6.1 What it means

If you want to provide effective User experience, you should use selectable options and default values where possible. You must consider how to keep text input (or interaction) lightweight.

3.8.6.2 How to do it

3.8.7 Provide default settings and preferences

3.8.7.1 What it means

You need to allow the user to customize the widget with preferences. Consider providing default settings. 

3.8.7.2 How to do it

----------------------------- end ------------------------

** Reference

[1] Best Practices for Motorola Webui Widgets, http://developer.motorola.com/motodevchallenge/Widget_Best_Practices.pdf/ 

[2] Apple Human Interface Guidelines, http://developer.apple.com/DOCUMENTATION/UserExperience/Conceptual/AppleHIGuidelines/OSXHIGuidelines.pdf 
Received on Thursday, 19 March 2009 13:23:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:00 UTC