1 / 9

Design of Palm Pilot

Design of Palm Pilot. Rob Haitani Presented by: Pankaj Thakkar. Overview of Palm Pilot. PIM Functionality Not a PC replacement Single button Hot Sync capability Touch sensitive screen with handwriting recognition Less is More. Dimensions: 4.7” x 3.1” x 0.6” Weight: 5.7 ounces

shamus
Télécharger la présentation

Design of Palm Pilot

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. Design of Palm Pilot Rob Haitani Presented by: Pankaj Thakkar

  2. Overview of Palm Pilot • PIM Functionality • Not a PC replacement • Single button Hot Sync capability • Touch sensitive screen with handwriting recognition • Less is More • Dimensions: 4.7” x 3.1” x 0.6” • Weight: 5.7 ounces • Power Source: 2 AAA batteries • Screen: 160x160 pixels; black & white; touch sensitive • Processor: Motorola 68238 • Operating System: PalmOS

  3. Design Goals • Build a better device than existing handhelds like Zoomer and Newton • Support a limited functionality efficiently • Quick and instant access to information (frequently) • Target audience: PC users • Not a replacement for PCs. Provide Hot-Sync capability to synchronize information with PCs. • Do the right thing

  4. Non PC Design • Don’t emulate the PC design blindly • Mechanical buttons as well as software buttons • No “Save” buttons/functions • No application switching • Predictability more important than consistency • Software Miniaturization

  5. Implementation Notes • Every pixel counts. No fancy features • Make frequent tasks/functions easily accessible (e.g. by reducing the number of taps) • If in doubt, do a user-test to evaluate • Minimize clutter. Assess user requirements.

  6. Steps to Success • Wireless two way email through handheld • Context sensitive buttons (appearing/disappearing) • No menu support ? (As of now Palm does support pull down menus)

  7. Usability Analysis • Research about user preferences and requirements • Do user testing from the beginning of the project • Phone Test: If the other person can tell if you are using a Palm for accessing information (like schedule, phone numbers)

  8. Palm v/s Windows CE • CE design close to PC (windows) design • CE uses menu, Palm does not • According to Palm people, CE has extra bells and whistles, the sluggish performance will be annoying • Palm design is kept simple and it is made to do specific functions only

  9. Conclusions • Users want an efficient appliance (designed to do specific tasks) not a small PC • The interface needs to be simple and predictable • Many of the design principles which hold in PC world are not applicable in handhelds • Have many special purpose information appliances than a big bulky all rounder

More Related