W3C home > Mailing lists > Public > public-bpwg@w3.org > August 2009

Re: ISSUE-290 (hollobit): Desirable Goal of MWABP statements [Mobile ?Web Applications Best Practices]

From: Adam Connors <adamconnors@google.com>
Date: Tue, 11 Aug 2009 11:43:00 +0100
Message-ID: <393b77970908110343p42f95224id01b5a14de8a585e@mail.gmail.com>
To: Mobile Web Best Practices Working Group WG <public-bpwg@w3.org>
Cc: (wrong string) 전종홍 <hollobit@etri.re.kr>
As agreed at a previous meeting, I have gone through the desirable goals
proposed by Jonathan with an eye to updating the document where appropriate
and commenting where I feel the intent of the desirable goals is captured
elsewhere.

It's worth noting that the document has evolved somewhat since these goals
were first written (apologies for the slow response Jonathan) and I feel
many of the points have already seeped into the document in the form of
broader feedback.

Thanks,

Adam.

>
> 3.1.1 Use Cookies for Simple Client-Side State<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#bp-data-cookies> .
> 3.1.1.3 Desirable Goal of this statement
>
> [Improving User Experience], [Better security]
>
>
This is now "Use Cookies Sparingly"
[user experience] --> already covered: "excessive amounts can negatively
impact performance"
[better security] --> I don't think this is a goal of this particular BP.

>
> 3.1.2 Use HTML5 Client-Side Storage for Local Data Model<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#bp-data-html5> .
> 3.1.2.3 Desirable Goal of this statement
>
> [Improving User Experience], [Performance Improvement]
>
>
Often these two goals are very closely connected and will appear together.
In my mind this para. captures the intent here:

"...is a powerful technique that brings Web applications into parity with
native applications in terms of start-up and responsiveness".

I don't think much would be gained by explicitly saying we're talking about
user-experience / performance since this is an implicit goal that cuts
across the whole document. As captured in 1.3.1

"...to enable a better user experience..."


> 3.1.3 Replicate Local State Changes to a Server When Possible<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#bp-data-server> .
> 3.1.3.3 Desirable Goal of this statement
>
> [Improving User Experience], [Performance Improvement]
>
>

Again, I think these two goals are one of the fundamental goals of the
document and captured in 1.3.1 so don't need to be called out.


> 3.2.1 Do not Execute Untrusted JavaScript<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#d1e542> .
> 3.2.1.3 Desirable Goal of this statement
>
> [Better security]
>
>
>

This BP is in the section: "Security and Privacy" so I think this goal is
captured.

> 3.3.1 Inform the User About Automatic Network Access<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-inform-automation> .
> 3.3.1.3 Desirable Goal of this statement
>
> [Improving User Experience], [Performance Improvement]
>
>
>

Applies to all, captured in 1.3.1


> 3.3.2 Provide Sufficient Means to Control Automatic Network Access<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e631> .
> 3.3.2.3 Desirable Goal of this statement
>
> [Resource Saving], [Improving User Experience]
>
>
>

See 3.3.1.1 "Network traffic on a mobile device incurs a cost (both in terms
of data-charges and battery-life)..."


> 3.3.3 Ensure the User is Informed About Use of Personal and Device
> Information<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-inform-personalinfo> .
> 3.3.3.3 Desirable Goal of this statement
>
> [Improving User Experience]
>
>
> 3.4.1 Use Transfer Compression<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-conserve-compress> .
> 3.4.1.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
>

This BP is in the section "Conservative Use of Resources" so this is already
covered.


> 3.4.2 Minimize Application Size<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-conserve-contentsize> .
> 3.4.2.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
>

Ditto... See also 3.4 "The most effective way to ensure that applications
run smoothly and with low latency is to take steps to ensure minimal use of
resources"


> 3.4.3 Avoid Redirects<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-redirect-minimize> .
> 3.4.3.3 Desirable Goal of this statement
>
> [Performance Improvement], [Improving User Experience]
>
>
>

ditto

> 3.4.4 Optimize Network Requests<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#bp-conserve-requests> .
> 3.4.4.3 Desirable Goal of this statement
>
> [Performance Improvement], [Resource Saving]
>
>
> 3.4.5 Minimize External Resources<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-conserve-ext-files> .
> 3.4.5.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
> 3.4.6 Consider Inlining Small Stylesheets and Script Resources<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e869> .
> 3.4.7.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
> 3.4.7 Aggregate Static Images ("Sprites") into a Single Composite Resource<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#d1e8981> .
> 3.4.7.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
> 3.4.8 Include Background Images Inline in CSS Style Sheets<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#d1e928> .
> 3.4.8.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
> 3.4.9 Use Fingerprinting to Cache Dynamic Resources<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e948> .
> 3.4.9.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
> 3.4.10 Cache AJAX Data<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#d1e972> .
> 3.4.10.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
> 3.4.11 Use Power-Efficient Methods<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-conserve-power> .
> 3.4.11.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>   3.4.12 Minimize DOM Manipulation<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-conserve-dom> .
> 3.4.12.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
> 3.4.13 Reduce Cookie Size<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e1038> .
> 3.4.13.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
> 3.4.14 Don't Send Cookie Information Unnecessarily<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e1059> .
> 3.4.14.3 Desirable Goal of this statement
>
> [Resource Saving], [Performance Improvement]
>
>
> 3.5.1 Design for Multiple Interaction Methods<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e1117> .
> 3.5.1.3 Desirable Goal of this statement
>
> [Improving User Experience], [Compatibility improvement]
>
>
>

