51–60 of 74 posts
Earlier quoted context omitted.
If true, it displays celebration bunting on the front page on that day. Seems to be true for all holidays except Good Friday and the Queen's funeral (plus one (probably accidental) Easter Monday). https://github.com/alphagov/frontend/commit/5466c5f9ecc896a4...
I wonder why Good Friday doesn't get bunting.
How to not make great government websites: use random domain names instead of a single dedicated tld, different contractors and design for each, make sure there's enough overlap in functionality in-between each of them, and then regularly remind everyone that it's very easy to scam you with fishing attacks. Here are just some of the official French websites: service-public.fr impots.gouv.fr gouvernement.fr ameli.fr v…
Let's not forget the weird decision they made with the ac- domains, too. Instead of having all of them under one domain, they just use a naming convention: ac-nice.fr and ac-aix-marseille.fr are both official. It should've been nice.academie.fr and aix-marseille.academie.fr, imo.
Mandatory link to the one thing in the UK that actually works well: https://www.gov.uk Further details: https://www.gov.uk/government/organisations/government-digit...
I'm genuinely curious if people still think gov.uk is a good example - or I guess, as good as it was. I'm slightly biased from past experience but my feeling is a lot of the critical thinking that went into gov.uk has been lost. I just can't see the original form of GDS having an cookie banner on gov.uk for example. These were the guys that rightly pointed out that there is no actual need for people to have user acco…
DVLA is mostly very good, I'd say. Especially when dealing with vehicle registration, ownership change, taxing etc.
HMRC is in a category that I'd call "scary". Their website is nice and all but if you ever get locked out of their mobile app for confirming identity (or you delete it by mistake), it's really hard to fix the issue. This is connected to the fact that UK has no national ID card so they use various heuristic to confirm your identity.
UKVI is probably the worst as they don't offer a consistent experience. You can tell that some of their websites were developed in early 2000's and never updated.
Earlier quoted context omitted.
The Identity side of GDS has definitely been the worst. I wonder if due to the politics around that service, the thinking has stopped and the Just Get It Done, Even If It's Silly crowd has replaced it.
They're having another crack at it with GOV.UK One Login: https://www.sign-in.service.gov.uk/ I've participated in some user research with the team building it and I've also designed GOV.UK services pre-One Login that needed to verify people's identity. It's obviously a very difficult problem to solve when there's no universal central ID database. The people working on it are definitely cognizant of the failure of Ve…
Earlier quoted context omitted.
I'm genuinely curious if people still think gov.uk is a good example - or I guess, as good as it was. I'm slightly biased from past experience but my feeling is a lot of the critical thinking that went into gov.uk has been lost. I just can't see the original form of GDS having an cookie banner on gov.uk for example. These were the guys that rightly pointed out that there is no actual need for people to have user acco…
It depends. Usually local councils' websites are purely terrible. DVLA is mostly very good, I'd say. Especially when dealing with vehicle registration, ownership change, taxing etc. HMRC is in a category that I'd call "scary". Their website is nice and all but if you ever get locked out of their mobile app for confirming identity (or you delete it by mistake), it's really hard to fix the issue. This is connected to t…
Making the page (or their services) work well is in contradiction to the goals set by management.
Mandatory link to the one thing in the UK that actually works well: https://www.gov.uk Further details: https://www.gov.uk/government/organisations/government-digit...
I'm genuinely curious if people still think gov.uk is a good example - or I guess, as good as it was. I'm slightly biased from past experience but my feeling is a lot of the critical thinking that went into gov.uk has been lost. I just can't see the original form of GDS having an cookie banner on gov.uk for example. These were the guys that rightly pointed out that there is no actual need for people to have user acco…
I just re-registered to postal vote from overseas, and the information and links were a labaryinth, often sending me in circles.
Out of exasperation – since I thought my use case didn't match what I was looking for – I clicked the big green "Start" button on the wizard and it worked swimmingly.
When re=applying for a passport in the recent past it was great too, even allowing me to upload a photo from my phone.
Perhaps they have focused on some key interactions that would typically be seen as complex.
Mandatory link to the one thing in the UK that actually works well: https://www.gov.uk Further details: https://www.gov.uk/government/organisations/government-digit...
My sister and I are currently handling my mother's recent death, and with the exception of one slightly-out-of-date piece of information (you no longer need to pick up the Cause Of Death form to exchange it for Death Certificates - the CoD form is forwarded to the registry office), it's been extremely helpful.
Mandatory link to the one thing in the UK that actually works well: https://www.gov.uk Further details: https://www.gov.uk/government/organisations/government-digit...
How to not make great government websites: use random domain names instead of a single dedicated tld, different contractors and design for each, make sure there's enough overlap in functionality in-between each of them, and then regularly remind everyone that it's very easy to scam you with fishing attacks. Here are just some of the official French websites: service-public.fr impots.gouv.fr gouvernement.fr ameli.fr v…
Yeah, the Netherlands got 1,800 of those..
How to not make great government websites: use random domain names instead of a single dedicated tld, different contractors and design for each, make sure there's enough overlap in functionality in-between each of them, and then regularly remind everyone that it's very easy to scam you with fishing attacks. Here are just some of the official French websites: service-public.fr impots.gouv.fr gouvernement.fr ameli.fr v…
That's a very unfair take. The examples you list are of a completely different nature. > gouvernement.fr info.gouv.fr These are the same website. gouvernement.fr is a legacy URL that redirects to info.gouv.fr. Why did you include both? > ameli.fr As I'm sure you know, in France, social security is not administered by the government directly but by the social partners. They're in charge of managing ameli.fr, not the g…
I was making a non-exhaustive list of the ones that came through my mind.
> As I'm sure you know, in France, social security is not administered by the government directly but by the social partners.
What matters is whether that's an entity of the state or of a third party that is potentially trying to scam you.
I could have included pole-emploi.fr, oh sorry, I mean, francetravail.fr in my list.
All of the above plus the ones of the sibling comments under a single .etat.fr, .admin.fr, .public.fr, .france or whatever would only make sense. None of us would have to double-check again whether the information we're getting or form we're filling is official or not.