Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.

(Difference between revisions)

Mobile Web Design : Completeness Meter

From Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Tidy wiki text)
hamishwillee (Talk | contribs)
m (Text replace - "Category:Mobile Design" to "")
Line 1: Line 1:
[[Category:Mobile Web]][[Category:Mobile Design]][[Category:Mobile Web Design]]
[[Category:Mobile Web]][[Category:Mobile Web Design]]
{{ArticleMetaData <!-- v1.2 -->
{{ArticleMetaData <!-- v1.2 -->
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example]] -->
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example]] -->

Latest revision as of 03:29, 9 May 2012

Article Metadata
Created: mayankkedia (30 Jun 2009)
Last edited: hamishwillee (09 May 2012)

This design pattern is part of the Mobile Web Design series.


[edit] Introduction

There are some use cases which require an overall measurement, some sort of a quantitative analysis to understand how much/what percentage of an activity has been completed. The approach used to indicate this to the user of the website is known as completeness meter.

[edit] What is completeness meter

Completeness meter is an indicator/a barometer if you please to denote the overall completeness of a task, an activity etc. It is used to let the user know how much of the work vis a vis the given task they need to complete to get up to a certain level, the level could be measured in percentage terms, numerically, expressed in tags etc.

Completeness meter example

[edit] When to use

The completeness meter should be used in one of the following use case scenarios:-

  • The intention is to indicate to the user the overall status they are on vis-à-vis the activity for which the meter has been shown.
Completeness meter in software installation
Completeness meter with time remaining information
  • You want to fuel the user’s interest by giving them some sort of a measurement figure, something they might have been loathe to complete without that extra bit of incentive.
Quantitative figures for completeness
  • When the overall capabilities of the user can vary depending upon the completeness of their activity for instance credit points/trainings conducted etc.
Capabilities depend on the completeness figures
  • When the website recognizes/rewards user based on their completeness, it could be a combination of both qualitative and quantitative inputs for instance.

[edit] Advantages

Some of the key advantages of using the meter are:-

  • It helps the user in ascertaining their overall progress towards their desired goals/task completion status.
  • Helps the site to garner more information about the user, thereby tailoring the content more in sync with that data, for instance the user’s hobbies/favorites etc.

[edit] Usability guidelines

Some usability guidelines to follow while using the meter are:-

  • Provide the user with help/information on how to improve their completeness ratings.
Meter with edit option on linkedin
Helpful information to boost completeness
  • Always have a textual/figurative implementation of the meter so that the user knows their standings; don’t use them internally without letting the user know.
  • It might be a good idea to give the user a complete breakup of how the meter readings were arrived at.
Breakdown of completeness
  • If the use case of the website allows to, think about ways to reward the user with higher completeness ratings, this would motivate the others to get there as well.

--- Added by Mayank on 30/06/2009 ---

This page was last modified on 9 May 2012, at 03:29.
91 page views in the last 30 days.