3 ms·
You can "fake" mobile support using Twilio. It will not have an experience as good as a native smartphone application, but the cost is lower by (plural) orders
by patio11 16y ago
You can "fake" mobile support using Twilio. It will not have an experience as good as a native smartphone application, but the cost is lower by (plural) orders of magnitude, and the reach is far greater.
I'm writing Appointment Reminder, which features a scheduling interface (in a web app). I have heard from customers that it would be really, really handy if they could access their schedules while away from a computer. One of them specifically asked for a Blackberry app.
I could write a Blackberry app. And an iPhone app. And twelve Android apps. And... no, wait, this is insane. I have enough on my plate just getting the underlying service and web interface to work.
Instead, I am writing something responsive to the underlying need ("I need to check my schedule when not at a computer") with Twilio. Call the number you programmed into your phone, hit 1, bam, here is your schedule for today. That gives me 100% coverage on all handsets, including feature phones, for approximately an afternoon of work.
Now, if that feature blows the doors off, it might be worth surveying my customers about what phone they have and implementing e.g. an iPhone, BlackBerry, etc app as resources permit. If nobody uses the feature at all, or if I can't get the marketing for Appointment Reminder to the point where I have any customers to worry about not having an iPhone app, then I didn't spend several tens of thousands of dollars in vain to learn that.
- ryanhuff 16y agoIs a twilio "app" better than an iphone app shell that runs a slimmed down version of your web app?
- jraines 16y agoAccidental downvote . . . I agree that this seems more practical and almost as easy.
- patio11 16y agoIf that works for your purposes, wonderful. For my purposes, it sounds like "Teach yourself ObjectiveC so that you can write a version of the site you have to maintain in parallel, for the benefit of iPhone owning customers who may not exist."
- jfeldstein2 16y agoI think he means something like, "Why not build a simple webapp that prints out a users schedule, that they can view on any phone, and can save as an icon if their phone supports that (iphone)" It solves the problem you're trying to solve, requires minimal effort and is cross platform.
- nostrademons 16y agoIf your app is basically a webapp that you want to be accessible from mobile devices, you're best off with a mobile stylesheet for the web app. It can be a timesink, but definitely less of one than the multiple FTEs you need to support native mobile apps. To me, though, the really interesting stuff in mobile are the markets that simply aren't possible for desktop webapps. Things like Shazaam or Bump, and probably lots of other things that haven't been discovered yet. These things simply can't be done as webapps, because you don't have the hardware support necessary to access those features. It's like how when the web came out, everyone used it as a glorified storefront, with e-commerce everything, because that's what they were familiar with. It was only once it'd been out for ten years or so that we realized it replaced the socializing part of going to the mall and not the shopping part. It seems totally obvious today that people would use the web to talk to each other, but it wasn't so obvious in 1995.