Implementation report template for the Mobile Web Application Best Practices

This document is a template that should be used to send implementation feedback for the Mobile Web Application Best Practices W3C Last Call Working Draft dated 13 July 2010 that followed the W3C Candidate Recommendation dated 11 February 2010. Submitted feedback will be used to prepare the implementation report of the document.

Implementors of the Best Practices are invited to copy this implementation report template and edit it to reflect the results of their evaluation of their Web application through the Best Practices, accompanied with their comments and feedback on the work required to implement this or that Best Practice.

Please send filled implementation reports to the publicly archived mailing list <public-bpwg-comments@w3.org> if you agree with having the results public, or to the <member-bpwg@w3.org> otherwise (please note that the archives of this second mailing-list are W3C-Member visible; also note that you will receive a message saying that your message is pending moderator action in that case. This is normal, no further action is required on your part).

Note that Web applications are not expected to implement the whole set of Best Practices. The Mobile Web Best Practices Working Group rather expects Web applications to implement one or two Best Practices, and strongly encourages implementors to provide implementation feedback on this(these) Best Practice(s) while leaving out the Best Practices that do not apply to their Web application in the table below.

The notion of Web application is precised in the specification, and includes "regular" Web pages with some elements of interactivity as well as applications running in other kinds of Web run-time such as widgets.

Anyone can submit implementation feedback.

Implementation under test

Results of checking the Web application with the Best Practices

For each Best Practice implemented by the Web application: please indicate whether the implementation complies with the Best Practice, or complies partially; please use the comments column to precise partial implementations and to include any feedback or remark you may have on the Best Practice. Feel free to provide feedback on Best Practices that are not implemented by the Web application if needed.

Best Practice Implemented Partial Comments
1. Use Cookies Sparingly
2. Use Appropriate Client-Side Storage Technologies for Local Data
3. Replicate Local Data
4. Do not Execute Unescaped or Untrusted JSON data
5. Ensure the User is Informed About Use of Personal and Device Information
6. Enable Automatic Sign-in
7. Use Transfer Compression
8. Minimize Application and Data Size
9. Avoid Redirects
10. Optimize Network Requests
11. Minimize External Resources
12. Aggregate Static Images into a Single Composite Resource (Sprites)
13. Include Background Images Inline in CSS Style Sheets
14. Cache Resources By Fingerprinting Resource References
15. Cache AJAX Data
16. Do not Send Cookie Information Unnecessarily
17. Keep DOM Size Reasonable
18. Optimize For Application Start-up Time
19. Minimize Perceived Latency
20. Design for Multiple Interaction Methods
21. Preserve Focus on Dynamic Page Updates
22. Use Fragment IDs to Drive Application View
23. Make Telephone Numbers "Click-to-Call"
24. Ensure Paragraph Text Flows
25. Ensure Consistency Of State Between Devices
26. Consider Mobile Specific Technologies for Initiating Web Applications
27. Use Meta Viewport Element To Identify Desired Screen Size
28. Prefer Server-side Detection Where Possible
29. Use Client-side Detection When Necessary
30. Use Device Classification to Simplify Content Adaptation
31. Support a non-JavaScript Variant if Appropriate
32. Offer Users a Choice of Interfaces

The document also contains a small set of advisory notes from the Mobile Web Best Practices Working Group. While implementation of these advisory notes is not required for the document to transition out of Candidate Recommendation, the group invites submitters to provide feedback on these advisory notes as well, when relevant.

Advisory note Implemented Partial Comments
1. Consider Use Of Canvas Element or SVG For Dynamic Graphics
2. Inform the User About Automatic Network Access
3. Provide Sufficient Means to Control Automatic Network Access

Francois Daoust, <fd@w3.org>
Last Modified: $Date: 2010/07/09 10:12:51 $