1 / 6

WAP Application Usability In GSM Markets October 2000

WAP Application Usability In GSM Markets October 2000. Title slide here. Paul Smethers Director of Usability Phone.com. Problem Statement. “Usability” defined as intuitive user interface for average consumers WAP doesn’t define interaction model

jluciano
Download Presentation

WAP Application Usability In GSM Markets October 2000

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WAP Application UsabilityIn GSM MarketsOctober 2000 Title slide here Paul Smethers Director of Usability 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

  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

  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

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

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

More Related