I'm sure that developing a Twitter-to-SMS would be a fairly straightforward
exercise, given their API and the fact they currently support it in other
countries.

I am just wondering if this is a retrograde solution.

Anyone who has dealt with telcos will tell you that they love to skim
profits. The artificially high data rates for mobile data (and SMS for that
matter) is a classic case in point. They charge like wounded bulls because
they can - they own the infrastructure and, in the case of SMS, they own the
billing engine.

Given that 3G is fast becoming a standard globally, why would you develop a
solution based on 1G technology - and force yourself into bed with the
profiteering telcos?

Why not look at the other data channel (IP) and use that to create an
SMS-esque application? Create a solution that gives a SMS-like experience -
beeping/vibrating when incoming messages are received, with a reply service
- but which operates independently of a specific carrier?

And, if you're going to go down that path, why not build the app in such a
way that it can be interfaced with other social services?

The pain that has been articulated - wanting to keep an eye on 'social
updates' when away from your primary computer - is real. But it is felt by a
lot more people than just Twitter users.

Regards,

Mark
-----
Mark Neely
Master Strategist
Infolution Pty Ltd

e: m...@infolution.com.au
m: +61 (0)412 0417 29
skype: mark.neely

Read my blogs --> www.infolution.com.au
                            www.neelyready.com
Connect on LinkedIn --> www.linkedin.com/in/markneely