<?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"
	>
<channel>
	<title>Comments on: Don&#8217;t design for &#8220;mobile&#8221; - design for mobility</title>
	<atom:link href="http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/</link>
	<description>Adaptive Path Blog</description>
	<pubDate>Thu, 07 Aug 2008 23:48:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Mobility Products</title>
		<link>http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/#comment-178796</link>
		<dc:creator>Mobility Products</dc:creator>
		<pubDate>Fri, 13 Jun 2008 13:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/#comment-178796</guid>
		<description>Our &lt;a href="http://www.theramedic.co.uk" rel="nofollow"&gt;&lt;b&gt;Mobility Products&lt;/b&gt;&lt;/a&gt; range includes mobility scooter, mobility equipment, mobility aids, electric adjustable bed, mobility scooters, riser recliner chair, walkers, walk in bath, adjustable bed, stair lift, electrical mobility in UK.</description>
		<content:encoded><![CDATA[<p>Our <a href="http://www.theramedic.co.uk" rel="nofollow"><b>Mobility Products</b></a> range includes mobility scooter, mobility equipment, mobility aids, electric adjustable bed, mobility scooters, riser recliner chair, walkers, walk in bath, adjustable bed, stair lift, electrical mobility in UK.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Imran Sobh</title>
		<link>http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/#comment-175839</link>
		<dc:creator>Imran Sobh</dc:creator>
		<pubDate>Sat, 05 Jan 2008 00:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/#comment-175839</guid>
		<description>Although it is important to design for mobility, I think there is a lot of value in designing for situations as well. It's a subtle difference, and it emphasizes the unchanging elements of a context, whether it is physical, social, or informational. The idea of a hybrid context sounds about right. It's the middle ground between sitting at a desk in front of a screen and grabbing the info of the closest high quality sushi restaurant. I would venture to say that the hybrid context is where most of our living happens. I don't have statistics to back me up, but I would argue that the most meaningful usage of mobile devices happens in established places, such as home/work/school rather than on streets, buses, or other highly dynamic environments.

Like you said in your post, in those contexts, the need is for get-in-get out experiences, which a lot of times amount to simply finding the best shortcuts for input or searching (ie, GPS for location based services instead of typing). The hybrid context seems like a rich area that can provide for deeper needs, and where both the form and function play a balanced role. Perhaps mobile social applications become more useful in that case.

Just some thoughts...</description>
		<content:encoded><![CDATA[<p>Although it is important to design for mobility, I think there is a lot of value in designing for situations as well. It&#8217;s a subtle difference, and it emphasizes the unchanging elements of a context, whether it is physical, social, or informational. The idea of a hybrid context sounds about right. It&#8217;s the middle ground between sitting at a desk in front of a screen and grabbing the info of the closest high quality sushi restaurant. I would venture to say that the hybrid context is where most of our living happens. I don&#8217;t have statistics to back me up, but I would argue that the most meaningful usage of mobile devices happens in established places, such as home/work/school rather than on streets, buses, or other highly dynamic environments.</p>
<p>Like you said in your post, in those contexts, the need is for get-in-get out experiences, which a lot of times amount to simply finding the best shortcuts for input or searching (ie, GPS for location based services instead of typing). The hybrid context seems like a rich area that can provide for deeper needs, and where both the form and function play a balanced role. Perhaps mobile social applications become more useful in that case.</p>
<p>Just some thoughts&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peterme</title>
		<link>http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/#comment-175824</link>
		<dc:creator>peterme</dc:creator>
		<pubDate>Thu, 03 Jan 2008 16:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/#comment-175824</guid>
		<description>Tamlyn--

I don't disagree. I didn't want to drag the post on too long, but there's definitely something of a hybrid context on transit, where you do have long periods of relatively sedentary time. I've actually come to believe that iPhone is the perfect device for this context -- thanks to videos and video podcasts, games, and always-on connectivity, I can remain engaged while just sitting on the train. In fact, it's better in this context than in a true mobility context, because the nature of iPhone means it requires a lot of attention to use, which is not desirable when your environment is dynamic.</description>
		<content:encoded><![CDATA[<p>Tamlyn&#8211;</p>
<p>I don&#8217;t disagree. I didn&#8217;t want to drag the post on too long, but there&#8217;s definitely something of a hybrid context on transit, where you do have long periods of relatively sedentary time. I&#8217;ve actually come to believe that iPhone is the perfect device for this context &#8212; thanks to videos and video podcasts, games, and always-on connectivity, I can remain engaged while just sitting on the train. In fact, it&#8217;s better in this context than in a true mobility context, because the nature of iPhone means it requires a lot of attention to use, which is not desirable when your environment is dynamic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antoine Valot</title>
		<link>http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/#comment-175822</link>
		<dc:creator>Antoine Valot</dc:creator>
		<pubDate>Thu, 03 Jan 2008 11:02:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/#comment-175822</guid>
		<description>Good points, but you ought to take another look at iPhone, which is heralding the PC web experience on a mobile device. Safari on iPhone is full-fledged, and apart from Flash content, everything works on it.

Still, many web apps for iPhone miss opportunities to integrate with the circumstances and conditions of use. Your underlying point still applies, even without technological limitations.</description>
		<content:encoded><![CDATA[<p>Good points, but you ought to take another look at iPhone, which is heralding the PC web experience on a mobile device. Safari on iPhone is full-fledged, and apart from Flash content, everything works on it.</p>
<p>Still, many web apps for iPhone miss opportunities to integrate with the circumstances and conditions of use. Your underlying point still applies, even without technological limitations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tamlyn Rhodes</title>
		<link>http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/#comment-175821</link>
		<dc:creator>Tamlyn Rhodes</dc:creator>
		<pubDate>Thu, 03 Jan 2008 10:38:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2008/01/02/dont-design-for-mobile-design-for-mobility/#comment-175821</guid>
		<description>When I'm sat at a PC I'm usually working and I want a straightforward, get-to-the-point experience. When I'm on my mobile I'm usually killing time waiting for the bus, sitting on the train or waiting for a friend and I want to explore and be distracted!

OK, thats not 100% true but my point is that the type of experience depends on more than location and mobility. When I'm using Google Maps I expect the same simple interface whether I'm mobile or not.</description>
		<content:encoded><![CDATA[<p>When I&#8217;m sat at a PC I&#8217;m usually working and I want a straightforward, get-to-the-point experience. When I&#8217;m on my mobile I&#8217;m usually killing time waiting for the bus, sitting on the train or waiting for a friend and I want to explore and be distracted!</p>
<p>OK, thats not 100% true but my point is that the type of experience depends on more than location and mobility. When I&#8217;m using Google Maps I expect the same simple interface whether I&#8217;m mobile or not.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
