How an emoji becomes part of the shared standard
A new emoji has to solve a coordination problem: phones and apps need to agree that a particular character exists before they can reliably exchange it. The Unicode Consortium maintains that shared character standard. Its approval gives an emoji a recognized code point—a number that devices can use to identify it—rather than prescribing exactly how it must look.
Proposals are assessed for practical reasons to add a character, including whether people are likely to use it, whether it is distinct from existing emoji, and whether it can be represented clearly. A proposal for a pancake, for example, is not just a request for a cute drawing; it must make the case that the food merits its own place in a standard used across languages and platforms.
Approval is not the same as appearance
Once a character is accepted, the work is not over. Apple, Google, and other platform makers create their own artwork for it. That is why the same emoji can look different on different phones: Unicode establishes what the character means in the shared system, while each company decides how to draw it.
This division lets a message travel between devices without requiring every company to use identical illustrations. It also means approval does not guarantee that an emoji appears immediately everywhere; platforms must add support for it. The consortium decides which symbols enter the common vocabulary, but the final pat of butter—or whether there is one at all—belongs to the artist designing that platform’s version.
