<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: SpoolCast: Mobile Apps &#8211; Web-based or Native? &#8211; Q&amp;A with Josh Clark</title>
	<atom:link href="http://www.uie.com/brainsparks/2011/02/23/spoolcast-mobile-apps-web-based-or-native-qa-with-josh-clark/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2011/02/23/spoolcast-mobile-apps-web-based-or-native-qa-with-josh-clark/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Thu, 23 May 2013 10:02:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Stephanie Rieger</title>
		<link>http://www.uie.com/brainsparks/2011/02/23/spoolcast-mobile-apps-web-based-or-native-qa-with-josh-clark/comment-page-1/#comment-157305</link>
		<dc:creator>Stephanie Rieger</dc:creator>
		<pubDate>Sat, 26 Feb 2011 11:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=3328#comment-157305</guid>
		<description>Hello,
Nice podcast! Just passing on some comments regarding certain statements related specifically to mobile web development:

&quot;HTML 5 is already mature for mobile&quot;
HTML 5 is far from mature on mobile. The support is improving but there are still many unsupported aspects across all browsers. There are also wide variations in performance rendering certain features (such as CSS 3 transforms, animations etc) almost unusable on certain browsers (or devices). 

&quot;the mobile web is astonishingly consistent&quot; 
There is lots of fragmentation, even amongst single platforms. All Android devices run the same browser, however there is fragmentation across the browsers themselves. Some of this fragmentation is simply related to the various versions (1.5, 1.6, 2.0 etc) while other aspects relate to the actual implementation of each device by a given manufacturer and/or OEM. This pattern replicates itself across platforms as well (Symbian, iOS etc.) Lots of testing is still required and design techniques focussing on flexible/adaptive design are the most successful in terms of obtaining a consistent (yet never identical) result across platforms.

&quot;all devices running a version of the same browser&quot;
This is technically true however, mostly immaterial. There is no &quot;mobile webkit&quot;. Each manufacturer that uses WebKit implements and adapts their version differently. Differences (and bugs) can be due to all sorts of factors including the performance of the device itself. Certain aspects of the latest WebKit are just not appropriate for certain classes of device. The browser is therefore adapted accordingly. (e.g. there is a new touch based WebKit browser on mid-range Nokia featurephones and, amongst other things, this browser supports a lower JavaScript version)

&quot;Opera doesn&#039;t support webkit&quot;
This is true, however there is a bigger picture here due to the goals of Opera and what their browsers are designed to do. Opera has two different mobile browsers. Opera Mini is primarily designed for simpler devices (featurephones). Pages are proxied and compressed on the Opera server, then served to the device. This enables a &#039;smartphone-like web experience&#039; on very simple devices. It also reduceds the cost of usage dramatically due to the data compression. From an accessibility point of view, this is huge and close to 100 million people use Opera Mini each month for this very reason. Opera Mini is also very popular in the US as a significant number (at least 60%) of Americans don&#039;t owen a smartphone. Opera&#039;s web standards support is excellent however Opera Mini specifically, has limitations due to the proxy architecture. Opera Mobile is their second browser, designed for smartphones. It&#039;s standards support is also excellent http://www.opera.com/docs/specs/productspecs/ and uses a proprietary layout engine named Presto.</description>
		<content:encoded><![CDATA[<p>Hello,<br />
Nice podcast! Just passing on some comments regarding certain statements related specifically to mobile web development:</p>
<p>&#8220;HTML 5 is already mature for mobile&#8221;<br />
HTML 5 is far from mature on mobile. The support is improving but there are still many unsupported aspects across all browsers. There are also wide variations in performance rendering certain features (such as CSS 3 transforms, animations etc) almost unusable on certain browsers (or devices). </p>
<p>&#8220;the mobile web is astonishingly consistent&#8221;<br />
There is lots of fragmentation, even amongst single platforms. All Android devices run the same browser, however there is fragmentation across the browsers themselves. Some of this fragmentation is simply related to the various versions (1.5, 1.6, 2.0 etc) while other aspects relate to the actual implementation of each device by a given manufacturer and/or OEM. This pattern replicates itself across platforms as well (Symbian, iOS etc.) Lots of testing is still required and design techniques focussing on flexible/adaptive design are the most successful in terms of obtaining a consistent (yet never identical) result across platforms.</p>
<p>&#8220;all devices running a version of the same browser&#8221;<br />
This is technically true however, mostly immaterial. There is no &#8220;mobile webkit&#8221;. Each manufacturer that uses WebKit implements and adapts their version differently. Differences (and bugs) can be due to all sorts of factors including the performance of the device itself. Certain aspects of the latest WebKit are just not appropriate for certain classes of device. The browser is therefore adapted accordingly. (e.g. there is a new touch based WebKit browser on mid-range Nokia featurephones and, amongst other things, this browser supports a lower JavaScript version)</p>
<p>&#8220;Opera doesn&#8217;t support webkit&#8221;<br />
This is true, however there is a bigger picture here due to the goals of Opera and what their browsers are designed to do. Opera has two different mobile browsers. Opera Mini is primarily designed for simpler devices (featurephones). Pages are proxied and compressed on the Opera server, then served to the device. This enables a &#8216;smartphone-like web experience&#8217; on very simple devices. It also reduceds the cost of usage dramatically due to the data compression. From an accessibility point of view, this is huge and close to 100 million people use Opera Mini each month for this very reason. Opera Mini is also very popular in the US as a significant number (at least 60%) of Americans don&#8217;t owen a smartphone. Opera&#8217;s web standards support is excellent however Opera Mini specifically, has limitations due to the proxy architecture. Opera Mobile is their second browser, designed for smartphones. It&#8217;s standards support is also excellent <a href="http://www.opera.com/docs/specs/productspecs/" rel="nofollow">http://www.opera.com/docs/specs/productspecs/</a> and uses a proprietary layout engine named Presto.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
