Bookshelf Home | Contents | Index | Search | PDF

Siebel ePharma Handheld Guide for Windows-Powered Devices > Application Development > Defining User Functionality >

Taking Advantage of the Handheld Device

---

Siebel Handheld Client users have different requirements from Siebel Web Client users. Typically, handheld devices have limited screen space and use different methods for entering data, such as smaller keyboards or a touch-sensitive screen. By keeping the Siebel Handheld Client user experience in mind, you will build applications that will allow your users to be more productive. Some guidelines for taking advantage of the handheld device are discussed in the following sections.

Identify User Activities

To conserve memory (and thereby improve performance) and ease navigation, identify business processes that are required by end users and develop applications that support these processes. If more than one type of user needs a Siebel Handheld Client application, it is preferable to divide the application into multiple responsibilities rather than give all possible users access to all available screens and views. Responsibilities are fully configurable by the application developer.

Support Stop-and-Go Workflow

Design Siebel Handheld Client applications to support a stop-and-go workflow. End users interact daily with the Siebel Handheld Client application, performing job-related tasks. These end users frequently start the Siebel Handheld Client application, navigate to data, read or enter data, and later return to the application to resume entering information. Frequently, an end user needs to navigate to another view to retrieve information while in the middle of a task. Design your applications so that end users perform a minimum number of taps to navigate to the desired information.

Design Applications That Require Minimal Navigation

Design applications that are as flat as possible. In a Web-based application, you may have views with many applets, and the user toggles between the applets. However, for handheld applications, create a larger number of views with fewer applets to allow users to quickly find information with a minimal amount of toggling.

Design for the Handheld Screen

Consider the type of handheld device that is being used and the way the screen is laid out. Consider the following questions when designing your applets:

Are the applets laid out side by side (on a HPC 2000 handheld device) or stacked one on top of another (on a Pocket PC handheld device)?
If you are using a list applet, how wide is that list applet going to be? Is it a full-screen list applet or a child list applet?
What are the most important fields and columns that a user needs to see at a glance before scrolling?
If you have a form applet that is a parent, for example, what fields do you really need in order to avoid scrolling?

Because there is less screen space on a handheld device than on a laptop or desktop, the most important data should be immediately visible.

Bookshelf Home | Contents | Index | Search | PDF