How it Works
Nokia
Loading...
TS342
User Manual
33 pgs605.22 Kb0
Table of contents
Loading...

Nokia TS342 User Manual

FORUM NOKIA
WAP Service Developer's Guide for
Nokia Series 30 Phones with WML Browser
Browsing
Version 1.1; June 09, 2003
Contents
1 Introduction................................................................................................................................................ 7
1.1 Chapter Topics...........................................................................................................................................7
2 Guidelines for Design................................................................................................................................ 8
2.1 Applications for Mobile Use...................................................................................................................8
2.2 Validating WML .........................................................................................................................................8
2.3 GPRS Usability............................................................................................................................................8
2.3.1 No changes required by developers ...................................................................................8
2.3.2 Cache utilization........................................................................................................................8
2.3.3 Usability tips ...............................................................................................................................8
2.3.4 Infrastructure optimization...................................................................................................9
2.4 Site Organization......................................................................................................................................9
2.4.1 Doormat pages...........................................................................................................................9
2.4.2 Login..............................................................................................................................................9
2.4.3 Detecting the browser.............................................................................................................9
2.4.4 Optimizing for size....................................................................................................................9
2.4.5 The first screen........................................................................................................................10
2.5 Pictures and Tables............................................................................................................................... 10
2.6 Efficient Navigation ..............................................................................................................................10
2.7 Search........................................................................................................................................................ 10
2.8 Titles and Element Labels...................................................................................................................10
2.9 Error Messages and Confirmations..................................................................................................11
2.10 A Usability Test.......................................................................................................................................11
3 Introduction to the User Interface......................................................................................................12
3.1 Nokia Phones with 96 x 65 Pixel Screen Resolution.................................................................. 12
3.2 User Interface Hardware – Keys and Display................................................................................ 12
3.2.1 Two Soft Key Display.............................................................................................................12
3.2.2 Keys in Two Soft Key User Interface................................................................................. 13
3.3 Display Fonts...........................................................................................................................................13
3.4 Accessing the WAP Browser...............................................................................................................13
3.5 Navigation, Labels, and Titles ...........................................................................................................13
3.6 Scrolling....................................................................................................................................................14
3.7 Picture Viewer ........................................................................................................................................14
3.8 Cache .........................................................................................................................................................14
4 WML Elements for the Nokia User Interface .....................................................................................15
4.1 Text Formatting .....................................................................................................................................15
4.1.1 Paragraph and content alignment................................................................................... 15
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser
2
4.1.2 Line break................................................................................................................................. 15
4.1.3 Fieldset element.....................................................................................................................16
4.1.4 Pre element..............................................................................................................................16
4.2 Table ..........................................................................................................................................................16
4.3 Images ......................................................................................................................................................17
4.3.1 Animated GIF ........................................................................................................................... 18
4.4 Links........................................................................................................................................................... 18
4.5 Do Element ..............................................................................................................................................18
4.5.1 Prev task.................................................................................................................................... 19
4.5.2 Cardwide and deckwide scope.......................................................................................... 19
4.6 WML Input Processing .........................................................................................................................20
4.6.1 Input elements........................................................................................................................20
4.6.2 Direct input access.................................................................................................................21
4.6.3 Select element.........................................................................................................................21
5 Additional WAP 1.2.1 features .............................................................................................................23
5.1 Push ...........................................................................................................................................................23
5.1.1 Service inbox............................................................................................................................23
5.1.2 Service Indication...................................................................................................................23
5.2 Wireless Telephony Applications Interface (WTAI) Public Library ........................................ 24
5.2.1 Making a phone call...............................................................................................................24
5.2.2 Incoming call while browsing............................................................................................24
5.2.3 Sending DTMF tone................................................................................................................24
5.2.4 Adding a phone book entry................................................................................................25
5.3 Cookies......................................................................................................................................................25
5.4 Accesskey .................................................................................................................................................25
5.5 Content Download over WAP ............................................................................................................ 25
5.6 Segmentation and Reassembly (SAR)............................................................................................. 26
6 Terms and Abbreviations ......................................................................................................................27
7 References .................................................................................................................................................29
Appendix A. Wireless Application Protocol (WAP)..................................................................................30
Introduction...........................................................................................................................................................30
WAP Architecture.................................................................................................................................................. 30
WAP and Internet architecture.........................................................................................................30
Wireless Application Environment (WAE)...................................................................................... 31
Wireless Session Protocol (WSP) ...................................................................................................... 31
Wireless Transport Protocol (WTP)..................................................................................................31
Wireless Transport Layer Security (WTLS).....................................................................................31
Developing Applications for Mobile Browsing............................................................................................31
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser
3
Additional Information ......................................................................................................................................32
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser
4
Change History
04 Nov 2002 V1.0 Initial document release.
09 June 2003 V1.1 Template changed, Nokia 3510i and Nokia 8910i information removed.
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser
5
Disclaimer
The information in this document is provided ”as is,” with no warranties whatsoever, including any warranty of merchantability, fitness for any particular purpose, or any warranty otherwise arising out of any proposal, specification, or sample. Furthermore, information provided in this document is preliminary, and may be changed substantially prior to final release. This document is provided for informational purposes only.
Nokia Corporation disclaims all liability, including liability for infringement of any proprietary rights, relating to implementation of information presented in this document. Nokia Corporation does not warrant or represent that such use will not infringe such rights.
Nokia Corporation retains the right to make changes to this specification at any time, without notice.
The phone UI images shown in this document are for illustrative purposes and do not represent any real device.
Copyright © 2003 Nokia Corporation.
Nokia and Nokia Connecting People are registered trademarks of Nokia Corporation.
Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc.
Other product and company names mentioned herein may be trademarks or trade names of their respective owners.
License
A license is hereby granted to download and print a copy of this specification for personal use only. No other license to any other intellectual property rights is granted herein.
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser
6
WAP Service Developer's Guide for Nokia Series 30
Phones with WML Browser
Version 1.1; June 09, 2003
1 Introduction
The following document provides information and practical examples for developers who want to optimize their WAP services for Nokia Series 30 devices with a WML browser. It is written for service developers as well as anyone involved in creating the wireless information society who needs to know more about service creation on mobile terminals. This guide is not intended to describe WAP in detail, nor is it meant to replace any WAP specification.
1.1 Chapter Topics
Chapter 2 of this document describes several general usability issues concerning WAP service development. Chapter 3 introduces the browser's user interface elements, keys, display, and browsing conventions. Chapter 4 outlines some general WML elements that are mandatory features for WAP
1.2.1, according to the WAP Forum specifications. Chapter 5 introduces additional WAP 1.2.1 features that are supported in Nokia Series 30 phones.
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser
7
2 Guidelines for Design
The Nokia Series 30 UI is designed to be easy to use and intuitive. The following section offers general guidelines to help developers create browsing applications that will be perceived as usable and easy to understand.

