Chararacteristics of WAP Applications
Device Dependency | Simplicity | Context of Use | Information Access
This page gives an introduction to WAP applications and lists their characteristics.
Device Dependency
Today all statements toward designing WAP applications are extremely device dependent, e.g. different display sizes and availability of softkeys.
Therefore a simple and well-structured design is the best strategy for minimizing the problem of supporting different browsers as well as phones and other WAP devices.
Simplicity
When it comes to designing any kind of electronic service, simplicity is the key to gaining acceptance and appreciation from the users.
Simplicity is especially important in the context of use in a mobile environment since the user often needs to concentrate on other things besides using the terminal. Two examples for this are:
- Fully mobile, such as walking through the streets
- Semi mobile, such as sitting in a train
Thus restrictions apply due to the factors device, application and context. Some implications of this are the following:
- It should be unnecessary to remember codes, numbers, or other information from one part of the application to another.
- In situations of choice the users should be asked to make simple decisions rather than complex ones. Divide the problem if possible.
- Good utilization of the extremely limited display space is important. Therefore avoid unnecessary blank space.
- The user interface should be as simple as possible, but not simpler. Unnecessary information and functionality should be removed. In conventional office applications one rule of thumb says that 20% of the functionality is used 80% of the time. To simplify, we could say that in mobile applications it is often advisable to cut out this 80% in order to reduce complexity and increase usability.
Context of Use
The situation or context of use is more demanding than under the usual circumstances when designing "stationary" software for office use. When using a mobile device, the users will probably experience a larger number of interfering factors, which will distract their attention.
- We recommend that user testing on all services are done in a live environment.
- To assure that the application is usable, the design
process should be user centered, rather than technology
driven. If you start to think about WAP applications
consider your:
- Primary user group
- Context of use
- Primary user tasks
Information Access
Motto: Keep the Focus on the Task and the most Relevant Information, Functions / Links, ...
The tasks conducted on a WAP terminal can be divided into two major task types:
- Information retrieval, e.g. getting the latest
news:
Usually the users will prefer to use a normal PC based Internet connection to browse for information. - Problem solving, e.g. getting information about and
book the next connection flight:
This makes it important to make sure that the users are able to work on their tasks by allowing quick access to brief information.
Focus on the most needed functions in relation to most important information regarding the focused task.
Keep an acceptable and understandable ratio between information value and interaction effort.
