Sometimes in the public sector, we end up with a solution looking for a problem. Mobile apps, native or web, often fit that definition. Since this is a quandary that often comes up, we’re hoping to draft some guidelines later this year. But in the meantime, here are some ideas to get you thinking about the possibilities and pitfalls.
To app or not to app, that is the question
Our advice is to take a step back from an app as a solution and ask yourself:
- What are you trying to do?
- Do your users need an app?
- Will you build a native app or a web app?
- How do you measure success?
- Who will take care of your app after it launches?
We strongly recommend that you look at user research — ideally your own — to gauge whether people will be interested in an app.
Options to consider:
- leverage the Govt.nz customer experience research that we have undertaken, which we’ve published here on the Web Toolkit
- adopt responsive design to enable the public to access the public facing content on your site, which may reduce the need to develop a mobile app (some responsive design advice is also published on the Web Toolkit blog).
Some resources to help you find the answers you need
- Digital by Default News [UK]: Building an App - 3 Key Considerations
- Standalone mobile apps: the UK Government's position on mobile apps
- Takeaways from Mobile Accessibility 101
- Australian Public Service Mobile Roadmap
- Mobile App vs. Responsive Design: Ask These 10 Questions First
- Designing for mobile: Responsive design vs. mobilized sites vs. mobile app
- They Need an App
- Responsive web design vs. mobile app development
- Should you build a mobile app or mobile website — infographic
- Mobile apps: the new security breach
- Making Mobile Gov Project