[kierangill]

I’ve seen a lot of positivity surrounding login.gov on HackerNews. I’ve never used the service and am unfamiliar with the quality of its implementation. Many commenters here point to login.gov as an example of the US government shipping good software. [1]

1. From the end-user’s perspective, what makes this a quality service? Is it simply better than other government alternatives, or does it compete with equivalent modern services from the private sector?

2. From the technologist's perspective, why is this considered quality software? I see it's an open-source Ruby on Rails app[2] with basic documentation, tests, and monitoring. As a non-RoR developer, I'm curious where this project falls on the spectrum from merely adequate to exceptional, and why.

[1] e.g., in this comment section: “login.gov is one of the few government services that as a private sector techie I'm in awe of”

[2] https://github.com/18F/identity-idp/

[js2]

> 1. From the end-user’s perspective, what makes this a quality service? Is it simply better than other government alternatives, or does it compete with equivalent modern services from the private sector?

I couldn't even login to ssa.gov before it was integrated with login.gov. Every year or two I'd give it a shot, it told me my account was locked, I had to visit a Social Security office to get it unlocked. I tried that once; the local office wasn't able to help. Fast forward a few years and the login process has been delegated to login.gov. I was able to prove my identity in the normal way (asked a bunch of questions from my credit report) and finally login.

So let's start with: it works.

But it's at least as good as any SSO that I use elsewhere (Okta, Apple, Google). It supports multiple factors (security key, passkey, TOTP, etc), something that, e.g., Fidelity only barely offers.

Besides that, it's visually appealing, having a nice modern look.

[chneu]

The old SSA identity thing was useless. Out of the dozen or so people I know who have tried to use it, not a single person was able to make it work.

It was so, so bad.

[rsanek]

I'm happy that it sounds like Login.gov is better than the broken solution we had before. At the same time, I do not think a basic functional login system is something that should be celebrated as a success.

[financetechbro]

Why would this not be a success? The previous system didn’t work, the govt created a specialized team that built a great functional product, and now it works... they fixed a problem? Many would consider that a success.

Maybe don’t look at this through the lens of a tech company or normal business (bc it’s not), but look at I from the perspective of how shite govt tech is. Not sure if you live in the states but you should try apply to unemployment in somewhere like Florida and then report back to me how having a functional login page isn’t a success.

[js2]

It's funny you say that. The NC DMV used to have a decent site for renewing registration. It was basic but functional. No bling. Took me like 2 minutes to use.

A few years ago they replaced it with a vendor solution (PayIt[1]). It's terrible. The renewal process easily takes 5x as long. The old site was two steps and a couple forms. The new site is this stupid chat bot interface that pretends like it's thinking between the half dozen or so steps it now is. On top of that, I get to pay $3 or something for the privilege of using it.

Annoys me just thinking about it.

I have a whole rant about our local private toll road's web site too. Easily in the bottom 5 sites I have to deal with. I may switch back to MA's EZ Pass just out of spite.

[1]: https://payitgov.com/

[riskassessment]

I would say that it is more than a basic functional login system. At the very least it also needs to authenticate identity.

[FireBeyond]

> Many commenters here point to login.gov as an example of the US government shipping good software.

Maybe. But in some ways, my experience with it was a heaping turd (registering my identity for the IRS):

"Scan the front and back of your Driver's License."

[upload scan of front of DL @ 200DPI]

"Unable to find a face in the image you uploaded."

[upload scan of front of DL @ 300DPI]

"Unable to find a face in the image you uploaded."

Huh. Maybe I'll try with a lower resolution.

[upload scan of front of DL @ 72DPI]

"Thank you, now please upload the back of your Driver's License."

Hmm, 72DPI worked for the front, so...

[upload scan of back of DL @ 72DPI]

"Unable to read a barcode in the image you uploaded."

[upload scan of back of DL @ 200DPI]

"Unable to read a barcode in the image you uploaded."

[upload scan of back of DL @ 300DPI]

"Thank you for verifying your Driver's License".

[zeagle]

As a Canadian end user with a nexus card, it just works, and it works with less errors and issues than my revenue canada login which has poor UI and steers me towards sign in partners with by making that the natural login with dark patterns. Come to think of it, I'm surprised the nexus program hasn't been cancelled yet.