A colleague sent me a stack overflow thread today entitled “How much does it cost to develop iPhone applications?” It’s worth taking a look at, most interesting is an answer suggesting around $10,000 ($50/hr for a Developer and $50/hr for a Graphic Designer x 200 total hours), which the stack overflow community quickly jumped on, providing insight and information to back up a more realistic $50k-100k (and some say $200k) price tag.

At Mosio, naturally we get asked about mobile applications from clients all the time. I love my MacBook Pro, iPhone and iPad, but Apple has spent plenty of money in advertising to convince us all that “There’s an App for That.” They even spent money trademarking the phrase and that’s fine, they benefit by doing so. The craziest thing about the mobile apps hype is that it caters to less than 1/3 of the mobile subscriber market. Consider recent research about Mobile Content Usage for the month of July 2010 in the image above from Wireless Week:

Among all U.S. mobile subscribers ages 13+:
31.4% Used a Downloaded App
33.6% Used a [Mobile] Browser
66% Sent a text message to another phone

Why, then, do people think it’s so inexpensive to develop iPhone apps?
I’m not exactly sure, but my guess is that it’s a combination of people wanting to believe it costs less combined with the misinformation from people selling shoddy development services or app workarounds trying to capitalize on the hype. And before those of you developing “affordable” iPhone applications start flaming me in the comments, consider the fact that by saying it’s inexpensive and cheap, you’re essentially selling yourselves short, commoditizing your expertise. The misinformation hurts your skills and service.

The world is mobile and we want to provide a mobile experience beyond text messaging. What should we do?

If you are a library and looking for a great way to mobilize your website or catalog, we recommend you visit our friends at Boopsie. They have a great team and wonderful experience in helping libraries on an existing platform that makes the process simple.

My wife loves to read magazines and books every night after work. I love to read articles on my iPhone. The problem is that when you’re reading a magazine or a book, it’s obvious what you’re doing. When I’m “reading” my iPhone, in her eyes, I’m working. Yes, some of them are articles, news and blog posts about work, but many other times they are not. I can’t think of too many other reasons currently why I’d like an iPad, which is being announced by Apple tomorrow.

Note: I have $.50 riding on the fact that it’s called an iPad and plan on using my winnings to pay for half of a bus ride on MUNI.

There has been a lot of talk around the office about what this and other e-readers will do for the publishing industry and we’ve signed up to get our Kindle Devloper’s Kit, but based on some of the recent news and talks that happened at ALA Midwinter recently, it got me thinking again about libraries and how e-readers and specifically the iPad will change or not change libraries.

Here’s what I’ve determined: Outside of the discussions going on about mobile technologies in libraries, I don’t think it will change it too much. The iPad will offer some great new graphic interfaces where buttons will be bigger, browsing experiences will be more tactile (as the iPhone and other mobile phones do), but e-readers and libraries becoming more mobile-friendly will play into the fact that an iPad will just be a bigger version of the iPhone. Obviously at this point I haven’t seen one, so I’ll update if I’m wrong, but I can’t help myself in thinking people will be holding up the iPad to their ears as a silly joke, looking like they’re talking on an iPhone.

So we’re back to mobile. Do I think libraries should start spending money and resources to develop iPad Apps? Absolutely not. In fact, we don’t think libraries should spend money and resources on iPhone Apps. If you need some great reasons, Michelle Kraft (AKA the Krafty Librarian) just wrote a great piece called “Stop the App Madness” and Jason Griffey’s proclamation of 2010 being the Death of the App is actually something we’ve talked about a lot over here. And while it’s great to see these things talked about in the library community, we’ve noticed that Google is betting on the mobile web, plus some research stating that the cloud will replace mobile apps (and their stores) in the next five years.

All of this said, I’m looking forward to seeing how the iPad and e-readers “change” libraries, but only time will tell. In the meantime, I’m really looking forward to seeing what it looks like and ultimately what it does, other than to let my wife know I’m reading and not answering work emails.

Why can’t we just use a phone to handle SMS reference services?

We get that question a lot. It is a great question seeing as mobile phones provide the “truest” form of SMS communications – similar to listening to a vinyl album on a record player.

Our answer usually goes something like this: You can…BUT… given the emerging library technologies available to manage text message reference, mobile phones are very inefficient by comparison.

As we have highlighted before, text messaging is now the preferred method of communication for Americans on the go. Libraries have the opportunity to connect with patrons anywhere (and vice versa) with SMS. The features and functionality of services that are built to manage text messaging without a phone are making the entire SMS reference experience better from librarian to patron, and including administration.

Here are some of the points we reference when answering this FAQ…

* Texting vs. Typing
Texting is not and will never be faster than typing. Mobile data speeds will never be faster than internet speeds. Phone processors will never be faster than computer processors. As an efficiency tool, the mobile phone will never match a computer. Even if you personally send and receive twice as many text messages per day than the average American teenager, it doesn’t mean your associates do.

