121–130 of 222 posts
Earlier quoted context omitted.
I nearly quit when it said "your age and birthdate don't match". Glad I got through because the bow and check also gave me a laugh.
I absolutely expected that. Having both birthdate and age was the Chekhov's gun on that form. The only thing better would be to have them on different form pages.
Earlier quoted context omitted.
Flag icons in grayscale. My country's flag is three equally large horizontal bars, just like 12 other nations (and a lot more if you count variations like little insignia etc). [1] 1: https://en.wikipedia.org/wiki/Triband_(flag)
I'm one of those 12 too, I just went to dev tools and searched for my country's 2 char code.
Earlier quoted context omitted.
Really the entire idea of client/server-side email "validation" kind of seems like an ancient, cockroach-like anti-pattern that is impossible to stamp out. Like, what is the problem they're even solving? One validates email addresses by sending an email with a token the user then acts on. There are useful things to do with emails, like checking against already registered ones (including any blacklists), but I can't t…
> Even on the left side of the @ a surprising number of scripts seem to fail on things that are perfectly acceptable characters. I've had an input require a minimum of 3 characters on the left side of the @ to register. My email was just "me@example.com" using my own domain name. A perfectly valid email address. I am also unable to sign up for Id.me for the IRS because it rejects both of my personal email addresses.…
Love all the little details. Some favorites: * Clicking 'expand' button on any dialog (T&C) expanded the dialog to cover the page but doesn't expand the contents to match * Tiny flag icons to select country * The age slider that went from 0-180 years and didn't update as you slid it (fun on a trackpad) * number input for house number that required clicking on the arrows to change it one at a time * utterly ambiguous…
But captchas were truly the icing on the cake.
The only thing missing would have been a 'subscribe to our newsletter' feature 2 seconds after each page loads.
Love all the little details. Some favorites: * Clicking 'expand' button on any dialog (T&C) expanded the dialog to cover the page but doesn't expand the contents to match * Tiny flag icons to select country * The age slider that went from 0-180 years and didn't update as you slid it (fun on a trackpad) * number input for house number that required clicking on the arrows to change it one at a time * utterly ambiguous…
Earlier quoted context omitted.
Usually you can hit the year number and it'll let you skip whole years. But yeah.
iirc the Android 4 date picker had a microscopic hit-area on the date where, if clicked, would display a year-key-in dialog. I don't know if newer ones have this. I hate date pickers so much that I use the Google Assistant in all its hellish, buggy glory to create appointments for my calendar on my phone.
Flutter provides separate Material date picker [0] and time picker widgets [1], but no date-time picker widget that displays the selected DateTime and lets the user change the date or time. When I asked Flutter team for one 2 years ago, their UX person refused to add it, saying that because it's not in the Material Design Spec [2] [3] that it doesn't belong in the Flutter widget library.
Flutter does implement the excellent iOS DateTime picker [3].
[0] https://api.flutter.dev/flutter/material/showDatePicker.html
[1] https://api.flutter.dev/flutter/material/showTimePicker.html
[2] https://material.io/components/date-pickers
[3] https://material.io/components/time-pickers
[4] https://flutter.dev/docs/development/ui/widgets/cupertino
Earlier quoted context omitted.
I have a personal punishment policy for any obvious violation of UX/UI - they will permanently and irrevokably lose me as a customer. Even if they fix it, I won't budge. Leadership needs to use their own products and if they allow this to go to production, I wonder what they're doing behind the scenes. Small battles that I pick, but by god it is so satisfying.
So a small shop that can only pay 1 fresh bootcamp dev who is trying their hardest doesn’t get your business because they can’t keep up with several hundred Frontend google devs. Seems a little silly and absolutist.
Earlier quoted context omitted.
I have a personal punishment policy for any obvious violation of UX/UI - they will permanently and irrevokably lose me as a customer. Even if they fix it, I won't budge. Leadership needs to use their own products and if they allow this to go to production, I wonder what they're doing behind the scenes. Small battles that I pick, but by god it is so satisfying.
So a small shop that can only pay 1 fresh bootcamp dev who is trying their hardest doesn’t get your business because they can’t keep up with several hundred Frontend google devs. Seems a little silly and absolutist.
Earlier quoted context omitted.
Really the entire idea of client/server-side email "validation" kind of seems like an ancient, cockroach-like anti-pattern that is impossible to stamp out. Like, what is the problem they're even solving? One validates email addresses by sending an email with a token the user then acts on. There are useful things to do with emails, like checking against already registered ones (including any blacklists), but I can't t…
> what is the problem they're even solving? The problem they're solving is that a lot of people just enter their email wrong and then wonder why they didn't get the signup email. > Like if someone tries to register an already registered email, send an email about it don't leak that it's registered. This is something that's cargo-culted far too often. Maybe for some services it's worth keeping secret which emails are…