Implementation report for the Mobile Web Application Best Practices

This document is an implementation report for the Mobile Web Application Best Practices W3C Candidate Recommendation dated 11 February 2010.

Implementation under test

Results of checking the Web application with the Best Practices

Best Practice Implemented Partial Comments
1. Use Cookies Sparingly X Used only to cache search parameters to simplify reexecuting the same search over again and to pin point specific search results for tracking.
2. Use Appropriate Client-Side Storage Technologies for Local Data X Only few data is stored for convenience. Application fails gracefully, i.e., all functions are still working even without cookies being available.
3. Replicate Local Data No data replicated
4. Do not Execute Unescaped or Untrusted JSON data X JSON is not being used, couls also be marked as N/A
5. Inform the User About Automatic Network Access There is no automatic network access
6. Provide Sufficient Means to Control Automatic Network Access There is no automatic network access
7. Ensure the User is Informed About Use of Personal and Device Information X No personal data is used, yet, could also be marked as N/A.
8. Enable Automatic Sign-in Postponed. Waiting for a T-Online crossplattform service that will enable the user to choose to automatically sing-in using his MSISDN as a means of identification.
9. Use Transfer Compression The amount of data transfered is already optimized towards mobile devices.
10. Minimize Application and Data Size X Application functionality, layout and presentation is adapted to fit the mobile device.
11. Avoid Redirects X
12. Optimize Network Requests X
13. Minimize External Resources X
14. Aggregate Static Images into a Single Composite Resource (Sprites) No static images are being used currently, could also be marked as N/A
15. Include Background Images Inline in CSS Style Sheets X
16. Cache Resources By Fingerprinting Resource References
17. Cache AJAX Data No AJAX being used
18. Do not Send Cookie Information Unnecessarily X
19. Keep DOM Size Reasonable X
20. Optimize For Application Start-up Time X
21. Minimize Perceived Latency X
22. Design for Multiple Interaction Methods X Common mobile device input methods are supported, like touch screen, stylus, cursor keys, scrollwheels, etc.
23. Preserve Focus on Dynamic Page Updates No dynamic page updates
24. Use Fragment IDs to Drive Application View
25. Make Telephone Numbers "Click-to-Call" X
26. Ensure Paragraph Text Flows X
27. Ensure Consistency Of State Between Devices No user login
28. Consider Mobile Specific Technologies for Initiating Web Applications Not yet being used. Automatic redirect based on the user agent from the desktop variant (www.autoscout24.de) to the mobile variant (m.as24.de) is in the works.
29. Use Meta Viewport Element To Identify Desired Screen Size X Only for some devices
30. Prefer Server-side Detection Where Possible X Data is adapted to the mobile device
31. Use Client-side Detection When Necessary
32. Use Device Classification to Simplify Content Adaptation X
33. Support a non-JavaScript Variant if Appropriate X
34. Offer Users a Choice of Interfaces The server side FIT application does handle this.
35. Consider Use Of Canvas Element or SVG For Dynamic Graphics

Francois Daoust, <fd@w3.org>
Last Modified: $Date: 2010/06/18 16:09:46 $