<?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: Is anyone on staff actually reading the mobile version of your news website?</title>
	<atom:link href="http://www.ojr.org/p1815/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ojr.org/p1815/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=p1815</link>
	<description>Focusing on the future of digital journalism</description>
	<lastBuildDate>Mon, 15 Apr 2013 13:43:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Craig Saila</title>
		<link>http://www.ojr.org/p1815/#comment-2234</link>
		<dc:creator>Craig Saila</dc:creator>
		<pubDate>Mon, 25 Jan 2010 11:56:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1815#comment-2234</guid>
		<description><![CDATA[Couldn&#039;t agree more with your article (and with some of the comments in thread)...and I work at msnbc.com.

In the past year-and-a-half or so, smart phones have rapidly changed the way people consume mobile content, and it&#039;s essential mobile sites be treated with similar care as the primary websites.

If our technology could move as fast as our journalists do, responding to these changes wouldn&#039;t be a problem. The frustrating reality is that technology doesn&#039;t always work that way.

Moving away from legacy systems, for example, takes time even if the content is stored in XML (as msnbc.com&#039;s articles are). The bigger the system is, the larger the time penalty.

All of this is a long way of saying that at msnbc.com, we&#039;ve been working to create a better mobile for a while. And very shortly, we&#039;ll be releasing some foundational improvements to our story pages on both the mobile and traditional web which should help escalate mobile&#039;s status in our world. ]]></description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t agree more with your article (and with some of the comments in thread)&#8230;and I work at msnbc.com.</p>
<p>In the past year-and-a-half or so, smart phones have rapidly changed the way people consume mobile content, and it&#8217;s essential mobile sites be treated with similar care as the primary websites.</p>
<p>If our technology could move as fast as our journalists do, responding to these changes wouldn&#8217;t be a problem. The frustrating reality is that technology doesn&#8217;t always work that way.</p>
<p>Moving away from legacy systems, for example, takes time even if the content is stored in XML (as msnbc.com&#8217;s articles are). The bigger the system is, the larger the time penalty.</p>
<p>All of this is a long way of saying that at msnbc.com, we&#8217;ve been working to create a better mobile for a while. And very shortly, we&#8217;ll be releasing some foundational improvements to our story pages on both the mobile and traditional web which should help escalate mobile&#8217;s status in our world. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 64.12.116.136</title>
		<link>http://www.ojr.org/p1815/#comment-2233</link>
		<dc:creator>64.12.116.136</dc:creator>
		<pubDate>Sun, 24 Jan 2010 12:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1815#comment-2233</guid>
		<description><![CDATA[Site managers are more concerned about the technology than journalism. They have a great handle on which button to push but not enough imagination for content. It is all about color and visuals, not prose and words.

Danny L. McDaniel
Lafayette, Indiana]]></description>
		<content:encoded><![CDATA[<p>Site managers are more concerned about the technology than journalism. They have a great handle on which button to push but not enough imagination for content. It is all about color and visuals, not prose and words.</p>
<p>Danny L. McDaniel<br />
Lafayette, Indiana</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 69.107.134.49</title>
		<link>http://www.ojr.org/p1815/#comment-2232</link>
		<dc:creator>69.107.134.49</dc:creator>
		<pubDate>Sun, 24 Jan 2010 00:29:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1815#comment-2232</guid>
		<description><![CDATA[It is possible to successfully deep link to mobile websites without affecting other linking conventions. But as you point out, people on staff aren&#039;t even using their own mobile websites (and I bet even the web developers aren&#039;t visiting their own mobile sites either).

To deep link, you could really easily add a query string to the end of the URL for mobile formatted sites. For example the link:

http://www.www.ojr.org/ojr/people/robert/201001/1815/

could have some javascript to detect that you&#039;re on a mobile device and redirect you to the URL:

http://www.www.ojr.org/ojr/people/robert/201001/1815?mobile=true

This way, the link is preserved.]]></description>
		<content:encoded><![CDATA[<p>It is possible to successfully deep link to mobile websites without affecting other linking conventions. But as you point out, people on staff aren&#8217;t even using their own mobile websites (and I bet even the web developers aren&#8217;t visiting their own mobile sites either).</p>
<p>To deep link, you could really easily add a query string to the end of the URL for mobile formatted sites. For example the link:</p>
<p><a href="http://www.www.ojr.org/ojr/people/robert/201001/1815/" rel="nofollow">http://www.www.ojr.org/ojr/people/robert/201001/1815/</a></p>
<p>could have some javascript to detect that you&#8217;re on a mobile device and redirect you to the URL:</p>
<p><a href="http://www.www.ojr.org/ojr/people/robert/201001/1815?mobile=true" rel="nofollow">http://www.www.ojr.org/ojr/people/robert/201001/1815?mobile=true</a></p>
<p>This way, the link is preserved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 166.137.138.106</title>
		<link>http://www.ojr.org/p1815/#comment-2231</link>
		<dc:creator>166.137.138.106</dc:creator>
		<pubDate>Sat, 23 Jan 2010 19:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1815#comment-2231</guid>
		<description><![CDATA[And I tried to email this excellent article, but the email link doesn&#039;t work on a mobile.

Jm]]></description>
		<content:encoded><![CDATA[<p>And I tried to email this excellent article, but the email link doesn&#8217;t work on a mobile.</p>
<p>Jm</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amy Gahran</title>
		<link>http://www.ojr.org/p1815/#comment-2230</link>
		<dc:creator>Amy Gahran</dc:creator>
		<pubDate>Fri, 22 Jan 2010 18:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1815#comment-2230</guid>
		<description><![CDATA[Dead on, Robert!

A coupla things to add:

1) Often I hear news site managers excuse these major mobile gaffes by saying their news CMS can&#039;t really handle mobile. Answer: Don&#039;t use your crappy outdated print-focused CMS for mobile. Instead, pull full-content RSS feeds  from your original CMS and use that to populate a more flexible CMS that can more easily create mobile friendly content.

2) Re: making links go right to pages for mobile users, not to the mobile home page: this should be a top priority. Put a programmer on it now. It&#039;s not always trivial, but it can *always* be fixed. Mobile is a key potential ad revenue source for any news org (especially metro &amp; local venues), but only if you don&#039;t annoy the crap out of mobile users. By routing people to your mobile home page you force them to search for the content they thought they were getting in the first place -- and searching for anything on mobile, even when site search is really good, is more of a usability hassle than from a computer. I am surprised how many news orgs consider this a low priority to fix.

- Amy Gahran]]></description>
		<content:encoded><![CDATA[<p>Dead on, Robert!</p>
<p>A coupla things to add:</p>
<p>1) Often I hear news site managers excuse these major mobile gaffes by saying their news CMS can&#8217;t really handle mobile. Answer: Don&#8217;t use your crappy outdated print-focused CMS for mobile. Instead, pull full-content RSS feeds  from your original CMS and use that to populate a more flexible CMS that can more easily create mobile friendly content.</p>
<p>2) Re: making links go right to pages for mobile users, not to the mobile home page: this should be a top priority. Put a programmer on it now. It&#8217;s not always trivial, but it can *always* be fixed. Mobile is a key potential ad revenue source for any news org (especially metro &#038; local venues), but only if you don&#8217;t annoy the crap out of mobile users. By routing people to your mobile home page you force them to search for the content they thought they were getting in the first place &#8212; and searching for anything on mobile, even when site search is really good, is more of a usability hassle than from a computer. I am surprised how many news orgs consider this a low priority to fix.</p>
<p>- Amy Gahran</p>
]]></content:encoded>
	</item>
</channel>
</rss>