The use of mobile apps is not a replacement for building a mobile responsive website. Before considering building a stand-alone app for a service, you should ensure that the core web service works well on all mobile devices.
There are some instances when a native mobile app would be of value to the user. Examples of these include, but are not limited to:
- Where digital information is essential without an internet connection. A good example of this is the NICE Guidance app.
- Where there is a need or a user demand for continued engagement with the mobile app - regularly using it or updating data. A good example of this is Public Health England’s Couch to 5k mobile app.
- Where there is a need for the service to be able to integrate with other features and apps on the mobile device. A good example of this is an app which integrates with another stand-alone navigation app.
- Where there are specific data storage requirements that cannot be achieved using a web-based service. A good example of this is an app which is storing confidential / sensitive clinical data about a user.
Cabinet Office policy on mobile apps
- Provided by: GDS
- Applies to: all new or existing mobile apps created by central government and ALBs
Stand-alone apps will only be considered for approval once a core web service works well on all mobile devices. If you think there is a good case for the inclusion of a mobile app as part of your digital project, you should speak with the DH Digital Team and provide clear evidence of the user need that can only be fulfilled with this solution.
Approval is also required for any spending on existing mobile apps, including upgrades or redesign, also including apps developed by partner organisations. Your spend request should be accompanied by convincing evidence to support the continuation of the existing mobile app.