User Guide

CHAPTER 1
Newton and Its Users
Design for the Newton System 1-11
Keep Applications Simple 1
Newton isn’t designed for complex tasks or applications that require viewing
a large area or multiple windows of data at a time. Applications that require
the user to keep track of several pieces of information at once probably won’t
work well because the user must either move around a lot within the
application, or deal with many simultaneous or layered views. Studies show
that users become confused in those situations.
Remember that people will use Newton while on the move, in places where
there’s no place to sit or to set it down. In such settings, it’s easiest to use
applications with simple, straightforward screens and an obvious path
through the information. Make sure that your application’s controls are
clearly identified, that there aren’t too many “places” for the user to navigate
through, that you don’t display too many container views at once, and that
the user can easily see what to do. Minimize writing; tapping to pick from a
list of alternatives is easier.
Use Screen Space Wisely 1
Because the user’s hand is usually held close to a Newton device, it’s best to
keep tappable controls at the bottom of the screen, have the user enter data
in the middle of the screen, and display titles and other descriptors at the top
of the screen. This way, the most important information (the user’s informa-
tion) isn’t obscured each time he or she taps a button. If you need to display
controls on the side, make sure your application allows users to move the
controls to either side of the screen, according to whether they are right- or
left-handed.
Check the Screen Size 1
A Newton application’s main view—the visual object that serves as the
application’s base of user operations—can be any size. If your application’s
main view does not fill the entire screen, keep in mind that whatever is
visible behind your application will be operable. In this situation, users can