pull down to refresh

This language pops up...

must be at least 1000

...and it goes red. Unless you remove it completely. Kind of non-standard, or just oddly subjective UX, IMO.

I couldn't reason about why the choice would be from the set {0, 1000, 1001, 1002, ...}. I would have expected any positive integer if it was actually optional.

Hmmm I can see why that'd be confusing. I'm just not sure how to design it otherwise. Any ideas?

reply

...right now, you kind of have like a Schrödinger-cat equivalent of a None/Zero.

Maybe subtle change to the form validation logic:

Current:

  • {Negative Integer} -> Red -> "must be at least 1000"
  • {None} -> Yellow -> lets you post
  • {0, ..., 999} -> Red -> "must be at least 1000"
  • {1000, ...} -> Yellow -> lets you post

Proposed:

  • {Negative Integer} -> Red -> "must be 0 or at least 1000"
  • {None, 0} -> Yellow -> lets you post
  • {1, ..., 999} -> Red -> "must be 0 or at least 1000"
  • {1000, ...} -> Yellow -> lets you post
reply

Ah I get it! I just need to say 0 is allowed!

reply

deleted by author

deleted by author

deleted by author

deleted by author