Gartner Blog Network


Should Governments Develop iPhone Apps?

by Andrea Di Maio  |  July 14, 2010  |  12 Comments

I was following an interesting debate on Twitter about a recent BBC article pointing out that the UK government would have spent too much money developing iPhone applications, when it occurred to me that a client I talked to recently mentioned the development of an iPhone app. This was outside the UK and concerned the ability for citizens to take a picture of a pothole or some other problem, send it to the Department of Public Works and be able to track when the problem would be fixed.

I remember that I discussed different aspects with the client, including whether there could be any issue with not supporting other smartphones (such as Android or Windows based) and what the impact on both citizen expectations and internal processes would be. On the former he did not seem to be particularly concerned, as people already have the ability today to report a problem through the web, and any mobile browser would do. On the latter, though, he seemed considerably more concerned, especially with the quantity and quality of information they would receive. What if people start submitting all sort of pictures, including those that do not concern any problem? What if this is so successful that they are overwhelmed with reports? And what if a reported problem is not fixed quickly enough and a constituent just calls his elected council member to complain?

All this makes me reflect that for how cool iPhone apps can be, it is difficult to articulate their actual value for government. It seems to me that governments risk losing both ways. If the app were not successful, people would criticize government for wasting money. If it were, but processes and technology were not in place to smoothly manage its impact, people would criticize government for not being responsive and for wasting money.

So what should governments do? Well, just step back and think that iPhone is a consumer choice. So why shouldn’t those same consumers who are eager to use the iPhone get an application developed and be made responsible to develop the processes that are required to allow government to use it at no extra cost? If I take the pothole example, why shouldn’t a citizen community be responsible for commenting upon and rating the problems reported by iPhone app users, so that government can access to information that has been partially vetted and assured by the community?

We can’t ask to have a government that is lean, cheap, innovative and citizen-oriented government all at the same time. If we want the thrills and frills of new consumer technology we have to engage and help government make the best use of it, at an affordable cost and risk.

The BBC article is probably right: just developing iPhone apps is hard to justify. But those who criticize the article are also right in pointing out that government cannot stand still on this. So why not taking the AppsForDemocracy idea to the next level? Let’s have communities both develop application and help manage their impact: I believe it is a fair trade.

The answer to the question in the title might be: No, governments should not develop iPhone apps, the community should.

Category: web-20-in-government  

Tags: crowdsourcing  government-20  

Andrea Di Maio
Managing VP
15 years at Gartner
28 years IT industry

Andrea Di Maio is a managing vice president for public sector in Gartner Research, covering government and education. His personal research focus is on digital government strategies strategies, Web 2.0, open government, cloud computing, the business value of IT, smart cities, and the impact of technology on the future of government Read Full Bio


Thoughts on Should Governments Develop iPhone Apps?


  1. Davied says:

    Isn’t this discussion the same as fifteen years ago when the first internet sites appeared? Also criticized because it was an extra channel with (then) very little users. Also doing it wrong a lot of times and spending too much money.

    The difference is that there were no online communities or app stores around in those days. In the Netherlands there are by now three pothole sites or applications around, all made by small companies.

    But I wonder if that’s the future of government services: just letting small companies make tiny apps that are hardly connected to other services or platforms. How can we use the innovations from coders and companies without the usability problem for users trying to help their government bodies?

    I would be interested in your opinion about that. We getting beyond the phase of just saying ‘the community will solve it’. Government 2.0 is not the same is no government, it’s a different division of tasks between government and society. Where is the new dividing line?

  2. […] This post was mentioned on Twitter by Pascal POTY, Emile HOOGE, Raymond Lunes and others. Raymond Lunes said: No indeed, the community should w #opendata RT @AndreaDiMaio Should Governments Develop iPhone Apps? http://bit.ly/b8T7K0 #odnl […]

  3. […] Read the original post: Should Governments Develop iPhone Apps? […]

  4. […] See the article here: Should Governments Develop iPhone Apps? […]

  5. @Davied – You make a very good point. My observation is that choosing one particular consumer platform or device inevitably exposes government to criticism. Whereas creating a web site opens a channel to anybody who wants to use it through a device of choice, developing or subsidizing the development of an application for a particular device (and – in this case – one that is hardly “open”) is a more questionable use of taxpayer money.
    However my concern is not really about iPhone or Android. My concern is that this whole idea of engagement need to make government more effective and less expensive: therefore the “community” must be engaged in the most appropriate ways for this to happen.

  6. […] Should Governments Develop iPhone Apps? […]

  7. […] Should Governments Develop iPhone Apps? – "No, governments should not develop iPhone apps, the community should." […]

  8. When you use apps make notes of what really caught your eye and what didn’t catch your eye. The best way to develop a quality iPhone app and discover a need is to think like the customer! By doing this, you give yourself an insight into what the iPhone app consumers really enjoy and don’t enjoy! Sometimes by discovering a need that customers do not want, can help you just as much as discovering a need that customers do want.

  9. […] Should Governments Develop iPhone Apps? […]

  10. […] exception of tax returns, though the history and issues are a bit different there). Andrea di Maio comes close to making that argument: So what should governments do? Well, just step back and think that iPhone is a consumer choice. So […]

  11. […] Inspired by Matthew Somerville’s use of iUI to fake an iPhone look and feel to his Train Times application, I’ve put together a little demo of how the FCO’s new feeds might be repurposed, with a little app optimised for iPhones which takes the latest alerts, visualises them on a map, and enables you to get the phone number and opening times for an embassy if you need it. It’s a fairly silly little proof of concept, but hopefully it shows that RSS feeds don’t just have to live in newsreaders. And it’s what Andrea DiMaio has decreed. […]

  12. […] hacken vi sett bygger ju på just RSS-hackande.BTW, tack vare den här texten hittade jag också https://blogs.gartner.com/andrea_dimaio/2010/07/14/should-governments-develop-iphone-apps/ Mycket […]



Comments are closed

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.