Almost one year ago, we deployed a custom application for a critical department. Here on the eve of the next iPhone, I am reflecting where we are with the app.
This application required almost 4 GB of local data for offline use in an indexed database. That requirement forced us to use Windows Mobile 6.5 and SQL Compact. Since the app started development prior to Microsoft announcing Windows Phone 7, we thought we would have devices available for a couple of years. One year from the deployment, we are down to one device that costs $600 each, and won't even run the app without errors at this point.
In the meantime, the consumer-grade devices of one year ago are failing and needing replacement. And a small but vocal group are clamoring for an iPhone. I can't say I blame them. We can give them an app that has the offline data, and hopefully get it working on a business device from Motorola. But it runs on a phone they can't do much else with, and frankly have a hard time navigating because Windows Mobile was written more for IT staff than general users. Or we could give them an iPhone and open their day to exponentially more uses, such as mapping and voice dictation. All this at one-third the price.
For now we are trying to get the Motorola to work, and to give them the offline data they often need. We'll see what the iPhone announcement brings tomorrow, and if the requests from our users change any as well.
