Genie 7110 manual Navigation Guidelines, Never define a prev as having no action

3 Navigation Guidelines

■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

Name (first & last):

John Doe

Alpha Next

User presses the

Back key

Are you sure

you want to

cancel your

order?

Yes No

Delete shield

Nokia 7110 Browser

----------Order	---------	Options items:
Name (first & last):		Edit
[John Doe]		Next
Options	Back

Mitsubishi Trium Browser

----Confirm order----		Options items:
Are you sure you		No
want to cancel		Yes
your order?
Options	Back

Order	Are you sure
Name (first &	you want to
last):	cancel your
John Doe	order?
OK	Yes	No
User presses the	Delete shield
Back key	[City &

<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.

16 Genie Application Style Guide February 2001