Before Unicode: The Pixel Gardens of Japan

The flower emoji we tap out today did not begin as a Unicode committee’s idea — they began as tiny, hand-drawn pixel art on Japanese mobile phones in the late 1990s, years before “emoji” meant anything to the rest of the world.

The most commonly cited starting point is 1999, when Japanese telecom NTT DoCoMo released a set of 176 emoji designed by a young interface designer named Shigetaka Kurita for its “i-mode” mobile internet service. Kurita built each character on a tiny 12-by-12 pixel grid, drawing inspiration from manga, the Zapf Dingbats typeface, and existing emoticon conventions, in order to pack more visual meaning into the extremely limited screen space and character allowances of early mobile phones. The set was an instant hit in Japan and was quickly copied by rival carriers, and it’s this collection that the Museum of Modern Art in New York eventually acquired for its permanent design collection in 2016 — a rare case of software characters being treated as fine art.

It’s worth noting, though, that Kurita’s set has since been dethroned as the “first” emoji set by emoji historians. Research published by Emojipedia has traced an earlier 90-character set released by the carrier SoftBank in 1997, which — notably — is also where the now-iconic pile-of-poo emoji originated. Flowers were part of these early Japanese sets from the start, reflecting a visual culture where seasonal floral imagery (particularly cherry blossoms) was already deeply embedded in everyday communication, calendars, and design.

Because each Japanese carrier — DoCoMo, SoftBank, and au/KDDI — built its own incompatible emoji set during this period, the same “flower” character could look completely different, or map to a completely different code point, depending on which network you or your recipient used. This fragmentation is exactly the mess that Unicode standardization was eventually built to solve.

Going Global: Unicode 6.0 and the Class of 2010

For emoji to work across brands, countries, and operating systems, they needed a single shared numbering system — which is where the Unicode Consortium comes in. Unicode is the international standard that assigns every character, symbol, and emoji a unique code point so that a message sent from an iPhone displays correctly on an Android phone, a Windows PC, or anywhere else.

The vast majority of today’s core flower emoji were formally folded into this global standard in a single release: Unicode 6.0, published in 2010. This is the moment the modern flower emoji lineup as most people know it was born, all filed under the “Animals & Nature” category:

• Tulip (U+1F337)
• Cherry Blossom (U+1F338) — directly inspired by Japanese sakura, and still one of the most-used flower emoji today
• Rose (U+1F339)
• Hibiscus (U+1F33A)
• Sunflower (U+1F33B)
• Blossom (U+1F33C) — the generic yellow daisy-style flower, often just called “the flower emoji”
• Bouquet (U+1F490)
• White Flower (U+1F4AE) — a stylized cherry-blossom rosette

Interestingly, most of these characters weren’t actually usable as full-color emoji on major platforms until several years later. Unicode 6.0 assigned the code points and text meaning, but it was the release of “Emoji 1.0” in 2015 — the point at which Unicode formally began tracking emoji as their own versioned category, retroactively — that cemented these as the graphical, colorful characters we associate with modern texting. Apple had already brought many of them to iPhone keyboards outside Japan starting around 2011, which is really what triggered their explosion into global, everyday use.

The Additions: How the Bouquet Grew

Unicode releases a new set of characters roughly once a year, and flower emoji have picked up a handful of newcomers since that original 2010 batch — each addition reflecting a different gap someone on the Unicode Emoji Subcommittee decided was worth filling.

Rosette (🏵️) arrived with Unicode 7.0 in 2014. Rather than depicting a specific flower, it’s a stylized award-ribbon or cockade shape — floral in form but tied more to ideas of achievement, honor, and recognition than to nature itself.

Wilted Flower (🥀), sometimes called Wilted Rose, was added in Unicode 9.0 in 2016. It filled an emotional gap the original set didn’t cover: nearly every flower emoji up to that point was a symbol of freshness, romance, or celebration, and there was no way to express loss, heartbreak, or the end of something using a flower. The wilted, drooping bloom did exactly that.

Lotus (🪷) followed much later, in Unicode 14.0 in 2021. Its addition was notable because it filled a distinctly non-Western gap in the emoji set: the lotus carries deep religious and cultural significance in Buddhism, Hinduism, and Jainism, representing purity, enlightenment, and rebirth, and it’s the national flower of both India and Vietnam — none of which was represented anywhere in the flower emoji lineup before.

