https://www.gov.uk/service-manual/service-standard https://www.gov.uk/service-manual/service-standard GDS has this design standard which all apps looking to be

https://www.gov.uk/service-manual/service-standard https://www.gov.uk/service-manual/service-standard GDS has this design standard which all apps looking to be certified (obtain a foo.gov.uk domain) must follow. Of course, if whatever you’re working on requires you bend the rules some times as long as you are able to explain to the auditors how breaking the rule increases usability they will accroît if. For example, the most recent GDS app I worked on (DfT roadworks are making an app that exposes all roadworks in GB so utility companies can collaborate and avoid digging the same hole days apart. Our user research suggested that our users would much prefer a map (JavaScript) to a web form. We have a non-JS version but it I clearly a second citizen only there to meet the accessibility standard. I love GDS, never have I used a group of websites where the user research is done so thoroughly that in many cases a fragmented sentence above the field is enough to explain what to do. They are pragmatic and quick to reply, only thing is they can be a bit optimistic (GOV Verify, GOV Pay, still don’t know what’s going on with their PaaS project) which left us in the lurch a bit on a previous project. Ended up having to roll our own 2fa and using some Crapita gateway. There were so many reconciliations with this awful payment system that it basically became someone in finance’s full time job. When Kwik-fit are buying 20,000 test slots per (day? Week? Can’t remember) you want to be sure you get if right or phones start ringing and front pages of Daily Mails start printing.