<?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: Emergency Social Media Needs To Be Tailored To Mobile Phones As Well As Computers</title>
	<atom:link href="http://incaseofemergencyblog.com/2009/05/13/emergency-social-media-needs-to-be-tailored-to-mobile-phones-as-well-as-computers/feed/" rel="self" type="application/rss+xml" />
	<link>http://incaseofemergencyblog.com/2009/05/13/emergency-social-media-needs-to-be-tailored-to-mobile-phones-as-well-as-computers/</link>
	<description>A Citizenâ€™s Eye View of Public Preparedness</description>
	<lastBuildDate>Mon, 16 Feb 2026 13:57:48 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jonas Landgren</title>
		<link>http://incaseofemergencyblog.com/2009/05/13/emergency-social-media-needs-to-be-tailored-to-mobile-phones-as-well-as-computers/comment-page-1/#comment-32569</link>
		<dc:creator>Jonas Landgren</dc:creator>
		<pubDate>Fri, 15 May 2009 22:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://incaseofemergencyblog.com/?p=1375#comment-32569</guid>
		<description>I do believe that John is absolutely right in the observation that mobile devices are becoming more and more critical when designing apps and services for crisis communication. However, I would like to push it a bit longer and make a perhaps even stronger statement.

The only thing we will know for sure in times of large scale emergencies and crisis are that people in formal and informal response organizations will have a mobile phone in their pockets. So the challenge is not to only tailor applications for the mobile devices, but to actually rethink the complete application paradigm and shift the design to applications that truly make full use of the fact that mobile devices has completely unique features that computers still do not have. A mobile device is not a laptop or a small version of a stationary computer. In terms of a mobile phone, it is a consumer electronic product with a different set of design dimensions that crisis management software vendors still have a hard time to make use of. We need new business models, new interaction models, and new infrastructure and development models that fundamentally are different to the old &quot;we are investing in crisis-IT&quot; perspective. Most organizations are not at all interested in IT, but they are desperate for better technology use. I would argue that much can be learn from the design of social media where a completely different is emerging. The mobile device is not small laptop, it is something different and this difference should be explored. In my research group we have young ambitious students that cannot wait to lay their hands of the intellectual goods that is produced in the intersection between formal and informal organizations and crisis response.</description>
		<content:encoded><![CDATA[<p>I do believe that John is absolutely right in the observation that mobile devices are becoming more and more critical when designing apps and services for crisis communication. However, I would like to push it a bit longer and make a perhaps even stronger statement.</p>
<p>The only thing we will know for sure in times of large scale emergencies and crisis are that people in formal and informal response organizations will have a mobile phone in their pockets. So the challenge is not to only tailor applications for the mobile devices, but to actually rethink the complete application paradigm and shift the design to applications that truly make full use of the fact that mobile devices has completely unique features that computers still do not have. A mobile device is not a laptop or a small version of a stationary computer. In terms of a mobile phone, it is a consumer electronic product with a different set of design dimensions that crisis management software vendors still have a hard time to make use of. We need new business models, new interaction models, and new infrastructure and development models that fundamentally are different to the old &#8220;we are investing in crisis-IT&#8221; perspective. Most organizations are not at all interested in IT, but they are desperate for better technology use. I would argue that much can be learn from the design of social media where a completely different is emerging. The mobile device is not small laptop, it is something different and this difference should be explored. In my research group we have young ambitious students that cannot wait to lay their hands of the intellectual goods that is produced in the intersection between formal and informal organizations and crisis response.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Shea</title>
		<link>http://incaseofemergencyblog.com/2009/05/13/emergency-social-media-needs-to-be-tailored-to-mobile-phones-as-well-as-computers/comment-page-1/#comment-32377</link>
		<dc:creator>John Shea</dc:creator>
		<pubDate>Thu, 14 May 2009 00:47:36 +0000</pubDate>
		<guid isPermaLink="false">http://incaseofemergencyblog.com/?p=1375#comment-32377</guid>
		<description>That was one of the key lessons learned Janice Nall expressed at a workshop on Monday. CDC has really taken the lead on mobile communication research (NOAA is very good, as is DC gov&#039;t), but the rest of the public information apparatus needs to catch up with the need to identify appropriate delivery methods for initial and subsequent messages.  It really culminates in gov&#039;t having to rethink its audience.</description>
		<content:encoded><![CDATA[<p>That was one of the key lessons learned Janice Nall expressed at a workshop on Monday. CDC has really taken the lead on mobile communication research (NOAA is very good, as is DC gov&#8217;t), but the rest of the public information apparatus needs to catch up with the need to identify appropriate delivery methods for initial and subsequent messages.  It really culminates in gov&#8217;t having to rethink its audience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan D. Abolins</title>
		<link>http://incaseofemergencyblog.com/2009/05/13/emergency-social-media-needs-to-be-tailored-to-mobile-phones-as-well-as-computers/comment-page-1/#comment-32363</link>
		<dc:creator>Jonathan D. Abolins</dc:creator>
		<pubDate>Wed, 13 May 2009 21:15:20 +0000</pubDate>
		<guid isPermaLink="false">http://incaseofemergencyblog.com/?p=1375#comment-32363</guid>
		<description>John, thanks for this posting and covering this topic.

If soem readers are wondering what I meant by the various techniques to handle languages that aren&#039;t supported on devices, I&#039;ll give some some examples of &quot;Romanization&quot; of Arabic texts.

For Arabic, there are things such as Arabic Chat Alphabet. Wikipedia entry: http://en.wikipedia.org/wiki/Arabic_Chat_Alphabet

A good presentation on Decoding Arabic Chat: http://www.basistech.com/knowledge-center/Arabic/arabic-chat-linguistics.pdf

The same general concepts can be found for other languages, including Hebrew, Russian, Chinese, etc.

The key thing is finidng out what the non-English readers in your audience are doing with their mobile devices.  Otherwise, much effort could be spent in translating info into other languages for mobile device access but it isn&#039;t accessible when it&#039;s most needed.  Get people from the non-English reading community involved in the design and testing.</description>
		<content:encoded><![CDATA[<p>John, thanks for this posting and covering this topic.</p>
<p>If soem readers are wondering what I meant by the various techniques to handle languages that aren&#8217;t supported on devices, I&#8217;ll give some some examples of &#8220;Romanization&#8221; of Arabic texts.</p>
<p>For Arabic, there are things such as Arabic Chat Alphabet. Wikipedia entry: <a href="http://en.wikipedia.org/wiki/Arabic_Chat_Alphabet" onclick="javascript:pageTracker._trackPageview('/outbound/comment/http://en.wikipedia.org/wiki/Arabic_Chat_Alphabet');" rel="nofollow">http://en.wikipedia.org/wiki/Arabic_Chat_Alphabet</a></p>
<p>A good presentation on Decoding Arabic Chat: <a href="http://www.basistech.com/knowledge-center/Arabic/arabic-chat-linguistics.pdf" onclick="javascript:pageTracker._trackPageview('/outbound/comment/http://www.basistech.com/knowledge-center/Arabic/arabic-chat-linguistics.pdf');" rel="nofollow">http://www.basistech.com/knowledge-center/Arabic/arabic-chat-linguistics.pdf</a></p>
<p>The same general concepts can be found for other languages, including Hebrew, Russian, Chinese, etc.</p>
<p>The key thing is finidng out what the non-English readers in your audience are doing with their mobile devices.  Otherwise, much effort could be spent in translating info into other languages for mobile device access but it isn&#8217;t accessible when it&#8217;s most needed.  Get people from the non-English reading community involved in the design and testing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