Hyacinth (🪻) is the newest addition, arriving with Unicode 15.0 in 2022. Compared to the others, its adoption push was less about symbolism and more about simple representation — hyacinths are a widely grown garden and cut flower that, somewhat surprisingly, had no emoji equivalent for over a decade after the original set launched.

Each of these later additions went through Unicode’s public proposal process, where anyone can submit a case for a new emoji, arguing for its frequency of use, distinctiveness from existing characters, and expected popularity — a process that can take a year or more from proposal to your keyboard.

Same Code Point, Different Flower: The Design Free-For-All

One of the stranger quirks of the emoji system is that Unicode standardizes the meaning and code point of a character, but not its appearance. Every company — Apple, Google, Microsoft, Samsung, WhatsApp, Meta, Twitter/X — designs its own visual interpretation of “U+1F33C BLOSSOM” or any other flower character, which is why the same emoji you send can look noticeably different depending on which device the recipient is using.

This has led to some genuinely inconsistent flower emoji over the years. The generic Blossom emoji, for instance, has been rendered as pink on some platforms and yellow on others; White Flower has appeared with a red outline on one platform and an orange outline on another, sometimes including the Japanese character 花丸 (roughly “very well done,” referencing its origin as a teacher’s stamp of approval on schoolwork in Japan) and sometimes omitting it entirely. These aren’t just cosmetic differences — they occasionally created genuine confusion about what a flower emoji was even supposed to represent, since a design change by one platform could shift a symbol’s implied meaning without any change to its underlying Unicode definition.

Platform vendors do periodically redesign their emoji sets for style consistency (flattening, simplifying, or restyling entire libraries), which means a flower emoji sent in 2015 may render quite differently to the same character sent today, even though nothing about its Unicode code point ever changed.

What the Flowers Actually Mean, in Practice

Emoji meaning is rarely fixed by Unicode itself — it’s negotiated by usage, the way slang always has been. A few patterns have solidified over more than a decade of use:

Cherry Blossom (🌸) carries the most specific cultural weight of any flower emoji, tied directly to its Japanese origin as a symbol of spring, renewal, and the beauty of impermanence — the sakura blooms only briefly each year before falling, a metaphor that long predates emoji and appears throughout Japanese art and poetry. In casual use it’s become shorthand for “soft,” “cute,” or gently romantic — often deployed where a full rose would feel too intense.

Rose (🌹) is the most straightforwardly romantic of the set, drawing on the flower’s centuries-old Western association with love and passion, and it remains one of the most-used flower emoji in romantic or affectionate messages.

Sunflower (🌻) and Blossom (🌼) trend toward simple, unambiguous positivity — happiness, warmth, and general appreciation of nature — without the specific romantic or cultural baggage of the rose or cherry blossom.

Hibiscus (🌺) and Bouquet (💐) occupy more occasion-based niches: hibiscus often signals a tropical or vacation context, while bouquet is the default choice for congratulations, thanks, or general well-wishes, functioning as a kind of catch-all “here are flowers for you” gesture.

Wilted Flower (🥀) is the outlier of the group — the only mainstream flower emoji whose default emotional register is negative, used to signal heartbreak, disappointment, or the end of something.

Lotus (🪷) has picked up associations with mindfulness, yoga, and wellness culture in casual Western use, layered on top of (and sometimes flattening) its deeper original religious symbolism.

None of these meanings were designed in — they emerged the way word connotations always do, through years of accumulated use across millions of conversations, then got reinforced by emoji reference sites and dictionaries that document the drift after the fact rather than dictating it beforehand.

Where Things Stand Now

The flower emoji roster has grown from an implicit, carrier-specific handful of Japanese pixel icons in the late 1990s into a standardized, cross-platform set of a dozen distinct characters spanning Unicode releases from 2010 through 2022 — tulip, cherry blossom, rose, hibiscus, sunflower, blossom, bouquet, white flower, rosette, wilted flower, lotus, and hyacinth. Each new addition has tended to fill a specific gap rather than simply add more decoration: an emotional register that was missing (wilted flower), a cultural or religious tradition that had gone unrepresented (lotus), or simply a widely grown flower nobody had gotten around to including yet (hyacinth).

Given that pattern, future additions are more likely to keep chasing genuine representational gaps — flowers tied to specific cultures, regions, or emotional registers not yet covered — than to simply expand the category for its own sake. The Unicode Consortium’s public proposal process means, in principle, anyone can make that case for the next one.