1 / 33

W3C Mobile Web Initiative and Default delivery context

W3C Mobile Web Initiative and Default delivery context. Presented by : Dinesh Kumar Chobey W3C India E-mail : dinesh.kumar@ieee.org. Mobile environment. Mobile media has increasingly becoming the preferred medium of communication

duquette
Download Presentation

W3C Mobile Web Initiative and Default delivery context

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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

  7. Limitations of Mobile Devices • 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

  8. Mobile Web Best Practices • "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.

  9. 10 ways to mobilize 1. Design for One Web Content designed with diverse devices in mind reduces cost, increases flexibility, and reaches the needs of more people. 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. 2. Rely on Web standards In the highly fragmented market of devices and browsers, standards are the best guarantee for interoperability.

  10. 10 ways to mobilize (Contd..) 4. Be cautious of device limitations When choosing to use a particular Web technology, consider that mobile devices vary greatly in capability. 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. 5. Optimize navigation Simple navigation and typing become critical when using a small screen and keyboard, and limited bandwidth.

  11. 10 ways to mobilize (Contd..) 7. Keep it small Smaller sites make users happier by costing less in time and money. 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. 8. Use the network sparingly Web protocol features can help improve the user experience by reducing the impact of network bottlenecks and latencies. 10. Think of users on the go • Web users on the go want compact information when • time is short and distractions many.

  12. Lowest Common Denominator Approach: • 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. http://www.w3.org/TR/mobile-bp/

  13. DDC

  14. 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.

  15. Problem with Indian Languages

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

  17. different Indian language support handsets

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

  19. 65536 16bit • 256K 18bit • 16M 24bit

  20. 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.

  21. Proposed I-DDC

  22. W3C Mobile-OK Checker • 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.

  23. relationship between MobileOk library and other W3C Standards. Implementation of tests in Java Best Practices Tests 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 Mobile Web Best Practices 1.0 Page Size :[Page_Size_usable] Divide pages into usable but limited size portions Mobile-OK Checker Java Library

  24. Mobile-OK Checker Interface

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

  26. Current activities: 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 3. Build a fresh Default Delivery Content (DDC ) for Indic Scripts 4. Implementation of W3C Mobile OK Checker – Initiated with Hindi Language

  27. 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.in

  28. Thank You!!

More Related