Note that if there is a lot of text traffic on a given number, carriers like AT&T, Verizon, et al will block texts to and from that number until the traffic subsides. What's worse is that if you send a message to that number from the Twilio dashboard, its status will be "sent," but you will not actually receive it. Apparently in the world of SMS, "sent" simply means the message has been delivered to the destination carrier, and it is not a delivery receipt like with iMessage or BBM.
Twilio suggests that, to reduce this risk, you load balance across a collection of such numbers, or purchase a short code, which isn't cheap: http://www.twilio.com/sms/shortcodes
DOTGO solves the problem of service discoverability by mapping domain names to shortcodes representing TLDs. Want wikipedia.org? Text "wikipedia" to DOTORG (368674). Want to checkin to Foursquare? Text "foursquare" to DOTCOM (368266).
DOTGO also provides a language of reusable components, known as CMRL (Concise Message Routing Language), it allows you to create hierarchical menus, links and URL callbacks.
They're available in the United States and select countries in Latin America, Africa and Asia.
Previously, I was a web application developer for them, I still think it's a great idea and recommend you guys give it a go.
I actually spent some time looking into dumb phones a couple years ago. My favorite would be the motofone. It's got an e-ink display, which is great for battery and sunlight, and 2 antennas which is also great if you heaven forbid make actual calls with it. Also, pretty sturdy, small, and light.
I had a Motofone (also called F3) for the last 7 years. It started with a two week working battery life. It's a pain to text message on since it only shows 4 or 5 characters on, but it just worked as a reliable phone. Finally switched to an iPhone 5 after it became vital for me to have full Internet access 24/7 for work. If it weren't for that, I'd still have my F3. I love it as much as I love my iPhone 5.
You can still find some of them on eBay. I'd offer mine, but I'm keeping it as an emergency (911) phone for my car.
F3 to iPhone 5 has to be the biggest jump I've heard of lately. I've been meaning to pick up a dumbphone myself, maybe I'll grab an F3 - I remember when they came out, I was dying for one. It's a bit like buying the... junker of your childhood dreams.
I used this phone for about 6 months. The screen made it hard to navigate the menus and got in the way of even simple things like adding someone to your address book. The battery life was good but it was not significantly longer than the battery life of other dumb phones (since the screen is mostly off it doesn't make a huge difference).
Eventually I traded it in for a cheap nokia with an lcd.
I've been using the Motofone for three years now and I love it. The texting doesn't bother me either. It's also the lowest common denominator of phones that call and text, so we test all our dumb apps against it.
Googling for "card phone" doesn't actually bring up a lot of card phones. I see more prepaid cell phone cards and banks with mobile apps. The first card phone for sale isn't until page 2, and it's an eBay link.
I believe Nokia Asha line of phones is leading the charge in dumb phones in developing countries, Nokia Asha 501 being the newest. It has pretty freaking awesome (especially in countries where access to electricity is a luxury) 48 day standby time (beat that iPhone!). In addition, Asha 501 actually has some kind of support for 3rd party apps.
And if you want physical keypad instead of touchscreen, then the 301 is probably the best featurephone available. Similar crazy long battery life, good looking design, and all the features you'd need (aside flashlight). 301 also has 3G connectivity, so I believe it has better reception than pure 2G models such as 501.
I have a Nokia 1202 that I keep in my emergency drawer, that I take with me hiking and so on. It's very reminiscent of the 3315 in build quality. It talks, it txts, it has snake. What more do you need!
I actively use a Nokia 100 (as my "family calling" phone - calling and minimal texting -only-). A brand new one cost £18.99, it has a monster battery life, is super light and yet an absolute rock in build quality.
I'm sure it has some additional bling like FM radio, a media player or whatever and some games, but I use literally use that phone for nothing other than calling and texting.
I lived for the last 2 years with a Nokia 1610. Highly recommend but they discontinued in January and a new model came out with a camera (which was against my minimalist ethos at the time).
I ended up breaking the chain and switching back to an iPhone 5 but this app store has got me pining for the simpler days of pure sms and voice based comms.
Seems extremely similar to what Intuit has been building in India: Txtweb[1]. The apps support two modes PUSH and PULL. The most common is PULL, where you SMS to some number something like "@appname.optionalExtension <stuff that will be passed on to the application logic", response comes back as SMS. Their experimental PUSH automatically pushes subscribed users with SMSes. I had developed an app, @news a couple of years ago and still see decent traffic on it. The developers are also quite friendly and responsive. If you are interested in a similar platform but in a market that is benefitted from this application a lot more, you should definitely check them out.
I've thought about how you could probably get Siri to use SMS as an API to tons of services, like opentable, fandango, etc, etc - this seems to be a great step in that direction - which is actually the opposite of dumb, but instead seems uber smart.
I like the idea, it might be a nice replacement in the wake of the Google SMS shutdown. One quick thing: You might want to make app names case insensitive. My phone automatically capitalized Ltrain, resulting in a message stating the app was not found, however when I manually changed it to ltrain it worked. Maybe simple spelling correcting for app names (e.g. off by a letter or a letter is missing) could be added too?
Don't like the interface (makes it seem 100x more complicated than it is) but love the idea. I often hit my data cap, am in an area with slow or no data coverage or don't want to load up an app and would be happy to shoot a text off to get a piece of info.
I'm in the UK but this is a far bigger problem in other countries so if executed better this would be very interesting.
Neat idea. I might recommend allowing at least the first letter (of the app) to be case-insensitive though, since lots of things auto-capitalize. Also I'm not having much luck with 'dir', and some error messages or something would help, but meh - the concept is great!
This is really awesome. Back when I was helping work on Pingie (an rss->sms service), I put some of this functionality into it (weather reports, stock quotes, traffic reports).
Note that if there is a lot of text traffic on a given number, carriers like AT&T, Verizon, et al will block texts to and from that number until the traffic subsides. What's worse is that if you send a message to that number from the Twilio dashboard, its status will be "sent," but you will not actually receive it. Apparently in the world of SMS, "sent" simply means the message has been delivered to the destination carrier, and it is not a delivery receipt like with iMessage or BBM.
Twilio suggests that, to reduce this risk, you load balance across a collection of such numbers, or purchase a short code, which isn't cheap: http://www.twilio.com/sms/shortcodes