<div dir="ltr">Hi,<br><br>I'm interested in suggestions/comments/etc with regards to SMS-based applications. What I mean by this, is an application which uses SMS instead of data (GPRS/wifi) to work.<br><br>Examples could include:<br>
AOL AIM client using shortcode support<br>Google SMS query support through a more convenient interface<br>(In my specific case) San Francisco MUNI NextBus.com support, which allows you to lookup when a bus is coming via SMS, or schedule an alert for when a bus is Xmin away.<br>
<br>Odds are, this concept could be heavily expanded upon (twitter?), and it offers the following advantages over data:<br> - More reliable. Data can run into a lot more problems than SMS. Plus, there is no general "loss", even if you lose signal, the SMS comes in once you get it back<br>
- Less power. As the data is truly an "on demand" "connection", you don't need to maintain an active connection.<br> - No data costs for those who live in places with expensive data<br><br>Conversely, there are some disadvantages:<br>
- Higher latency<br> - Lack of features active connections offer (eg, AIM's "buddy is typing", etc)<br><br>I am aware of a Google Summer of Code project, <a href="http://code.google.com/p/sms-middleware/">http://code.google.com/p/sms-middleware/</a> , but its documentation is predictably minimal, and it is unclear if the base will be compatible with this.<br>
<br>Furthermore, it would seem that any code that is written be portable and not tied to a specific image. However I keep hearing FSO is the future, but a quick look at its API seems devoid of any mention of SMS.<br><br>
Anyway, I am a relatively novice programmer, and I'm soliciting comments, ideas, criticisms, etc. If someone has a specific interest in assisting me, or handling such a project themselves, let me know.<br><br>Jeffrey Malone<br>
</div>