F O R U M N O K I A WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser Version 1.
Forum.Nokia.com Contents 1 Introduction................................................................................................................................................ 7 1.1 2 Guidelines for Design................................................................................................................................ 8 2.1 Applications for Mobile Use...................................................................................................................8 2.
Forum.Nokia.com 4.1.2 Line break ................................................................................................................................. 15 4.1.3 Fieldset element ..................................................................................................................... 16 4.1.4 Pre element.............................................................................................................................. 16 4.2 Table .....................................
Forum.Nokia.com Additional Information ......................................................................................................................................
Forum.Nokia.com Change History 04 Nov 2002 V1.0 Initial document release. 09 June 2003 V1.1 Template changed, Nokia 3510i and Nokia 8910i information removed.
Forum.Nokia.com 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.
Forum.Nokia.com 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.
Forum.Nokia.com 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.
Forum.Nokia.com 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.
Forum.Nokia.com 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.
Forum.Nokia.com Proportional fonts are used in header text, and if the header text is too long, it is cut automatically. Cut titles are usually better than abbreviations, because the user may be confused by unfamiliar abbreviations. Although short words are recommended for element labels, acronyms that are not well known by the target user group should be avoided. The same label should always be used for the same thing, especially with function labels such as Delete, Remove, Erase, Clear, and Destroy. 2.
Forum.Nokia.com 3 Introduction to the User Interface The following chapter offers a brief overview of the user interface style in 96 x 65 pixel screen resolution phones. The main focus is on the WAP services element (WAP browser) of the phone. The WAP browser user interface is designed to comply with the user interaction handling known from other applications in the phone.
Forum.Nokia.com Figure 1: Structure of the browser screen The application area is 96 pixels (horizontal) by 45 pixels (vertical). It includes four lines of main text and can also be used for displaying graphics, which can be scrolled four ways (picture viewer) until the maximum deck size. 3.2.2 Keys in Two Soft Key User Interface The Send/Talk key works as a selection key. The End key exits a data call/GRPS connection and goes into idle state when pressed twice.
Forum.Nokia.com an input element is used in the editor title. The label of a do element is used in the Service options behind the Options soft key. 3.6 Scrolling The user can move up and down in a card view when it contains elements (hotlinks, input elements, and selection list items) and static text areas between them. This is done by ”jumping” from element to element. Scrolling through long static sections (that is, text lines) is done line by line.
Forum.Nokia.com 4 WML Elements for the Nokia User Interface This chapter serves as a guide for using WML in designing services. It provides an overview of graphical user interface elements, that is, the WML elements that are critical from the rendering point of view and their WML capabilities supported by the browser. The document does not include all possible WML elements and attributes. WAP service developers should pay special attention to Sections 4.2: Table and 4.3: Images.
Forum.Nokia.com 4.1.3 Fieldset element The fieldset element allows the grouping of related fields and text. The basic idea of grouping is to show the grouped items on the same display if possible. If the items cannot be displayed on the same display, the user is not given any notification. Fieldset always starts a new line and ends with a line break. 4.1.4 Pre element The pre element is supported. When the pre element is used, the content shown is rendered as “preformatted” to the extent possible.
Forum.Nokia.com
 | 27°C | | W 6/9 |  | 24°C |
