We’re not ‘appy. Not ‘appy at all.

The British Government Digital Service (a new team within Cabinet Office, which in its turn supports the Prime Minister and Deputy Prime Minister) is totally getting it:

Stand-alone mobile apps will only be considered once the core web service works well on mobile devices, and if specifically agreed with the Cabinet Office.

Above that:

Apps may be transforming gaming and social media, but for utility public services, the ‘making your website adapt really effectively to a range of devices’ approach is currently the better strategy. It allows you to iterate your services much more quickly, minimises any market impact and is far cheaper to support.

With that, they’re pushing anyone within the central government to, let me quote:

make your data and/or API available for re-use and you will stimulate the market if there is demand for native apps

Highly recommended read. Also contains a solid presentation (embedded above) and some figures of website performance after having given some a (responsive) overhaul. Spoiler: performance increased.

We’re not ‘appy. Not ‘appy at all. →

The British Government surprised me before, with their list of Design Principles. Also highly recommended.

Published by Bramus!

Bramus is a frontend web developer from Belgium, working as a Chrome Developer Relations Engineer at Google. From the moment he discovered view-source at the age of 14 (way back in 1997), he fell in love with the web and has been tinkering with it ever since (more …)

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.