<?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>Eyeline Communications &#187; Issues</title> <atom:link href="http://www.eyeline.mobi/tag/issues/feed/" rel="self" type="application/rss+xml" /><link>http://www.eyeline.mobi</link> <description>Just another WordPress weblog</description> <lastBuildDate>Thu, 22 Jul 2010 16:00:42 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>How to Make Sure USSD Services Spread Like a Wild Fire? Continued.</title><link>http://www.eyeline.mobi/ussd/348/</link> <comments>http://www.eyeline.mobi/ussd/348/#comments</comments> <pubDate>Fri, 24 Oct 2008 04:03:36 +0000</pubDate> <dc:creator>Ivan Komarov</dc:creator> <category><![CDATA[USSD]]></category> <category><![CDATA[Issues]]></category> <category><![CDATA[LinkedIn]]></category><guid
isPermaLink="false">http://www.eyeline.mobi/blog/2008/10/24/348/</guid> <description><![CDATA[Take the most out of this amazing technology &#8212; USSD &#8212; and avoid potential pitfalls. A long and heated discussion on LinkedIn about obstacles to a faster uptake of USSD, has yielded the following list of potential and fake &#8220;issues&#8221;. Let&#8217;s continue assessing them.
3. &#8220;Sloppy interface&#8221;
Assessment: MINIMAL
Resolution:
1) Use it as an entry point to other [...]]]></description> <content:encoded><![CDATA[<p>Take the most out of this amazing technology &#8212; USSD &#8212; and avoid potential pitfalls. A long and heated discussion on LinkedIn about obstacles to a faster uptake of USSD, has yielded the following list of potential and fake &#8220;issues&#8221;. Let&#8217;s continue assessing them.</p><p>3. &#8220;Sloppy interface&#8221;</p><p
style="margin-left: 0.49in">Assessment: MINIMAL</p><p
style="margin-left: 0.49in">Resolution:</p><p
style="margin-left: 0.49in">1) Use it as an entry point to other &#8220;picturesque&#8221; interfaces</p><p
style="margin-left: 0.49in">2) Text interface works fine on any phone</p><p
style="margin-left: 0.49in">3) Easier to work with (“Google chose text vs. banners”)</p><p>4. &#8220;No standardization&#8221;</p><p
style="margin-left: 0.49in">Assessment: MINIMAL</p><p
style="margin-left: 0.49in">Resolution:</p><p
style="margin-left: 0.49in">1) USSD is defined by GSM standards</p><p
style="margin-left: 0.49in">2) USSD gateways (centers) are usually connected through a standard protocol like SMPP</p><p
style="margin-left: 0.49in">3) USSD services and applications are often supplied with USSD	center</p> ]]></content:encoded> <wfw:commentRss>http://www.eyeline.mobi/ussd/348/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How to Make Sure USSD Services Spread Like a Wild Fire?</title><link>http://www.eyeline.mobi/ussd/how-to-make-sure-ussd-services-spread-like-a-wild-fire/</link> <comments>http://www.eyeline.mobi/ussd/how-to-make-sure-ussd-services-spread-like-a-wild-fire/#comments</comments> <pubDate>Tue, 21 Oct 2008 10:24:28 +0000</pubDate> <dc:creator>Ivan Komarov</dc:creator> <category><![CDATA[USSD]]></category> <category><![CDATA[Issues]]></category> <category><![CDATA[LinkedIn]]></category><guid
isPermaLink="false">http://www.eyeline.mobi/blog/2008/10/21/how-to-make-sure-ussd-services-spread-like-a-wild-fire/</guid> <description><![CDATA[Well, take the most out of this amazing technology and avoid potential pitfalls. A long and heated discussion on LinkedIn about obstacles to a faster uptake of USSD, has yielded the following list of potentially hard and easy issues:
1. &#8220;Difficult to remember USSD codes&#8221;
Assessment: MINIMAL
Resolution:
1) Use a single point of entry for all services, like [...]]]></description> <content:encoded><![CDATA[<p>Well, take the most out of this amazing technology and avoid potential pitfalls. A long and heated discussion on LinkedIn about obstacles to a faster uptake of USSD, has yielded the following list of potentially hard and easy issues:</p><p>1. &#8220;Difficult to remember USSD codes&#8221;</p><p>Assessment: MINIMAL</p><p>Resolution:<br
/> 1) Use a single point of entry for all services, like *111#<br
/> 2) Send a Help SMS with all codes upon the first access of *111# or when selecting &#8220;Help&#8221;<br
/> 3) Don&#8217;t use *&#8211;# numbers, use real numbers (<a
href="http://eyeline.mobi/contacts/">contact us</a> to learn how) <span
id="more-347"></span></p><p>2. &#8220;It&#8217;s considered old fashioned&#8221;</p><p>Assessment: MINIMAL</p><p>Resolution:<br
/> 1) It&#8217;s the easiest entry point to any other (advanced) service – what functionality of a mobile phone can compare with a phone call 	in terms of simplicity?<br
/> 2) USSD uptake is actually growing over time<br
/> 3) Experts forecast a greater use of USSD</p><p><em>(to be continued)</em></p> ]]></content:encoded> <wfw:commentRss>http://www.eyeline.mobi/ussd/how-to-make-sure-ussd-services-spread-like-a-wild-fire/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 3/18 queries in 0.056 seconds using disk

Served from: www.eyeline.mobi @ 2010-07-30 10:40:54 -->