This is what I'm referring to: http://twitter.github.com/bootstrap/components.html#badges
Is "badge" the commonly agreed upon term? Facebook and countless other sites use this feature to instantly update users via messages, requests and notifications. The UI pattern is becoming so common I fully expected to find something authoritative, like would with "dialog" or "modal". But what I've found has been all over the place: badge, notification, notifier, messages, jewel, update icon, bubble, counter, count... But which is the most semantic and accurate?
I fully acknowledge that I'm attempting to split hairs, but after initially intending to do a quick search on Google to find out what this pattern was called, I've now come to the conclusion that either: a) there is no consensus on how to describe this very common UI pattern. or b) I'm searching in the wrong places with bad assumptions and incorrect terminology (I'm hoping it's A, but I'm man enough to admit that it's more likely to be B).
StackOverflow's "badge" tag description is "A badge is a concise visual indication of something important to the user. For example, the number of unread emails in an email app can be displayed as a badge on the app's icon."
Alas, I'm still not convinced that the word "badge" is even remotely appropriate here.
Not to mention, my team is working on a feature that is completely unrelated that we've decided to call "badges" (not "badgers", very important distinction), so when I saw Bootstrap's .badges
component I started wondering if we were incorrectly applying a "known" concept.
So what is that little notification update icon thingy called?
Edit: after seeing a couple of replies I want to clarify that I'm asking this in the spirit of semantic coding. I don't really "care" about the design or usability aspect of the pattern, I am more interested in staying committed to being as semantic as possible with my code. After muddling through terribly written markup from countless open source projects I've come to fully understand the value of semantic coding. Understanding how to effectively describe classes is more than just a "UX" or vocabulary thing. It's about clean code, DRY code, organized semantic code that describes the content as accurately as possible, and so on.