compatibility improvement == "Handling Variations in Delivery Context"


> 3.5.2 Use Scripting to Improve Perceived Performance<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-presentation-ui-scripting> .
> 3.5.2.3 Desirable Goal of this statement
>
> [Improving User Experience], [Performance Improvement]
>
>
> 3.5.3 Preserve Focus on Dynamic Page Updates<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-presentation-focus> .
> 3.5.3.3 Desirable Goal of this statement
>
> [Improving User Experience]
>
>
> 3.5.4 Group Closely Coupled Views<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e1211> .
> 3.5.4.3 Desirable Goal of this statement
>
> [Improving User Experience]
>
>
> 3.5.5 Use Fragment IDs to Maintain Application History<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#d1e1229> .
> 3.5.5.3 Desirable Goal of this statement
>
> [Improving User Experience]
>
>
> 3.5.6 Make Telephone Numbers "Click-to-Call"<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#bp-interaction-uri-schemes> .
> 3.5.6.3 Desirable Goal of this statement
>
> [Improving User Experience]
>
>
> 3.5.7 Ensure Paragraph Text Flows<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e1276> .
> 3.5.7.3 Desirable Goal of this statement
>
> [Improving User Experience], [Compatibility improvement]
>
>
> 3.5.8 Separate Rarely Used Functionality<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e1300> .
> 3.5.8.3 Desirable Goal of this statement
>
> [Improving User Experience], [Resource Saving]
>
>
> 3.5.9 Enable Progressive Rendering<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e1332> .
> 3.5.9.3 Desirable Goal of this statement
>
> [Improving User Experience], [Performance Improvement]
>
>
> 3.5.10 Ensure Consistency Between Desktop and Mobile<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e1356> .
> 3.5.10.3 Desirable Goal of this statement
>
> [Improving User Experience], [Compatibility improvement]
>
>
> 3.5.11 Consider Using Push<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#bp-conserve-usepush> .
> 3.5.11.3 Desirable Goal of this statement
>
> [Improving User Experience]
>
>
> 3.5.12 Use Canvas Tag For Dynamic Graphics<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#bp-canvas> .
> 3.5.12.3 Desirable Goal of this statement
>
> [Improving User Experience]
>
>
> 3.5.13 Use viewport Meta Tag To Identify Desired Screen Size<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20091303#bp-viewport> .
> 3.5.13.3 Desirable Goal of this statement
>
> [Improving User Experience]
>
>
> 3.6.1 Use Server-side Capability Detection<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-devcap-detection> .
> 3.6.1.3 Desirable Goal of this statement
>
> [Compatibility improvement], [Resource Saving]
>
>
> 3.6.2 Use Client-side Capability Detection for Dynamic Device State<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-devcap-scripting> .
> 3.6.2.3 Desirable Goal of this statement
>
> [Compatibility improvement], [Maximizing Development Productivity]
>
>
> 3.6.3 Use Device Classification to Simplify Content Adaptation<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-devcap-classify> .
> 3.6.3.3 Desirable Goal of this statement
>
> [Maximizing Development Productivity], [Compatibility improvement]
> 3.6.4 Support a non-JavaScript Variant if Possible<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#bp-devcap-scripting-support> .
> 3.6.4.3 Desirable Goal of this statement
>
> [Maximizing Development Productivity], [Compatibility improvement]
>
>
> 3.6.5 Offer Users a Choice of Interfaces<http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e1515> .
> 3.6.5.3 Desirable Goal of this statement
>
> [Improving User Experience], [Compatibility improvement]
>
>
>
>
>
> Id like to discuss about this issue and my proposal.
>
>
>
> Best Regards,
>
>
>
> --- Jonathan Jeon
>
>
>
> -----Original Message-----
> From: public-bpwg-request@w3.org [mailto:public-bpwg-request@w3.org] On
> Behalf Of Mobile Web Best Practices Working Group Issue Tracker
> Sent: Thursday, March 19, 2009 9:52 PM
> To: public-bpwg@w3.org
> Subject: ISSUE-290 (hollobit): Desirable Goal of MWABP statements [Mobile
> Web Applications Best Practices]
>
>
>
>
>
>
>
> ISSUE-290 (hollobit): Desirable Goal of MWABP statements [Mobile Web
> Applications Best Practices]
>
>
>
> http://www.w3.org/2005/MWI/BPWG/Group/track/issues/290
>
>
>
> Raised by: Jonathan Jeon
>
> On product: Mobile Web Applications Best Practices
>
>
>
> To help people understand MWABP, we'd better to add the concept of
> desirable goal.
>
>
>
>
>
>
>
>
>
>
>
Received on Tuesday, 11 August 2009 10:43:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:54 UTC