<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Adtools &#187; best practice</title>
	<atom:link href="http://blog.adtools.co.uk/tag/best-practice/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.adtools.co.uk</link>
	<description>Advertising Operations &#38; Technology</description>
	<lastBuildDate>Fri, 25 Nov 2011 13:21:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>W3C Announce Best Practice in Mobile App Design &amp; Development</title>
		<link>http://blog.adtools.co.uk/w3c-announce-best-practice-in-mobile-app-design-development/877/</link>
		<comments>http://blog.adtools.co.uk/w3c-announce-best-practice-in-mobile-app-design-development/877/#comments</comments>
		<pubDate>Tue, 04 Jan 2011 15:18:53 +0000</pubDate>
		<dc:creator>Sean</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Misc]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[apps]]></category>
		<category><![CDATA[best practice]]></category>
		<category><![CDATA[w3c]]></category>

		<guid isPermaLink="false">http://blog.adtools.co.uk/?p=877</guid>
		<description><![CDATA[W3C have brought together some salient points to remember when developing mobile products/apps. I&#8217;m sure we&#8217;re well aware of a lot of these but this doc provides a handy reference to the most important of them. http://www.w3.org/TR/mwabp/ Use Cookies Sparingly Use Appropriate Client-Side Storage Technologies for Local Data Replicate Local Data Do not Execute Unescaped [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://blog.adtools.co.uk/wp-content/uploads/2011/01/W3C_logo-300x180.jpg" alt="" title="W3C_logo" width="200" height="120" class="alignright size-medium wp-image-883" /></a>W3C have brought together some salient points to remember when developing mobile products/apps. I&#8217;m sure we&#8217;re well aware of a lot of these but this doc provides a handy reference to the most important of them.</p>
<p><a href="http://www.w3.org/TR/mwabp/">http://www.w3.org/TR/mwabp/</a></p>
<ol>
<li>Use Cookies Sparingly</li>
<li>Use Appropriate Client-Side Storage Technologies for Local Data</li>
<li>Replicate Local Data</li>
<li>Do not Execute Unescaped or Untrusted JSON data</li>
<li>Ensure the User is Informed About Use of Personal and Device Information</li>
<li>Enable Automatic Sign-in</li>
<li>Use Transfer Compression</li>
<li>Minimize Application and Data Size</li>
<li>Avoid Redirects</li>
<li>Optimize Network Requests</li>
<li>Minimize External Resources</li>
<li>Aggregate Static Images into a Single Composite Resource (Sprites)</li>
<li>Include Background Images Inline in CSS Style Sheets</li>
<li>Cache Resources By Fingerprinting Resource References</li>
<li>Cache AJAX Data</li>
<li>Do not Send Cookie Information Unnecessarily</li>
<li>Keep DOM Size Reasonable</li>
<li>Optimize For Application Start-up Time</li>
<li>Minimize Perceived Latency</li>
<li>Design for Multiple Interaction Methods</li>
<li>Preserve Focus on Dynamic Page Updates</li>
<li>Use Fragment IDs to Drive Application View</li>
<li>Make Telephone Numbers &#8220;Click-to-Call&#8221;</li>
<li>Ensure Paragraph Text Flows</li>
<li>Ensure Consistency Of State Between Devices</li>
<li>Consider Mobile Specific Technologies for Initiating Web Applications</li>
<li>Use Meta Viewport Element To Identify Desired Screen Size</li>
<li>Prefer Server-side Detection Where Possible</li>
<li>Use Client-side Detection When Necessary</li>
<li>Use Device Classification to Simplify Content Adaptation</li>
<li>Support a non-JavaScript Variant if Appropriate</li>
<li>Offer Users a Choice of Interfaces</li>
<li>Consider Use Of Canvas Element or SVG For Dynamic Graphics</li>
<li>Inform the User About Automatic Network Access</li>
<li>Provide Sufficient Means to Control Automatic Network Access</li>
</ol>
<p><a href="http://www.w3.org/TR/mwabp/">http://www.w3.org/TR/mwabp/</a></p>
<p>				<!-- Social Sharing Toolkit v2.0.4 | http://www.marijnrongen.com/wordpress-plugins/social_sharing_toolkit/ --></p>
<div class="mr_social_sharing_wrapper"><span class="mr_social_sharing_top"><iframe src="https://www.facebook.com/plugins/like.php?locale=en_US&amp;href=http%3A%2F%2Fblog.adtools.co.uk%2Fw3c-announce-best-practice-in-mobile-app-design-development%2F877%2F&amp;layout=standard&amp;show_faces=false&amp;width=51px&amp;height=24px" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:51px; height:24px;" allowTransparency="true"></iframe></span><span class="mr_social_sharing_top"><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.adtools.co.uk%2Fw3c-announce-best-practice-in-mobile-app-design-development%2F877%2F&amp;text=W3C+Announce+Best+Practice+in+Mobile+App+Design+%26+Development&amp;via=adops" target="_blank" class="mr_social_sharing_popup_link"><img src="http://blog.adtools.co.uk/wp-content/plugins/social-sharing-toolkit/images/buttons/twitter.png" alt="Share on Twitter" title="Share on Twitter"/></a></span><span class="mr_social_sharing_top"><g:plusone size="medium" count="false" href="http://blog.adtools.co.uk/w3c-announce-best-practice-in-mobile-app-design-development/877/"></g:plusone></span><span class="mr_social_sharing_top"><script type="IN/Share" data-url="http://blog.adtools.co.uk/w3c-announce-best-practice-in-mobile-app-design-development/877/"></script></span></div>
]]></content:encoded>
			<wfw:commentRss>http://blog.adtools.co.uk/w3c-announce-best-practice-in-mobile-app-design-development/877/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How not to deal with Adblock users</title>
		<link>http://blog.adtools.co.uk/how-not-to-deal-with-adblock-users/507/</link>
		<comments>http://blog.adtools.co.uk/how-not-to-deal-with-adblock-users/507/#comments</comments>
		<pubDate>Thu, 22 Apr 2010 08:16:34 +0000</pubDate>
		<dc:creator>Sean</dc:creator>
				<category><![CDATA[Adblocking]]></category>
		<category><![CDATA[Misc]]></category>
		<category><![CDATA[adblock]]></category>
		<category><![CDATA[best practice]]></category>

		<guid isPermaLink="false">http://blog.adtools.co.uk/?p=507</guid>
		<description><![CDATA[Techdirt reports that gaming site The Escapist has apparently banned users who mention the Firefox add-on Adblock. After much user anger they listened to their users and later un-banned those them but it seems to have left a bitter taste in the users mouths. http://techdirt.com/articles/20100420/1042189110.shtml]]></description>
			<content:encoded><![CDATA[<p>Techdirt reports that gaming site <a href="http://www.escapistmagazine.com/">The Escapist</a> has apparently banned users who mention the Firefox add-on <a href="https://addons.mozilla.org/en-US/firefox/addon/1865">Adblock</a>. After much user anger they listened to their users and later un-banned those them but it seems to have left a bitter taste in the users mouths.</p>
<p><a href="http://techdirt.com/articles/20100420/1042189110.shtml">http://techdirt.com/articles/20100420/1042189110.shtml</a><br />
				<!-- Social Sharing Toolkit v2.0.4 | http://www.marijnrongen.com/wordpress-plugins/social_sharing_toolkit/ --></p>
<div class="mr_social_sharing_wrapper"><span class="mr_social_sharing_top"><iframe src="https://www.facebook.com/plugins/like.php?locale=en_US&amp;href=http%3A%2F%2Fblog.adtools.co.uk%2Fhow-not-to-deal-with-adblock-users%2F507%2F&amp;layout=standard&amp;show_faces=false&amp;width=51px&amp;height=24px" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:51px; height:24px;" allowTransparency="true"></iframe></span><span class="mr_social_sharing_top"><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.adtools.co.uk%2Fhow-not-to-deal-with-adblock-users%2F507%2F&amp;text=How+not+to+deal+with+Adblock+users&amp;via=adops" target="_blank" class="mr_social_sharing_popup_link"><img src="http://blog.adtools.co.uk/wp-content/plugins/social-sharing-toolkit/images/buttons/twitter.png" alt="Share on Twitter" title="Share on Twitter"/></a></span><span class="mr_social_sharing_top"><g:plusone size="medium" count="false" href="http://blog.adtools.co.uk/how-not-to-deal-with-adblock-users/507/"></g:plusone></span><span class="mr_social_sharing_top"><script type="IN/Share" data-url="http://blog.adtools.co.uk/how-not-to-deal-with-adblock-users/507/"></script></span></div>
]]></content:encoded>
			<wfw:commentRss>http://blog.adtools.co.uk/how-not-to-deal-with-adblock-users/507/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

