Skip to main content

Will SMS Applications Thrive?

Short Message Service (SMS) text messaging is now standard on mobile phones. (Multimedia Message Service, or MMS, is an enhanced messaging service that adds the ability to attach pictures and sounds to the messages you transmit.) It is widely used. But will it survive in anything resembling its current form?

I am a big fan of Google SMS. I was at Academy buying shoes on a Sunday evening and decided to go to Oshman's in the hope they would have a better selection. Would Oshman's be open on a Sunday evening? How could I obtain their phone number so I could call them? If I used my mobile phone's directory assistance service, it would cost me $1.25. I ended up using Google SMS to determine Oshman's phone number.

I wrote 'oshmans austin texas' in a text message and sent it to 46645 (GOOGL on most phones). Within seconds, I had received a text message back from Google SMS with the address and phone number of Oshman's. Very convenient! Yahoo has a similar service.

I can imagine many useful applications of this sort. There are many situations where we are on the go, need some information, but don't have access to it without calling someone to have them look it up. But I know of only two such services: Google SMS and Yahoo's similar service. And I don't know anyone else who has ever used them. Why haven't SMS applications taken off?

Comments

Brandon said…
I think dodgeball is pretty cool but only a few people are using it. May want to try it: http://austin.dodgeball.com/index.php
Roger L. Cauvin said…
Oh yeah, now I remember you and Cote mentioning Dodgeball about a month ago.
Robert Zamees said…
4INFO (shortcode 44636) has a similar text message offering, but provides a few services that Google does not: sports scores ("packers" "nfl"), fantasy stats ("joe crede" "priest holmes"), flight times ("swa san jose san diego") and a beta version of mobile download search. All these services can be accessed via sms (44636), wap (http://wap.4INFO.net ), or email to search@4INFO.net.

Why 4INFO instead of Google?
“When asked recently for the address of a trendy downtown Manhattan club called Butter, both 4Info and Yahoo! located it on the first try. But Google sent back results better suited to baking.”
- Wendy Widman, Forbes.com. 8/3/2005

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the