1. W3C MOBILE WEB INITIATIVE AND DEFAULT DELIVERY CONTEXT Presented by : Dinesh Kumar Chobey W3C India E-mail : dinesh.kumar@ieee.org

2. Mobile environment  Mobile media has increasingly becoming the preferred medium of communication  Indian Mobile Market is one of the fastest growing – has overtaken China in terms of growth  Usage of Mobile Web is growing besides the messaging services.  In the top 10 list of countries, India moved up, switching spots with Ukraine. [source : http://www.opera.com/smw]

3. Issues related to mobile web browsing :

4. Small screens as compared to Desktop computers

5. Different Screen Sizes….

6. Navigation Issues

8. Small Screen size in Mobile Phones Devices with different Screen size and Display Properties. Limited Computing capacity of the mobile handsets Mobile Networks Latest technologies available to the web designers but not supported by the mobile browsers LIMITATIONS OF MOBILE DEVICES

11. "Mobile Web Best Practices 1.0" is a W3C Web Standard that helps people design and deliver content that works well on mobile devices. By following these guidelines, content producers will broaden their audience, create effective Web sites and applications, and make browsing the Web convenient on more devices. Mobile Web Best Practices

12. 1. Design for One Web Content designed with diverse devices in mind reduces cost, increases flexibility, and reaches the needs of more people. 10 ways to mobilize 2. Rely on Web standards In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability. 3. Stay away from known hazards Thoughtful design can help reduce usability problems due to small screens and keyboards, and other features of mobile devices.

13. 4. Be cautious of device limitations When choosing to use a particular Web technology, consider that mobile devices vary greatly in capability. 10 ways to mobilize (Contd..) 5. Optimize navigation Simple navigation and typing become critical when using a small screen and keyboard, and limited bandwidth. 6. Check graphics & colors Images, colors, and style brighten content, but require care: devices may have low-contrast screens or may not support some formats.

14. 7. Keep it small Smaller sites make users happier by costing less in time and money. 10 ways to mobilize (Contd..) 8. Use the network sparingly Web protocol features can help improve the user experience by reducing the impact of network bottlenecks and latencies. 9. Help & guide user input Keyboards and other input methods on mobile devices can be tedious to use, so effective designs minimize the need for them. 10. Think of users on the go Web users on the go want compact information when time is short and distractions many.

15.  Defines a minimum set of features that a device have to support. In this case, content is developed based on these guidelines  In this approach, developers only create a single version of the content that can work fairly well on as many mobile devices as possible  The minimum set of features a device is expected to support is called the Default Delivery Context (DDC)  DDC is now part of the Mobile Web Best practices 1.0 recommendation by the W3C. Lowest Common Denominator Approach: http://www.w3.org/TR/mobile-bp/

16. DDC

17. Problems with present DDC :  This DDC has now become old as mobile supports have improved.  New mobile browsers have now implemented better technology in them.  No proper Font support for major Indian languages.  No standard for client-side scripting has been given in the DDC. But its very essential for creating non-static web pages.

18. Problem with Indian Languages

19. Issues in Indian Languages Presentation Issues Bandwidth & Cost Fonts and Rendering issues Input Service provider level issues Character encoding

20. DIFFERENT INDIAN LANGUAGE SUPPORT HANDSETS Handset CompanyModelHindiTamilMarathiGujaratiBengaliKannadaTeluguPunjabi Nokia2610 Nokia2610 YYYYYYYY Nokia6085 Nokia6085 Y - Y ----- Nokia2600 Nokia2600 Y - Y ----- Nokia1600 Nokia1600 YYYYY --- Nokia1100 Nokia1100 Y - Y ----- Nokia6020 Nokia6020 Y - Y ----- Nokia3120 Nokia3120 Y - Y ----- Nokia3220 Nokia3220 Y - Y ----- Nokia1200 Nokia1200 Y - Y ----- Nokia1650 Nokia1650 YYYYYYYY Nokia1108 Nokia1108 Y - Y ----- Nokia3100 Nokia3100 Y - Y ----- Nokia6610i Nokia6610i Y - Y ----- Nokia6610 Nokia6610 Y - Y ----- SamsungS GH-X210 Samsung SGH- X210 Y ------- MotorolaL 6 MotorolaL6 Y - Y ----- SonyEricss onJ230i SonyEricss onJ230i Y ------- LGKG110 LGKG110 Y - Y -----

21. Changes that should be incorporated in I-DDC :

23. 6553616bit 256K18bit 16M24bit

25. Client Side Scripting Maximum of designers use Java Script for client side scripting. Following issues to be dealt with while dealing with scripting :  Java script is to be processed locally on mobile. But all mobile phones do not posses that much of processing capacity.(Analysis required).  Different browsers process java Script using different technologies. (Some of them process java script on server instead of mobile handset. E.g.: Opera. )  Mobile browsers supporting java script do not support full versions of it, some features are omitted. This leads to a problem in giving version-wise standard.

26. Proposed I-DDC Delivery ContextDefault Value Usable Screen Width240px, minimum Markup Language SupportXHTML Basic 1.1 Character EncodingUTF-8 Image Format SupportJPEG, GIF89a and PNG Maximum Total Page Weight- Color Weight65536 Colors, minimum Style Sheet SupportCSS1 and CSS2 HTTPHTTP 1.1 ScriptECMA Script 3

27. MobileOK is a validation tool provided by W3C in order to deliver the Mobile Friendliness of web contents and check the level of Best Practices followed. The related specifications with Mobile-OK are: Mobile Web Best Practices 1.0 : Sixty Guidelines for delivering friendly Web content to all mobile devices. The mobileOK Basic Tests 1.0 : These tests contains the formal definitions of the tests based on Mobile Web Best practices run by Mobile-OK Checker. W3C Mobile-OK Checker

28. RELATIONSHIP BETWEEN MOBILEOK LIBRARY AND OTHER W3C STANDARDS. PAGE_SIZE_LIMIT Retrieve the document under test, if its size (excluding any redirections discussed under 2.4.4 HTTP Response) exceeds 10 kilobytes, FAIL Add to a running total (total size) the size of all the HTTP retrieve the document under test Implementation of tests in Java Best Practices Tests Mobile Web Best Practices 1.0 Page Size :[Page_Size_usabl e] Divide pages into usable but limited size portions Mobile-OK Checker Java Library

29. Mobile-OK Checker Interface

30. Stakeholders needed for enabling Mobile web in India Mobile Manufactures Content Developers Service Providers Industry and Research Institute W3C India Mobile Web Initiative in India

31. Current activities: 3. Build a fresh Default Delivery Content (DDC ) for Indic Scripts 1.Review and enhancement of refined Mobile Web Best Practices for Indic Languages 2. Inclusion of new Mobile OK Basic Tests for Indic scripts based on refined guidelines 4. Implementation of W3C Mobile OK Checker – Initiated with Hindi Language

32. Important links :  Mobile Web Initiative http://www.w3.org/standards/webdesign/mobilweb  Mobile web Best Practices http://www.w3.org/TR/mobile-bp/  Mobile OK Checker http://validator.w3.org/mobile/ Mail us at : w3cindiaoffice-dit@nic.inw3cindiaoffice-dit@nic.in

33. Thank You!!