<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: SMS-Chat Revisited</title>
	<link>http://mobilitysite.com/2008/03/sms-chat-revisited/</link>
	<description>Mobility News, Reviews, and Views</description>
	<pubDate>Tue, 02 Dec 2008 07:45:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Martijn Brouns</title>
		<link>http://mobilitysite.com/2008/03/sms-chat-revisited/#comment-4259</link>
		<dc:creator>Martijn Brouns</dc:creator>
		<pubDate>Wed, 26 Mar 2008 10:30:10 +0000</pubDate>
		<guid>http://mobilitysite.com/2008/03/sms-chat-revisited/#comment-4259</guid>
		<description>Thanks for summing up these valuable considerations. This is what helps the industry improve the end-user experience. It also perfectly supports some previous studies we did as a company a little while back!

We have consider though what the target audience of an SMS Chat service is as this heavily impacts the design priniciples of such a service.

In my opinion SMS Chat is (contrary to community based chat services like MSN) aimed at improving the plain SMS services everybody knows. In other words: it's not targeted at a certain community but at the mass.

Design criteria for mass communication services are:
- simple user interface (like voice, sms, google, etc)
- high reliability (you rely on SMS so it should work ALWAYS)
- interoperability (as you rely on messages to be received)

Looking at you SMS Chat suggestions, the question should be raised what is required to implement on a device/client and what can be dealt with in the network?

Looking at the list of your requirements (see below for a summary), most suggestions depend on a specific handset and/or client. In most cases (#1 to 14) this functionality is already available although neither wide-spead not standardised. An d that is EXACTLY what holds us back from making SMS Chat interesting. It's of no use downloading rich clients if the recipient doesn't see my message enrichments, right?

For mass communication services interoperability and standardisation is KEY. Thus, we may be best of (at least as long as dievces and clients are not standardised) making a number of network based improvements for the functionality you suggest.

The feature below remain to be highly client specific and applicability depends on users buying speicifc handsets and/or downloading specific client applications.
1.  Message appearance on device - 
2.  Ability to copy/paste/etc
3.  Ability to autocapitalize
4.  Predictive text support
5.  Hyperlink support
6.  Sort, tag, group messages
7.  Emoticon gallery
8.  Larger input panel
9.  Send button as softkey
10. Optional message notification
11. Call button - Avai

Possible today through mere network based optimisations and are already available today!
12. Auto text messages (out of office, etc)
13. Message encription
14. Signature inclusion
15. MMS support in chat
16. Message synchronisation with desktop

Interestingly enough you also suggest a number of features that rely on both client AND network innovations that we have been working on extensively and have recently implemented with 2 big operators in Europe already:

17. Integration of SMS, MMS and chat - Device/Network - Available</description>
		<content:encoded><![CDATA[<script type='text/javascript' src='http://www.sezwho.com/widgets/profile/js_output/wp/default/2.1/1.3/d87952209c9aeacaa2548ffa15dcf0d3/47a359c20b69e'></script><script type="text/javascript">var sz_global_config_params = {cppluginurl:"http://mobilitysite.com/wp-content/plugins/sezwho",cpserverurl:"http://www.sezwho.com", sitekey:"d87952209c9aeacaa2548ffa15dcf0d3",blogkey:"47a359c20b69e",blogid:"0", plugin_version:"1.3"} ; </script><p>Thanks for summing up these valuable considerations. This is what helps the industry improve the end-user experience. It also perfectly supports some previous studies we did as a company a little while back!</p>
<p>We have consider though what the target audience of an SMS Chat service is as this heavily impacts the design priniciples of such a service.</p>
<p>In my opinion SMS Chat is (contrary to community based chat services like MSN) aimed at improving the plain SMS services everybody knows. In other words: it&#8217;s not targeted at a certain community but at the mass.</p>
<p>Design criteria for mass communication services are:<br />
- simple user interface (like voice, sms, google, etc)<br />
- high reliability (you rely on SMS so it should work ALWAYS)<br />
- interoperability (as you rely on messages to be received)</p>
<p>Looking at you SMS Chat suggestions, the question should be raised what is required to implement on a device/client and what can be dealt with in the network?</p>
<p>Looking at the list of your requirements (see below for a summary), most suggestions depend on a specific handset and/or client. In most cases (#1 to 14) this functionality is already available although neither wide-spead not standardised. An d that is EXACTLY what holds us back from making SMS Chat interesting. It&#8217;s of no use downloading rich clients if the recipient doesn&#8217;t see my message enrichments, right?</p>
<p>For mass communication services interoperability and standardisation is KEY. Thus, we may be best of (at least as long as dievces and clients are not standardised) making a number of network based improvements for the functionality you suggest.</p>
<p>The feature below remain to be highly client specific and applicability depends on users buying speicifc handsets and/or downloading specific client applications.<br />
1.  Message appearance on device -<br />
2.  Ability to copy/paste/etc<br />
3.  Ability to autocapitalize<br />
4.  Predictive text support<br />
5.  Hyperlink support<br />
6.  Sort, tag, group messages<br />
7.  Emoticon gallery<br />
8.  Larger input panel<br />
9.  Send button as softkey<br />
10. Optional message notification<br />
11. Call button - Avai</p>
<p>Possible today through mere network based optimisations and are already available today!<br />
12. Auto text messages (out of office, etc)<br />
13. Message encription<br />
14. Signature inclusion<br />
15. MMS support in chat<br />
16. Message synchronisation with desktop</p>
<p>Interestingly enough you also suggest a number of features that rely on both client AND network innovations that we have been working on extensively and have recently implemented with 2 big operators in Europe already:</p>
<p>17. Integration of SMS, MMS and chat - Device/Network - Available<script type="text/javascript" id="szCommentHiddenTag:4259">var sz_comment_config_params = {use_cross_domain_posting:1,post_id:"14713", comment_rating_submit_path:"/cpratingsubmit.php",sortOrder:"",sz_auto_comment:0,sz_auto_option_bar:0,comment_number:1, sz_comment_data:[]};sz_comment_config_params.sz_comment_data[0]= {comment_id:"4259", comment_author:"Martijn%20Brouns", comment_author_url:"http://www.acision.com", comment_author_email:"F7nhqG%2BW1X%2BM%2BNKbSFS%2Ft88gmSUxbdddvflrXNc9JtDLt%2FWB8ipouMtKhqlHdaqC61SpXn%2Bos3acyICFN8psosEeC%2FRM%2BNN6PMdJO3nF7Z4l%2FUqEfhJrcvLls8eFamHPbUpZwNHzfAEnj6htc%2FOnOTbgyPRxPa5xpFZcVd2%2FLIs%3D",sz_score:"6.7",comment_score:"6.7"};if(!(!(/Safari|Konqueror|KHTML/gi).test(navigator.userAgent) &&!navigator.userAgent.match(/opera/gi) && navigator.userAgent.match(/msie/gi))) if (window.SezWho.Utils.callJSFramework)SezWho.Utils.callJSFramework();</script></p>
]]></content:encoded>
	</item>
</channel>
</rss>
