Filter
Top Products
CHAPTER 3
Controls
Buttons 3-11
A button can disappear and reappear with no visual effect or with a subtle
visual effect such as zoom closed and zoom open. Generally, buttons should
not flash as they appear. Visual effects that attract the eye virtually compel
immediate action, as if they were shouting, “Tap me now!”
Button Placement 3
Text buttons and picture buttons are easiest to use at the bottom of the view
that contains them. In that position a user’s hand won’t cover the view while
tapping a button. Buttons that affect all items in a main view should go on a
status bar at the bottom of the main view (see “Primary Controls and Status
Bar” on page 2-11). The status bar is optional if the main view is small, like
the main views of the built-in Connection, Card, and Time Zones applications.
Buttons at the bottom of a slip or other auxiliary view are generally not on a
status bar.
In a view that displays multiple items, each item is headed by a separator bar
(see “Separator Bars” on page 2-11). Buttons that apply to only one item do
not go at the bottom of the view. Instead, the buttons are attached to each
item’s separator bar, and they scroll along with the item when a user scrolls
the view. For example, a Filing button and an Action button go at the right
end of each separator bar (see “Filing Button” on page 3-27 and “Action
Button” on page 3-28). Other buttons can go on a button bar that floats near
the end of an item. Figure 3-11 shows buttons on a separator bar, buttons on
a floating button bar, and buttons on a status bar.
It’s possible for your application to add buttons to another application’s
status bar. For example, your application could add a button to the backdrop
application’s status bar so users could bring your application to the front
without going through the Extras Drawer. This could be a boon or a nightmare
depending on how crowded the status bar is in the backdrop application. If
you want to add a button to another application, make sure users can disable
the feature.