2.1 Applications for Mobile Use

When deciding what information to include in various applications on a mobile terminal, developers should consider the types of situations where the mobile phone will be used. The content of the service should fulfill the needs of the target user group and be optimized for the most common tasks. Because of the mobility of the small display, the user might primarily use the mobile phone when there is no PC access to the Internet, and for quick information. Examples might include speedy access to flight schedules, short news flashes, and access to weather information or checking the temperature at a traveler’s destination. It is less likely that users will use their mobile phones to surf.
2.2 Validating WML
There are several XML validators available that validate documents against WML Document Type Definition. It is recommended that authors validate their WAP pages, because invalid WML is always treated as an error and discarded (that is, it is not shown to the user).
Several XML validators can be found at http://www.wapdevelopers.org/.
2.3 GPRS Usability
GPRS enables efficient use of resources, instant access, fast delivery of information, and innovative charging models.

2.3.1 No changes required by developers

Since the WAP standard was designed to allow content to be delivered over any bearer service, it is not necessary for developers to make changes to their WAP services or applications. This is true even when delivery of the services is enabled over GPRS, 3G, or any other networks.
2.3.2 Cache utilization
Developers should use HTTP proxy to cache WML content whenever the content is accessed through the Internet. The proxy should be placed close to the WAP gateway to minimize the distance for data transfer between the two components. The home page (first page) can alternatively be kept on a local server, close to the WAP gateway.
Most clients have a cache; using it is a good way to improve the user's experience. Cache headers should be sent with documents to ensure that pages are cached on the client if possible. Content developers should not assume that pages are cached by default.
2.3.3 Usability tips
Round trips in the network add a minimum two-second delay to the response time. Therefore the number of round trips should be minimized. The response time of a first page has a strong impact on the user experience, so it is worth optimizing.
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser
8
2.3.4 Infrastructure optimization
The latency between the WAP gateway and content server should be minimized. Each query traverses this link twice, once as a request and once as a response.
The WAP gateway should be placed close to the GPRS gateway. (The GPRS gateway is technically called a “Gateway GPRS Support Node,” or GGSN.) “Close” in this instance refers to both latency and the probability of packet loss. Lost messages cause additional delays due to HTTP retransmission.
2.4 Site Organization
2.4.1 Doormat pages
It is not recommended to start the site using a doormat page, which serves no other purpose than to perhaps greet the visitor and display a logo. It is better if the user can go to the service directly.
2.4.2 Login
Entering login information can be time consuming with a mobile phone. Login information should be requested only once during the session, not each time after starting navigation from the main page. Case-sensitive checking of user names and passwords should be avoided.
2.4.3 Detecting the browser
When using a modern Web site hosting environment, it is possible to detect the browser as well as the language mode and supply the correct content transparently, without user interaction.
The Nokia Series 30 mobile browser sends a user agent field in the WSP header to the WAP gateway when the content is fetched from the origin server. This user agent field can be used to define the type of browser and then build a logic on the origin server to serve suitable content. From the WAP gateway, it is then delivered inside the HTTP header.

