Filter
Top Products
Navigation Guidelines
3
18 Genie Application Style Guide February 2001
Openwave Navigation Guidelines
■ Always define an action for <do type="accept">.
If no action is defined, a task of <do type="prev"> may be automatically bound to
the
<do type="accept"> key with the label OK or Back, which may not be what
the developer is intending. If Back is a more appropriate label than OK, use this:
Example 3-5
<do type="accept" label="Back">
<prev/>
</do>
■ Limit the length of labels.
Define <do> element, <option> element, and anchors labels using five characters or
fewer: the screen size on many phones is limited. Longer labels may be truncated and
lose meaning.
Example 3-6
<do type="accept" label="Find">
<go href="find.wml"/>
</do>
In Example 3-6, the label Find is under five characters.
■ Limit the number of softkey actions to two or fewer, when possible.
Since most phones do not have more than two softkeys, this limit allows the user to
view both softkeys. This simplifies tasks because the softkey labels are accessible
with one keypress. When more than two elements are defined, the first element is
bound to the primary softkey, and all other options and elements are accessible from
the secondary softkey.