Loading...
Flash Player 9 (or above) is needed to view slideshows. We have detected that you do not have it on your computer.To install it, go here
-
scottpurdie favorited this 4 months ago
-
jorge.marquezm favorited this 6 months ago -
schee favorited this 11 months ago
-
ksniech favorited this 11 months ago -
wtamanaha favorited this 2 years ago
-
Added to the group movil2.0 by fgbncampus
-
scyuen favorited this 2 years ago
-
tomomi favorited this 2 years ago
-
ncho favorited this 2 years ago
-
ShawnBLU favorited this 2 years ago
-
jppaz favorited this 2 years ago
-
bbswiss favorited this 2 years ago -
jsmanrique favorited this 2 years ago
-
Added to the group Mobile 2.0 by kuchmuch
Slideshow Transcript
- Slide 1: The Truth About Mobile Web Development Standards Andrea Trasatti atrasatti@mtld.mobi dotMobi (mTLD Top Level Domain, Ltd.) © 2006 mTLD, Ltd. All rights reserved. .mobi and the .mobi logo are trademarks of mTLD, Ltd.
- Slide 2: dotMobi Mission • Internet made mobile Content and services are created to work on mobile devices • Help mobile services to grow Every computer sold, 4 mobile devices are sold. More services should be created for this growing audience • Help “mobile web” growth The web has brought information to the masses, the same must be made possible for mobile devices Growth Future of Mobile London, 14 November 2007 Andrea Trasatti 2
- Slide 3: W3C Mobile Web Initiative • Best Practices specifies best practices for Web content when accessed from mobile devices • mobileOK defines machine tests based on the Best Practices to help identify Web content developed with mobile devices in mind • Core Vocabulary defines a vocabulary about properties that are required for the development and adaptation of content for mobile devices • API defines a common API to access information in a device database according to the Core Vocabulary Future of Mobile London, 14 November 2007 Andrea Trasatti 3
- Slide 4: W3C Best Practices W3C Recommendation describing 60 Best Practices, such as: •Exploit device capabilities to provide an enhanced user experience •Take reasonable steps to work around deficient implementations •Carry out testing on actual devices as well as emulators •Provide consistent navigation mechanisms •Do not cause pop-ups or other windows to appear and do not change the current window without informing the user •Keep the number of externally linked resources to a minimum Future of Mobile London, 14 November 2007 Andrea Trasatti 4
- Slide 5: W3C mobileOK Basic Tests 1.0 mobileOK Basic Tests 1.0 • W3C Mobile Web Best Practices checker (Beta) • T.A.W. • ready.mobi Future of Mobile London, 14 November 2007 Andrea Trasatti 5
- Slide 6: W3C Core Vocabulary Core properties to create or adapt a mobile web site •Screen Size Width and height in pixel •Markup XHTML Basic 1.0, XHTML-MP, etc •Image Formats PNG, JPEG, GIF, etc •Style Sheets CSS 1.0, WCSS 1.0, CSS 2.1 Future of Mobile London, 14 November 2007 Andrea Trasatti 6
- Slide 7: W3C DDR API Standard API to access device descriptions •Identify a device •Get a property value •Extended functionalities such as device groups Future of Mobile London, 14 November 2007 Andrea Trasatti 7
- Slide 8: The truth about standards • Creating a standard is a HARD job • Standards should provide direction, tools help build applications • Standards should provide interoperability, fragmentation is not good for anyone ready.mobi, site.mobi, device database Future of Mobile London, 14 November 2007 Andrea Trasatti 8
- Slide 9: Andrea Trasatti atrasatti@mtld.mobi dotMobi (mTLD Top Level Domain, Ltd.) © 2006 mTLD, Ltd. All rights reserved. .mobi and the .mobi logo are trademarks of mTLD, Ltd.