2.4.4 Optimizing for size

Interactive pages should be short; informative pages, long. Having pages that are too short and require many downloads is worse than having close-knit information on one longer page. In particular, interactive pages with forms should not be too long, as users start to lose their feeling of control if the form is more than two screenfuls. Empty rows can be misleading, as users may think there is no more content below.
If, for example, a page contains a story or instructions, the entire content should be on one page. Subtitles that take the user to points within a page help when browsing long, informative pages.
It is difficult to give hard and fast guidelines about how many links should be provided on one link list page. If the links clearly belong together and are easy to browse (one line per link, in alphabetical or other logical order), it is better to provide 30 links on one page than 5 links on six pages.
As for the total downloading time, some studies place an upper limit for acceptable delay on a PC­based browser at 10 to 15 seconds, including all images. It is highly recommended to have a response time (excluding connection time) of less than 10 seconds in a mobile environment.
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser
9

2.4.5 The first screen

The first (topmost) screenful of any page is the most important. All often-used navigational links, search fields, login screens, and the bulk of the information should reside there. The user can then navigate forward before the rest of the page has been loaded, and will not have to scroll the page.
Wasting the top of the page on banner advertisements or non-informative graphics should be avoided. It is better to place advertisements at the left or right edge.

2.5 Pictures and Tables

Downloading images takes time, and many users may opt to switch off the loading of images for more speed. Authors should try to optimize image size. If there are large pictures on the site, authors should consider using thumbnails for the image index. Color images should be tested for visibility on a monochrome display. Usually, the same image cannot be used for color and monochrome displays.
An alternative text (using the alt attribute of the <img> element) should be provided for images that convey information. A null alternative text (alt=””) should be used for images that do not convey information, or that are used for page layout or decorative purposes only.
The table width or height should not exceed the screen size, since scrolling will make the table less readable (e.g., column titles are not visible after scrolling down).
2.6 Efficient Navigation
The service provider must be responsible for navigation as a whole. A consistent navigation method should be provided within the service. Each page should contain links to the main page of the site and to the possible subsection main pages.
The back function can also be provided as a link on the page, but should not be used, for example, on pages that will return the user to a purchasing or confirmation page.
If access keys are used, their definitions should be consistent for the main page links, e.g., “1” always takes the user to the main page of the service.
2.7 Search
A piece of information in the service can be found by moving ahead in a tree hierarchy or by conducting a search. Ideally, both methods should be provided. The tree hierarchy helps the first-time user clarify the service structure, but it may be too slow for an experienced user.
Search results should be optimized to include only a few items; if more are found, the user should have the opportunity to narrow the search criteria.

2.8 Titles and Element Labels

The title describes the contents of the display. Use of titles is recommended in WML. Titles help the user navigate in the application because they remind the user where s/he is within the application. It may be a good idea to start the title with the service’s name and keep the total length of the title short. The item previously selected by the user should determine the header text. For instance, the title “Bookmarks” tells the user that the display contains a list of bookmarks in the application and that the options item previously selected was Bookmarks.
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser
10
Loading...
+ 23 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use