But uptake has slowed.
Building the app is only half the challenge -- now you have to run it
Developing your own apps isn’t easy.
Well, that’s not quite true. Writing the code can be easy, but the real challenge comes when you actually have to operate the services you’ve built, and support your users. And if your app is a departmental app you’ve built yourself? That means you're now your own operations team. You’re going to have to plan how you’re going to run your services, and how you’re going to communicate with users.
Running a service is a long way from writing the code. You’re going to need to be on top of the services and APIs you’re using in your app, and keeping an eye on the networks and platforms that are running your code. You don’t need to have the same SLAs as a commercial app, or one that’s come from your IT department, and you don’t have to provide out-of-hours support – but your users are going to expect to be able to use the app when they want to, as it’s there to help get their jobs done.
So what can you do? If you’re using a platform like Azure to build your apps, many of the operational tools you’re looking for are built in. The same goes for the upcoming 2013 release of Visual Studio, which lets you debug code running on remote browsers. But you have no control over a lot of the things you'll be using in your apps. So that neat location service you’re using to help a field service engineer get to a customer -- you know that it says it’s accurate to 20 feet or so, but do you know how accurate it really is?
That’s a big problem facing any developer building a quick app for a few people. You may well trust a service enough to put it at the heart of your code, but if it’s a consumer-grade service you’re not going to have a service agreement to call on, and the user agreement you signed up to is unlikely to be any help when your users start complaining.
Part of the solution is educating your users, letting them know that they’re using apps that have been built with consumer-grade tools and that there’s no service level agreement. But that brings in another problem, as many consumer services are rock solid.
When did you last see Facebook go down, or Google Maps have a major outage? Users will expect the same level of service from your apps, even if the free API you’re using only has a limited number of calls an hour.
Working with an API brokerage can help, as it lets you see how many calls you’re using, and when you’re close to a limit. You could build those features into your own services, but you’re building apps to help your colleagues, not to spend your time operating a service – especially as you’ve still got your own job to do. Being able to log onto a portal simplifies the task of managing your services by letting you see key information at a glance.
Viafo's new service helps you keep tabs
The team behind the Viafo API brokerage are currently trialing a new service, aimed at giving both developers and API owners a view of how their APIs are performing. It’s a useful service, and one that means that you’re able to understand just why your users weren’t able to use your app a week ago, and why they’re only getting a 75% success rate with certain calls.
Google's plan to bring Chrome packaged apps to Android and iOS is part of its strategy to make the web the primary platform for users. Converting Apple device owners will be a challenge.
Most companies understand that they need a social media presence, but many are flying by the seat of their pants instead of crafting a social media plan that aligns closely with business goals.