Developing custom apps for tablets and smartphones has become the cool thing to do. Just make sure you aren’t opening a can of budget-busting worms long term.
As tablets and smartphones become everyday business tools, smart IT leaders are moving from just accepting them to devising ways to fully support mobile business applications. For many IT organizations, that means jumping into the deep end of the pool by creating custom apps for both internal and external users. After all, if there’s more than half a million apps on Apple’s App Store, then most IT organizations should be up to the task of creating their own, right?
Maybe. But just because you can do something doesn’t mean you should. The bar for developing custom apps for smartphones and tablets should be high, at least as high as it was for creating them on PCs. Here’s a good rule of thumb: Web when you can; custom apps when you must.
Unfortunately, none of the OS vendors is particularly interested in the success of WORA tools, so they’ll make changes that will force both your chosen tool developer and your organization to make an update on the new platform. When Apple introduced iOS 5, it took months for even the commercial developer community to update all their apps. It’s not as if the old apps broke–though some may have– but if you’re in for an ounce, you’re in for a pound. Users will expect your app to work like all the rest. Apps on Apple devices can be a challenge, but Android significantly ups that challenge, as those releases are more regular and there’s less guidance from Google on how the UI should look and feel.
The more frequent OS updates and differences in implementation from manufacturer to manufacturer have given WORA tools a less-than-stellar reputation. They’re often dubbed “write once, debug everywhere.” Whether or not they deserve that reputation, and whether or not they’ll grow out of it, anyone looking to roll their own applications had better take the task seriously.
The short-term investment in creating those first pristine apps is likely to be the tip of the iceberg in terms of people and capital costs. Whether you’re using internal teams for development or contracting with coding houses (a practice that brings its own set of challenges), you’ll need to make a sober assessment of the short- and long-term costs of supporting the practice. Much in the same way that homeowners are shocked at the true cost and time to complete a home remodeling project, so it can be with software development. Estimates are made based on perfect conditions and often on an incomplete assessment of the business’ lifetime needs for those apps.
Sometimes, the basic nature of the app you envision will require that it access resources that only a custom application can get at. If you need the app to access the device’s accelerometer or near-field communications system, you’ll probably need to write a custom app. As these features become standard in phones, you’ll eventually be able to use them from Web applications. A bigger challenge comes around notifications. It’s reasonable to envision pushing notifications to devices based on all sorts of things (inventory levels, orders shipping, hundreds of others). Web-based apps typically rely on email notification.