Good afternoon! I was wondering if anyone might have any pointers to resources detailing, or want to add to my brain-storming of the following:
(1) Best practice in designing an SMS information service eg. "Send WEATHER + your town or city to 1234 to receive daily weather updates: example: WEATHER BOSTON, cost, 1 dollar per message". I imagine that it would be best to avoid sending long messages, too in/frequent messages, using too many codes and numbers and long, complicated instructions, and good to be flexible with date formats. (2) Info on the most common errors Imagine for example if you have to type in a bus service to see if it's on time, possible points of confusion could be whether it's a return or single journey, whether the bus service has a code which may be confused easily, whether there are various legs to the journey, different time-zones, mis-typing and so on. (3) Why, if someone has sent a message and received an error message or no message at all, they would keep on persisting, (it can become very expensive!!). I imagine a high-level of motivation for the service; the typical user self-blame for being clumsy, "I must have typed it wrong", also the assumption that the service may be overloaded in a given moment, or that the text message disappeared into the atmosphere may all play apart as well as poorly written error messages failing to explain why it didn't work. (4) Any examples of similar web based services that have been successfully adapted to SMS. Apart from mobile web design best practices, (many of which are relevant and useful) I haven't come across anything much specifically for SMS, so any suggestions welcome. Kind regards, Elizabeth ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
