This is iPhone application related.
Application UI is already done for S60 phones but we are developing
new version for iPhone as well.
There is a screen that displays a list of devices. For every device
in the list the user can perform one of the following
1. browse into the directory of the device
2. see device properties
3. see home page of the device
4. see settings for that device
Of the above, the most commonly used action (say default) is the
first one, which is 'browse directory'.
Using the S60 type regular phones, users use the five-way main
navigation button to first highlight the device they want to act on
and then select options menu that shows the above four actions.
In case of iPhone, as we know everything is single tap/touch we want
the user to see the 'browse into directory' on the tap of a device
in the list. This is because it being the most common action
performed. We do not want to include an additional step every time
for choosing from a modal box or a new screen containing the four
options. It is because we want to minimize the taps to be done by the
Now the user has tapped on the device and views the file directory as
the second screen.
My question: Is it a good idea to have the four options display on
this second screen showing the directory of deivce? The four options
has got to act on the device and not on the directory itself. If user
goes browsing deeper into the directory, the options change and
actions have to act on the files within the directory and not on the
>From your experience in designing interactions for iPhone applications, have you come across such a problem? How should it be
handled? Is there a convention sort of flow followed for iPhone app
dealing with such type of interaction?