When I moved to the UK, one of the surprising things was how well the GOV.UK ecosystem worked. My original country uses a mishmash of Java applets, ajax-based websites, and a mixture of mildly broken, outdated web technologies, served from a variety of domains. GOV.UK was a breath of fresh air with its simple, consistent UI, served as static HTML. This is how internet services should look like.
I moved there from the US (and since then I've moved back). The main surprise was learning that working for the government is relatively high paying and considered a very nice and challenging job that great programmers coveted. At least that was my impression when a very good systems engineer workmate left my company to start working for gov.uk. I do wish there was a similar system in the US as I would find public se…
We’re opening up access to Gov.uk forms
101–110 of 195 posts
Re: We’re opening up access to Gov.uk forms
#102Re: We’re opening up access to Gov.uk forms
#103Re: We’re opening up access to Gov.uk forms
#104Earlier quoted context omitted.
Umm, GOV.UK uses Google Analytics, Fastly CDN, AWS containers, and I believe is developing an app. (I worked at GDS until two years ago.)
Everyone uses Google Analytics. I don't find it particularly high up any list of real worries.
Re: We’re opening up access to Gov.uk forms
#105When I moved to the UK, one of the surprising things was how well the GOV.UK ecosystem worked. My original country uses a mishmash of Java applets, ajax-based websites, and a mixture of mildly broken, outdated web technologies, served from a variety of domains. GOV.UK was a breath of fresh air with its simple, consistent UI, served as static HTML. This is how internet services should look like.
The GOV.uk team loves moving things forward and leaving an awful lot of guff behind.
Re: We’re opening up access to Gov.uk forms
#106Re: We’re opening up access to Gov.uk forms
#107When I moved to the UK, one of the surprising things was how well the GOV.UK ecosystem worked. My original country uses a mishmash of Java applets, ajax-based websites, and a mixture of mildly broken, outdated web technologies, served from a variety of domains. GOV.UK was a breath of fresh air with its simple, consistent UI, served as static HTML. This is how internet services should look like.
If you stay around long enough you'll accumulate a few different log-in id's and find yourself redirected to legacy pages with no way of finding your way back. The GOV.uk team loves moving things forward and leaving an awful lot of guff behind.
Re: We’re opening up access to Gov.uk forms
#108Earlier quoted context omitted.
Umm, GOV.UK uses Google Analytics, Fastly CDN, AWS containers, and I believe is developing an app. (I worked at GDS until two years ago.)
Everyone uses Google Analytics. I don't find it particularly high up any list of real worries.
Re: We’re opening up access to Gov.uk forms
#109This is good news, but aren't well-phrased questions a strong suit of Gov.uk forms? Other government departments might not be familiar with proper guidelines for form creation. Has this issue been approached? (curious, as I'm not British)
It’s now easier than ever to make a government form!
And, even when a process might be better delivered via a different mechanism… a form becomes a low friction way to do it.
And a bad form might be worse than no form.
Re: We’re opening up access to Gov.uk forms
#110The GOV.UK Design System team [1] is really doing great work. Wish there would be more like this from other governments. [1] https://design-system.service.gov.uk/design-system-team/ Edit: Apparently there are a lot! Really nice to see.