<?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: Best Practices: Travel Websites and Mobile</title>
	<atom:link href="http://www.tourismkeys.ca/blog/2009/08/best-practices-travel-websites-and-mobile/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tourismkeys.ca/blog/2009/08/best-practices-travel-websites-and-mobile/</link>
	<description>Tips &#38; Tools to help you make the most of the mobile and social Web</description>
	<lastBuildDate>Thu, 15 Jul 2010 08:43:12 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeremy Kressmann</title>
		<link>http://www.tourismkeys.ca/blog/2009/08/best-practices-travel-websites-and-mobile/comment-page-1/#comment-851</link>
		<dc:creator>Jeremy Kressmann</dc:creator>
		<pubDate>Fri, 11 Sep 2009 14:17:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.tourismkeys.ca/blog/?p=1545#comment-851</guid>
		<description>David, this is a great point. A lot of websites haven&#039;t quite figured out that an increasing amount of traffic is now coming from mobile and the content needs to be accessible. I think one of the few industries that&#039;s gotten it &quot;right&quot; so fair are the airline sites.

One quick update on the &quot;m.&quot; and &quot;.mobi&quot; rule you raised - a mobile-optimized site doesn&#039;t need to have these modifiers in the URL. Our company has created a few that simply redirect the user from the main URL with no other action necessary. Check out our trends and insights blog on mobile for more info: www.mobilebehavior.com/next-great-thing</description>
		<content:encoded><![CDATA[<p>David, this is a great point. A lot of websites haven&#8217;t quite figured out that an increasing amount of traffic is now coming from mobile and the content needs to be accessible. I think one of the few industries that&#8217;s gotten it &#8220;right&#8221; so fair are the airline sites.</p>
<p>One quick update on the &#8220;m.&#8221; and &#8220;.mobi&#8221; rule you raised &#8211; a mobile-optimized site doesn&#8217;t need to have these modifiers in the URL. Our company has created a few that simply redirect the user from the main URL with no other action necessary. Check out our trends and insights blog on mobile for more info: <a href="http://www.mobilebehavior.com/next-great-thing" rel="nofollow">http://www.mobilebehavior.com/next-great-thing</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GreenSudbury</title>
		<link>http://www.tourismkeys.ca/blog/2009/08/best-practices-travel-websites-and-mobile/comment-page-1/#comment-845</link>
		<dc:creator>GreenSudbury</dc:creator>
		<pubDate>Mon, 07 Sep 2009 17:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.tourismkeys.ca/blog/?p=1545#comment-845</guid>
		<description>Thanks Todd: 
I like that you are also exploring some of the more cutting edge mapping and mobile applications. I&#039;ve just started a GreeenSudbury map at OpenGreenMap.org and realize there is so much to learn about Google Earth, GPS etc. I post a daily news roundup from Northern Ontario at http://GreenSudbury.ca and often check your great stories and informative posts. 
Keep up the good work1</description>
		<content:encoded><![CDATA[<p>Thanks Todd:<br />
I like that you are also exploring some of the more cutting edge mapping and mobile applications. I&#8217;ve just started a GreeenSudbury map at OpenGreenMap.org and realize there is so much to learn about Google Earth, GPS etc. I post a daily news roundup from Northern Ontario at <a href="http://GreenSudbury.ca" rel="nofollow">http://GreenSudbury.ca</a> and often check your great stories and informative posts.<br />
Keep up the good work1</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Janes</title>
		<link>http://www.tourismkeys.ca/blog/2009/08/best-practices-travel-websites-and-mobile/comment-page-1/#comment-842</link>
		<dc:creator>David Janes</dc:creator>
		<pubDate>Sat, 05 Sep 2009 14:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.tourismkeys.ca/blog/?p=1545#comment-842</guid>
		<description>I think with WAP it doesn&#039;t really matter, unless you&#039;re getting into graphics. Text will resize to the appropriate sign anyway.

If you use an automatic redirect to the mobile, it won&#039;t matter if you link back to the main site: when they click on the link, they&#039;ll just end up back on the mobile site!</description>
		<content:encoded><![CDATA[<p>I think with WAP it doesn&#8217;t really matter, unless you&#8217;re getting into graphics. Text will resize to the appropriate sign anyway.</p>
<p>If you use an automatic redirect to the mobile, it won&#8217;t matter if you link back to the main site: when they click on the link, they&#8217;ll just end up back on the mobile site!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wendy Mac</title>
		<link>http://www.tourismkeys.ca/blog/2009/08/best-practices-travel-websites-and-mobile/comment-page-1/#comment-840</link>
		<dc:creator>Wendy Mac</dc:creator>
		<pubDate>Thu, 03 Sep 2009 15:52:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.tourismkeys.ca/blog/?p=1545#comment-840</guid>
		<description>I&#039;m thinking we&#039;re going to opt for the server side redirect to our new WAP pages for handhelds by editing the .htaccess file and including the code found on this helpful site.
http://dev-tips.com/featured/redirect-iphone-blackberry-palm-requests-with-htaccess

That way, the iphone, blackberry and palm apps will automatically be shown the new url.

Of course I&#039;ll always include a link back to the main site.
Any advice on the screen dimensions we should be designing for if using a universal redirect such as this?</description>
		<content:encoded><![CDATA[<p>I&#8217;m thinking we&#8217;re going to opt for the server side redirect to our new WAP pages for handhelds by editing the .htaccess file and including the code found on this helpful site.<br />
<a href="http://dev-tips.com/featured/redirect-iphone-blackberry-palm-requests-with-htaccess" rel="nofollow">http://dev-tips.com/featured/redirect-iphone-blackberry-palm-requests-with-htaccess</a></p>
<p>That way, the iphone, blackberry and palm apps will automatically be shown the new url.</p>
<p>Of course I&#8217;ll always include a link back to the main site.<br />
Any advice on the screen dimensions we should be designing for if using a universal redirect such as this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Janes</title>
		<link>http://www.tourismkeys.ca/blog/2009/08/best-practices-travel-websites-and-mobile/comment-page-1/#comment-837</link>
		<dc:creator>David Janes</dc:creator>
		<pubDate>Mon, 31 Aug 2009 13:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.tourismkeys.ca/blog/?p=1545#comment-837</guid>
		<description>Yes, this is an excellent point. Note that Google&#039;s first big breakthrough (in the web world) was that the search page should minimize distractions - a field &amp; a couple of buttons. This model has to be everywhere in mobile.

On the iPhone, any place you _display_ a telephone number should be click to automatically dial it! I believe this will work on the BlackBerry too, but I&#039;m not sure if non-sophisticated browsers on Nokias and what-have-you will recognize the &quot;tel:&quot; URL link to automatically dial. Ah well.</description>
		<content:encoded><![CDATA[<p>Yes, this is an excellent point. Note that Google&#8217;s first big breakthrough (in the web world) was that the search page should minimize distractions &#8211; a field &amp; a couple of buttons. This model has to be everywhere in mobile.</p>
<p>On the iPhone, any place you _display_ a telephone number should be click to automatically dial it! I believe this will work on the BlackBerry too, but I&#8217;m not sure if non-sophisticated browsers on Nokias and what-have-you will recognize the &#8220;tel:&#8221; URL link to automatically dial. Ah well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd Lucier</title>
		<link>http://www.tourismkeys.ca/blog/2009/08/best-practices-travel-websites-and-mobile/comment-page-1/#comment-834</link>
		<dc:creator>Todd Lucier</dc:creator>
		<pubDate>Sat, 29 Aug 2009 23:49:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.tourismkeys.ca/blog/?p=1545#comment-834</guid>
		<description>Thanks David.
I had a thought the other day that as screen size decreases, the time commitment of the user decreases as well.  Mobile sites need to get to the point much more quickly than websites in general - NO DISTRACTIONS.  Handheld users are even more likely to be multi-tasking and want the information NOW.  It also needs to be place relevant.  It has to answer my needs as I stand HERE in your community or en route.
So DMO&#039;s and travel regions need to be smart about their mobile Web presence and design it with a deep understanding of the needs of travelers in their region.
Lastly - make sure your phone number is always prominent.  Since this mobile user is holding a phone, you might intuit, that they would appreciate being able to call someone.
Thanks again David.</description>
		<content:encoded><![CDATA[<p>Thanks David.<br />
I had a thought the other day that as screen size decreases, the time commitment of the user decreases as well.  Mobile sites need to get to the point much more quickly than websites in general &#8211; NO DISTRACTIONS.  Handheld users are even more likely to be multi-tasking and want the information NOW.  It also needs to be place relevant.  It has to answer my needs as I stand HERE in your community or en route.<br />
So DMO&#8217;s and travel regions need to be smart about their mobile Web presence and design it with a deep understanding of the needs of travelers in their region.<br />
Lastly &#8211; make sure your phone number is always prominent.  Since this mobile user is holding a phone, you might intuit, that they would appreciate being able to call someone.<br />
Thanks again David.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
