<?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/"
		>
<channel>
	<title>Comments on: Sydney WSG meeting Tuesday 19 August</title>
	<atom:link href="http://www.maxdesign.com.au/2008/07/13/wsg-sydney-august-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.maxdesign.com.au/2008/07/13/wsg-sydney-august-2/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 22:31:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Russ</title>
		<link>http://www.maxdesign.com.au/2008/07/13/wsg-sydney-august-2/comment-page-1/#comment-959</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Mon, 21 Jul 2008 03:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/2008/07/13/wsg-sydney-august-2/#comment-959</guid>
		<description>@ Lars Gunther

You have raised some interesting points.

Oddly enough, I have seen this debate in accessibility circles too.

The old stance was that we should provide one content to EVERYONE and then style the content different for different devices. 

After doing testing with people with users cognitive disabilities and learning difficulties it became clear that these users were not being serviced very well at all with if they were given the same content as others.

In some cases, these users needed specifically written content (simplified to key concepts) and in some cases completely reworked content (simple flash files or images instead of text). This is especially true for users with severe cognitive impairment

The same argument could be true for mobile devices. One could argue that content should be the same for everyone and that we simply change the css via media types for different devices.

However, like cognitive impaired users, mobile users may have distinctly different needs (quicker download, less graphics, simpler functions, abbreviated content etc) to those using other devices.

If that is the case, then we could easily justify creating a full rich site for most users, and a mobile-specific site for mobile devices.

The iphone site is a totally different concern. The news team have decided to build a site specifically for this device. While it could be considered the reverse of standards based development (building for a specific device rather than all devices) there may have been other motivations that were acceptable to the News team (fun, marketing etc)

An interesting debate  :)</description>
		<content:encoded><![CDATA[<p>@ Lars Gunther</p>
<p>You have raised some interesting points.</p>
<p>Oddly enough, I have seen this debate in accessibility circles too.</p>
<p>The old stance was that we should provide one content to EVERYONE and then style the content different for different devices. </p>
<p>After doing testing with people with users cognitive disabilities and learning difficulties it became clear that these users were not being serviced very well at all with if they were given the same content as others.</p>
<p>In some cases, these users needed specifically written content (simplified to key concepts) and in some cases completely reworked content (simple flash files or images instead of text). This is especially true for users with severe cognitive impairment</p>
<p>The same argument could be true for mobile devices. One could argue that content should be the same for everyone and that we simply change the css via media types for different devices.</p>
<p>However, like cognitive impaired users, mobile users may have distinctly different needs (quicker download, less graphics, simpler functions, abbreviated content etc) to those using other devices.</p>
<p>If that is the case, then we could easily justify creating a full rich site for most users, and a mobile-specific site for mobile devices.</p>
<p>The iphone site is a totally different concern. The news team have decided to build a site specifically for this device. While it could be considered the reverse of standards based development (building for a specific device rather than all devices) there may have been other motivations that were acceptable to the News team (fun, marketing etc)</p>
<p>An interesting debate  <img src='http://www.maxdesign.com.au/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars Gunther</title>
		<link>http://www.maxdesign.com.au/2008/07/13/wsg-sydney-august-2/comment-page-1/#comment-958</link>
		<dc:creator>Lars Gunther</dc:creator>
		<pubDate>Sun, 20 Jul 2008 00:19:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/2008/07/13/wsg-sydney-august-2/#comment-958</guid>
		<description>Shortest seminar ever. Creating sites for the iPhone. Should you be? No.

Seriously. You should make sites for mobile devices according to standards, and test in a reasonable assortment of UA:s. Period.

You should not make sites for the iPhone - and that includes the URL. Or is there an nokian95.news.com.au URL or operamini.news.com.au or operamobile.news.com.au. No. Case closed.

The web standards movement sees a shiny white phone and starts to sell its soul! &quot;But iPhone users are our target&quot;. I&#039;ve heard it before... &quot;MSIE users are our target...&quot;

maybe the seminar will be great. If Tim and Pete are Ok with having iphone as part of an URL, I&#039;d say they are disqualified to answer the first question, though.</description>
		<content:encoded><![CDATA[<p>Shortest seminar ever. Creating sites for the iPhone. Should you be? No.</p>
<p>Seriously. You should make sites for mobile devices according to standards, and test in a reasonable assortment of UA:s. Period.</p>
<p>You should not make sites for the iPhone &#8211; and that includes the URL. Or is there an nokian95.news.com.au URL or operamini.news.com.au or operamobile.news.com.au. No. Case closed.</p>
<p>The web standards movement sees a shiny white phone and starts to sell its soul! &#8220;But iPhone users are our target&#8221;. I&#8217;ve heard it before&#8230; &#8220;MSIE users are our target&#8230;&#8221;</p>
<p>maybe the seminar will be great. If Tim and Pete are Ok with having iphone as part of an URL, I&#8217;d say they are disqualified to answer the first question, though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

