Title slide here WAP Application Usability In GSM Markets October 2000 Paul Smethers Director of Usability Phone.com

Phone.com 2 Problem Statement “Usability” defined as intuitive user interface for average consumers WAP doesn’t define interaction model European WAP developers mostly use Nokia’s SDK and interaction model All WAP browsers have different interaction models Wireless interaction models are different from PC interaction models

Phone.com 3 Solution Constraints The issue is “Interaction” not “Presentation” Solution must allow for a standard to develop a single application for all wireless devices Most wireless devices cannot be upgraded by consumers Consumers will buy whatever device is popular Consumers will reject wireless Internet if it is not easy to use on their device It will take 1 year before a new standard can be deployed

Phone.com 4 Candidate Solutions Developers build multiple applications  Only solution that works today Semantically enriched markup language  New tags to allow developers to specify interaction desired Allow developers to explicitly define interaction model

Phone.com 5 Browser Differences Example Phone.com style “ ” WML Element Nokia style “ ” WML Element

Phone.com 6 Another Example Phone.com style “ ” WML Elements Nokia style “ ” WML Element Yes No