* Single-user access.
1 phone = 1 librarian, answering 1 question at a time. Receiving and responding to SMS patron inquiries using a mobile phone eliminates any possibility of efficient collaboration.

* Reporting is nearly impossible.
We say “nearly impossible” because mobile carriers will send a bill every month and users can see how many messages were sent and received, time/date/etc, but all data must then be entered somewhere else manually. The other option is maintain an ongoing call log, which is also manual and sounds as fun as filling out a time-sheet to prove you’ve been at work from 8-5 all week.

* Text message transcripts via mobile phones are non-existent.
We don’t know of any phones that allow a user to download text message conversation transcripts. They can be manually typed out, or some phones allow forwarding individual text messages to an email, but not entire conversations, so it would be necessary to send multiple messages to an email account, piece them together into a conversation, then upload them to a database. If this is not done, then there is no archive or living database of the types of questions received and answers given.

* Patron history is extremely limited.
Referencing past patron questions on a phone is not an option as a phone’s SMS inbox gets full. If old texts are not deleted, new texts will not be received. Once again, entering transcripts manually is the only solution.

* Phones are not collaboration-friendly.
Some people are better suited at answering certain questions than others. If those people are standing right next to you, you’re in luck. If not, the process you have to go through to get them to help you assist a patron is, at best, an inefficient challenge involving several pieces of technology. The only exception to this is if you literally throw the phone to that person, which can be done, but brings up the next point.

* Mobile phones break, get lost, stolen, need charging and become obsolete.
If you think this is a weak point then please feel free to move ahead to the next one. That said, there’s a strong likelihood that 1 of the above, if not all, has happened to your phone. Stuff happens, and when it happens to your phone, other stuff needs to happen causing a disruption in the very service you are aiming to provide.

* Patron privacy and security
The fact is that mobile phone number confidentiality plays by a different set of rules than email or IM. As an organization, it is important to determine the limits of your library’s liability by storing patron phone numbers on a handheld device that could get lost, stolen or hacked.

* Phones lack easy answer template options for FAQs.
Imagine having to text your library hours time…and time…and time again. Sure, you can save a draft of a FAQ or access a word doc in your phone, then copy and paste – if your phone allows these functions – but it’s pretty obvious that is not the best use of anyone’s time.

* Technical and customer support is not dedicated, quick or easy.
To some people, calling mobile carrier support gives the same feeling as visiting the DMV. Best to have a good book available. Regardless of what your feelings are about the customer or technical support of your mobile carrier, if something goes wrong, you just want it fixed as quickly as possible. While some carriers are known to have better customer service than others, we’ve never heard anyone talk about it being a quick or pleasant experience. Keep in mind, mobile carriers handle their service only. Technical support for the mobile phone itself is handled by the manufacturer.

* Phones are not scalable.
As the popularity and use of your SMS reference service increases, so do issues related to management, collaboration, reporting and efficiencies as mentioned throughout this post.

* Phones are not that cost-efficient.
We can’t possibly list all of the phones and plans available by mobile carriers, but there are some simple costs of using a phone to consider. Using a reliable mobile phone carrier (getting good reception in the library) with a QWERTY keypad is the first place to start. Basic math on the most stripped down phone & plan = Price of phone + Price of plan(s) + Activation Fee + Taxes + Insurance.

After taking some time to research phone costs, consider the cost of your or your staff’s time: texting rather than typing, transcribing SMS reference conversations, compiling data for statistics and reporting, waiting on hold with carriers or manufacturers if something happens to the phone or service.

If you’re wondering, here’s the cheapest cost for an iPhone on AT&T:
iPhone 3G (old) – $99 or 3Gs (new) – $199
One time activation – $36
Data Plan (required for life of phone) – $30 per month x 12
Voice Plan (min. voice plan required) – $40 per month x 12
Text Message Plan ($5 / $15 / $20) – $15 per month x 12
Taxes – $3 per month x 12
Insurance – $5 per month x 12

TOTAL = $1251 per year x 2 year contact = $2502

[By the way, we LOVE iPhones. We have them and Text a Librarian works great on both the iPhone and iPod Touch. That said, every issue presented above applies to the iPhone.]

In case you are still reading [enter crickets chirping], there’s one more thing to consider: Companies that build services for libraries have a vested interest to make sure their solutions are the best available for librarians. The good ones listen to feedback and not only respond, but anticipate, changes and trends in technology in the library industry.

Thanks for reading.

Ps. We realize that there are some libraries out there that are currently using a mobile phone to handle SMS reference. If it is working for you and your library, great! That said, if you are now looking to implement text message reference, it’s worth weighing all options to determine what will work best for your library and staff.