| T 6/10 |  | 28°C |
| F 6/11 |  | 29°C |
Example 2: Table element 4.Forum.Nokia.com 4.3.1 Animated GIF Most recent Nokia browsers1 support image format animated gif (.gif 89a). The maximum number of frames allowed is 13 (note, maximum file size is 2.4 kb). The animation can be viewed in the browser view. After running the animation in looping mode for 50 loops the animation will stop. The last frame of the animation will be shown as a static gif. 4.4 Links The anchored link element specifies a hotlink.
Forum.Nokia.com Type Accept Prev Help Reset Options Delete Unknown Static text OK Back Help Reset Options Erase Unknown Table 1: do elements label default text 4.5.1 Prev task The author of the WAP service is always responsible for the working navigation model inside its own service. If there is a need for back functionality, it should be explicitly defined with the prev type do element. The WAP browser does not have any implicit back functionality. 4.5.
Forum.Nokia.com PAGE 21Forum.Nokia.com 4.6.2 Direct input access The user can also select the input element by pressing any numeric key when the edit box appears and the pressed key is already placed in the edit box, i.e., the user can just start inputting characters and the edit box appears automatically. When T9 (predictive text input) is activated, the soft keys are "Options" and "Back" when the editor is empty. Otherwise the soft keys are "Options" and "Clear." This also applies if T9 is deactivated.
Forum.Nokia.com user can view the value between brackets in full by pressing the # key. Until the # key is released, the content that can fit on the screen is viewed. The soft keys are hidden while the content is viewed in full. The layout in full view is the same as the one selected by the user for browsing. The option element specifies a single choice option in a select element. Options can be grouped with an optgroup element, which specifies a group of choice items in a select element.
Forum.Nokia.com 5 Additional WAP 1.2.1 features 5.1 Push Nokia Series 30 phone is able to receive Push Service Indication (SI) type service messages. Push service messages are an ideal way for service providers to activate users, since they can be used to notify users of updated content or to alert them about information in their areas of interest (e.g., new e-mails, changes in stock prices, flight schedule changes or news headlines). Service messages indicate downloadable content.
Forum.Nokia.com ordered in the Service Inbox and also whether the user is notified about received Service Indication. The defined priority level has the following impact: • signal-high: Notification with an SMS alert tone is presented. • signal-medium: Notification with an SMS alert tone is presented. • signal-low: No indication of received Service Indication is displayed to the user. The Service Indication is silently stored in the Service Inbox.
Forum.Nokia.com been sent, the user returns to the card/deck where s/he initiated the sending. The voice call remains active. 5.2.4 Adding a phone book entry The AddPBEntry function offers an easy way to store a phone number and a corresponding name onto the phone book application from a WML card. The service provider provides the name and number.
Forum.Nokia.com For more information about content download, please go to http://www.forum.nokia.com/. 5.6 Segmentation and Reassembly (SAR) Some of the Series 30 phones support Segmentation and Reassembly (SAR) functionality, which is an optional feature in the Wireless Transport Protocol (WTP) layer defined by the WAP Forum. SAR is used to split large WTP messages into a number of smaller datagrams and selectively retransmit failed datagrams.
Forum.Nokia.com 6 Terms and Abbreviations Term or Abbreviation Description Card Deck A single WML unit of navigation and user interface. A collection of WML cards that is the smallest downloadable unit. You cannot download a single card in a deck; you must download the entire deck. Service developers should be aware of this, and not create large applications in a single deck. A way of defining the binding between events (such as a user selection) and a task (for example, to go somewhere).
Forum.Nokia.com WSP WTAI use in specifying content and user interface for narrowband devices, including cellular phones and pagers. Wireless Session Protocol. A layer of WAP stack, which is optimized for low bandwidth bearer networks with long latency. Wireless Telephony Applications Interface. Feature that provides the means to create telephony applications by using a WAE user-agent with the appropriate WTAI function libraries.
Forum.Nokia.com 7 References GPRS-related documentation http://www.mobilegprs.com Nokia Mobile Internet Toolkit 4.0 http://forum.nokia.com Nokia Phone User's Guides http://www.nokia.com Segmentation and Re-assembly-related documentation http://forum.nokia.com WAP Push-related documentation http://forum.nokia.com Wireless application specifications http://www.openmobilealliance.
Forum.Nokia.com Appendix A. Wireless Application Protocol (WAP) Introduction The Wireless Application Protocol (WAP) is a set of protocols that allows the development of applications and services for use with mobile phones and other mobile devices. The WAP Forum maintains these protocols and their related standards and specifications. The WAP Forum consists of a number of high-tech companies from the information technology, software, and telecommunication industries.
Forum.Nokia.com Wireless Application Environment (WAE) The Wireless Application Environment (WAE) is a general-purpose application environment that uses a combination of Internet and mobile terminal technology. It provides a framework for the development of applications on a mobile terminal. WAE contains support for the following functionality: • Wireless Markup Language (WML) - a lightweight presentation language, similar to Hypertext Markup Language (HTML) but optimized for use with mobile terminals.
Forum.Nokia.com Figure 2A shows the network-related elements required for developing and offering services to mobile users. Web Server HTML WML WML HTML Filter WAP Proxy Binary Wireless Network WTA Server Binary WML Figure 2A: Elements related to mobile browsing Web server The Web server stores the applications written in WML. Alternatively, existing HTML applications can be used.
Forum.Nokia.com Build Test Sell Developing and marketing mobile applications with Nokia Go to Forum.Nokia.com 1 Forum.Nokia.com provides the tools and resources you need for content and application development as well as the channels for sales to operators, enterprises, and consumers. Forum.Nokia.com Download tools and emulators 2 Forum.Nokia.com/tools has links to tools from Nokia and other industry leaders including Borland, Adobe, AppForge, Macromedia, Metrowerks, and Sun. Forum.Nokia.
