Discussion
Some UX failures that are so easy to fix. This is a perfect example. In the new Wow Forever game, you are limited to three characters. But After you create three, you are somehow allowed to start a fourth.
But only when you get to the final final step and hit FINISH do you get the "no, sorry" error message. The same check could have been made at the very beginning of this flow rather than at the very end. And it would have saved so much frustration.
@scottjenson My grocery store's self checkout says, "Have you scanned your shopper reward number?" *after* I scan my first item.
You know what I just scanned. Why are you asking me about something we both know I haven't done?
UX is really so simple. Just figure out exactly what info you need at each step of the process, no more no less.
That’s what makes UX so incredibly difficult :)
@benpate Fair enough. But I'd argue any time you put up an error dialog, you have an opportunity to ask "Could this have been prevented?" The answer may be no, but it's so often yes..."
@benpate @scottjenson where is the NOT OKAY button
Install Fedizen
Get the full app experience
@scottjenson this feels like one of those situations where a backend requirement develops separately from the frontend design. You end up having users get to the final step that actually submits the request to the backend, and the backend returns an error that wasn't checked by the frontend.