<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Andi Friedman &#187; usability</title>
	<atom:link href="http://www.andifriedman.com/index.php/tag/usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.andifriedman.com</link>
	<description>A work in progress.</description>
	<lastBuildDate>Sun, 18 Jul 2010 18:05:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Why not SMS in Africa?</title>
		<link>http://www.andifriedman.com/index.php/2010/02/why-not-sms-in-africa/</link>
		<comments>http://www.andifriedman.com/index.php/2010/02/why-not-sms-in-africa/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 14:47:53 +0000</pubDate>
		<dc:creator>Andi</dc:creator>
				<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Strategy]]></category>
		<category><![CDATA[Africa]]></category>
		<category><![CDATA[sms]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.andifriedman.com/?p=160</guid>
		<description><![CDATA[I read an interesting post from Steve Song earlier entitled &#8220;Why SMS in Africa&#8221; which outlines why SMS will remain relevant in the African context for some time to come. I agree with Steve that both IP and non-IP technologies should be considered but want to elaborate on the challenges SMS-based service face.
Naturally, through our [...]]]></description>
			<content:encoded><![CDATA[<p>I read an interesting post from Steve Song earlier entitled &#8220;<a href="http://manypossibilities.net/2010/02/why-sms-in-africa/">Why SMS in Africa</a>&#8221; which outlines why SMS will remain relevant in the African context for some time to come. I agree with Steve that both IP and non-IP technologies should be considered but want to elaborate on the challenges SMS-based service face.</p>
<p>Naturally, through our work on <a href="http://community.mobileresearcher.com">Mobile Researcher</a> and <a href="http://www.mobenzi.com">Mobenzi</a>, we&#8217;ve had a lot of technology decisions to make along the way. It goes without saying (although I&#8217;ll say it anyway) that I do not believe in a &#8220;one technology fits all approach&#8221;. SMS is obviously great for ad hoc, instant communication and a range of other communication-oriented tasks. But it falls down in a lot of other, more complex (and sometimes more valuable) scenarios.</p>
<p><span id="more-160"></span></p>
<p>Here are 5 reasons why:</p>
<h2>1. Usability</h2>
<p>Although people are familiar with how SMS works, they aren&#8217;t normally familiar with what your service is or how <em>it</em> works. I&#8217;ve seen loads of solutions which force users to format responses (commands, requests, etc) in cryptic ways so that a system can understand them and render the correct service (e.g. looking up information). This is one of the main reasons we&#8217;ve built Mobenzi in an attempt to <a href="http://www.mobenzi.com/index.php/features/improving-the-usability-of-sms-messaging-to-computers/">improve the usability of SMS</a> by adding real people to the mix.</p>
<h2>2. Cost</h2>
<p>Although SMS costs are probably coming down (I hope?), when one considers the transactional cost of an SMS, it&#8217;s a hellishly expensive way to conduct multiple interactions with people. Cost can even be a factor with reverse-billed services because SMS has a <em>perceived </em>cost which can act as a barrier to user participation.</p>
<h2>3. Service portability</h2>
<p>If you&#8217;re planning to use a short code, you can almost forget about using the same one worldwide. It&#8217;s often difficult, expensive, and/or impossible to register the same code in different countries. This again reduces the usability of the service (or at least increases the training you need to do in each country).</p>
<h2>4. Connectivity</h2>
<p>While SMS coverage is generally much better than data coverage, it&#8217;s still patchy in areas (even in very mature mobile markets like SA). Using a system which can&#8217;t work offline (rather than a smart client application) puts you at the mercy of coverage dynamics.</p>
<h2 style="font-size: 1.5em;">5. Building for the future</h2>
<p>I don&#8217;t have anything more than anecdotes and my own experience to support this but as if you look at even the low end models being brought out these days, its a relatively small percentage that don&#8217;t have internet connectivity. If you&#8217;re going to base your service on SMS now, it seems somewhat sensible to have a medium term plan to migrate it to IP. And be prepared to expend significant resources in that process. Swapping an engine whilst in flight might not be impossible &#8211; but rather expensive I would postulate.</p>
<p>Trying to take sides or apply a &#8220;technology <em>x</em> is better than technology <em>y</em>&#8221; approach is futile and in my opinion a waste of time which could be better spent leveraging an appropriate technology to solve a problem.</p>
<p>I believe the biggest barrier to wide-spread adoption of IP-based mobile services is that operators and manufacturers are generally pretty poor at shipping &#8220;internet-ready&#8221; devices. Don&#8217;t even get me started on signing applications which are able to use protected handset APIs.  That&#8217;s a rant for another, longer blog post.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.andifriedman.com/index.php/2010/02/why-not-sms-in-africa/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
