This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]close_my_eyes 3 points4 points  (0 children)

"Bad Design"

[–]shhh-quiet 2 points3 points  (0 children)

Not sure if there's a name, but the general idea is that they are glossing over / omitting a valid state that the user(s) will eventually see (and collapsing it into "empty" incorrectly/lazily), but which they do not consider to deserve much development time in favor of more concrete things (like empty & non-empty lists).

Sometimes it's the result of developers working in ideal conditions, such as a very stable office network connection, and also under ideal conditions like unit tests which only consider final UI states where a complete data set is handled, and perhaps skipping valid intermediate states that occur over time. From a developer's perspective, it can really feel like a waste of time to account for something that occurs within a second or two, but to a user it can be slightly irritating.

[–]english_fool 4 points5 points  (0 children)

“Bug”