Filter
Top Products
Navigation Guidelines
3
16 Genie Application Style Guide February 2001
■ Never define a prev as having no action.
Do not bind an action of type <noop/> to a task of <do type="prev">. This forces
the user to return to the home deck, which is not always intuitive and may make users
follow a long path to return to the application. Instead, bind the
prev task to an
intuitive place within the application, a starting point within the application or to the
home deck when that makes sense.
■ Provide a confirmation card (delete shield) to prevent data loss.
Do not allow users to back out of an application inadvertently when they have already
entered data in an entry query. Create a card asking users to confirm that they want to
quit. This spares users the tedious task of re-entering data.
Example 3-2
Openwave Browser
Nokia 7110 Browser
Mitsubishi Trium Browser
<onevent type="onenterbackward">
<go href="#confirm"> <!—- This goes to a card that asks users
if they are sure they want to delete all the data they've entered -->
</onevent>
In Example 3-2, the code should be placed on the card that spawns the data entry
form. If the user backs out after having entered the name, the confirmation card acts
as a delete shield.
Are you sure
you want to
cancel your
order?
Yes No
Name (first &
last):
John Doe
Alpha Next
User presses the
Back key
Delete shield
A
re you sure you
want to cancel
your order?
Options
Back
----Confirm order---- Options items:
No
Y
es
Name (first & last):
[John Doe]
Options Back
----------Order---------
Options items:
Edit
Next
Are you sure
you want to
cancel your
order?
[order
Andrew]
[City &
Yes No
Order
Name (first &
last):
John Doe
OK
User presses the
Back key
Delete shield