Lite Browsing
Documents
Download Nokia Browser Documentation, Technical Notes, White Papers and Articles.
Tools, Examples, and Tutorials
A range of applications and tutorial examples that help developers to develop a better mobile browsing experience.
Discussion
Discuss browsing issues, and help and share ideas with other developers in our Discussion Boards.
Browser Feature Tables
Compare browser characteristics. Sort and review all the device capabilities based on whatever platform you are developing for.
Learn how to optimize your mobile browser content…
Designing XHTML Mobile Profile Content v1.2
This updated document for Series 40 devices gives practical examples for developers who want to optimize their mobile browsing services for Series 40 devices with an XHTML browser.
XHTML Mobile Profile Example v1.1
This example helps you in testing your first XHTML Mobile Profile Web page. The example is closely related to the Getting Started with XHTML Mobile Profile document
Getting Started with XHTML Mobile Profile v1.1
This updated document provides an overview for developers who want to begin using the XHTML Mobile Profile (MP) to develop applications for Nokia mobile devices.
Develop content for the largest user base…
Would people on the move want to use your Web services? If the answer is yes, are you ready to serve them? Learn how to make a Web site that most users will have a great experience visiting.
Overview of Lite Browsing
More than four mobile phones are sold for every PC. There will be an estimated 1.3 billion mobile Internet users in 2008. With such huge market potential mobile browsing can offer real, attractive commercial opportunities. In addition, the mobile browsing ecosystem is maturing. Mobile browsers support XHTML (the estimated installed base is over 1.5 billion in 2007). The new .mobi top-level domain name provides an easy way to indicate to users that the site has been optimized for mobile devices (http://dotmobi.mobi). The W3C Mobile Web Initiative has released Mobile Web Best Practice 1.0 (www.w3.org/TR/mobile-bp/). A number of recent tools help in developing and testing mobile sites (http://dev.mobi). The new tools make development of mobile content cost-effective for individuals and small businesses, too, which greatly increases the mobile content provider base. With faster and cheaper transmissions end users no longer have a reason not to browse the Internet with their mobiles phones.
Why optimize your site for mobile phones?
The main reason is to guarantee that the site works with most mobile phones, thus allowing you to realize the potential of the mass market. The user should be able to have a good experience on a small screen, receive relevant information, and enjoy reasonable download cost and time. Traditional Web ads are often not visible but heavy on a mobile phone, whereas displaying ads adapted for a mobile phone provides a much better return (for example, using www.adservice.nokia.com). However, mobile users should not be restricted to the mobile site – if possible, provide a link to the full Web site, as many mobile users will want to access it at least occassionally.
Why develop for the Nokia Series 40 Browser?
Developers should pay special attention to providing a compelling experience on the Series 40 browser which is the most popular browser worldwide. The Series 40 browser provides more advanced features than the “Default Delivery Context” specified by the W3C Mobile Web Initiative. Developers should consider implementing device recognition to take full advantage of the capabilities of Series 40 phones. Using device recognition allows the site to go beyond the common capabilities when an end user has a more advanced phone.
Why use the DotMobi extension?
While it is a good idea to build a mobile-optimized site, it is even better to let the user know about it. Using a name like domain.mobi is the simplest way to do this. However, it also requires that the site follows the dotmobi Switch On Web Developer Guide (pc.mtld.mobi/documents/dotmobi_Switch_On_Web_Developer_Guide3.html) based on W3C work. The guide contains three mandatory rules: no frames, unknown browsers should be served an XHTML MP page, and www in the name is not needed.
