Iconic Arbitrary And Symbolic

Iconic Representation — arbitrary and symbolic

Arbitrary icons have no inherent connection to what they represent. The hamburger menu (three horizontal lines) doesn't look like a menu in any physical sense. The kebab menu (three vertical dots) doesn't look like options. The "@" symbol for email doesn't depict email. These icons work only because users have learned the convention through repeated exposure.

This is the most fragile form of iconic representation. New users don't recognize arbitrary icons. The icons depend entirely on convention strength, which varies by domain, by audience, and over time.

But arbitrary icons also have an unmatched advantage: they can compress meaning into a single recognizable form for functions that have no good visual referent. "More options" has no physical analog; the kebab menu fills that gap. "AI assistance" has no physical analog; the sparkle is filling that gap.

How arbitrary icons gain meaning

An arbitrary icon becomes recognizable only through accumulated exposure. The mechanism:

1. A few influential products use a particular form for a particular function.
2. Other products copy the convention.
3. Users encounter the form in many places associated with the same function.
4. Eventually, users recognize the form on sight, even in products they haven't seen before.

This is convention-formation. It usually takes years. The hamburger menu, for example, was used in some interfaces in the late 2000s, became more common around 2010–2012, and was a near-universal mobile convention by 2015. The kebab menu followed a similar trajectory a few years later.

Some conventions never make it. Many proposed icons are tried, fail to spread beyond the originating product, and remain opaque to users from other products. The convention-formation process is genuinely contingent — designers can't reliably predict which forms will become universal.

When arbitrary icons work

Arbitrary icons work when:

The audience has been exposed to the convention. A mobile-app user from 2025 recognizes the hamburger menu, the kebab menu, the sparkle for AI. A user from 2010 might not. A user who's never used software might not recognize any of them.

The function doesn't have a strong visual referent. "More options," "menu," "AI features," "share" — none of these have obvious physical referents. Arbitrary icons fill the vocabulary gap.

The icon is reinforced by usage. Users learn arbitrary icons through repetition. An arbitrary icon used in a single place in your product is harder to learn than one used in a consistent role across the product.

The icon is supported by context. Even arbitrary icons gain interpretability from where they appear. A kebab in the corner of a list item is more clearly "actions for this item" than the same kebab in an unexpected location.

When arbitrary icons fail

Arbitrary icons fail when:

The audience hasn't seen the convention before. Domain-specific icons (a "diff" icon in developer tools) for a non-developer audience. Recent conventions (the AI sparkle, in 2024) for users who haven't used current AI tools.

Multiple competing conventions exist. The "share" icon has different forms on Apple and Android platforms; users from one platform may not recognize the other's icon. Without label, the icon is ambiguous.

The icon is one of many similar arbitrary forms. A toolbar with the hamburger menu, the kebab menu, the bento menu (3×3 dots), and the meatballs menu (three horizontal dots) — all variations on "menu" that users are expected to distinguish. Conventions have to be sharply different to coexist.

The convention is changing or fading. Conventions stabilize over time but also drift. Users in transition periods may have trouble.

You invent your own arbitrary icon. A custom icon designed for your product without external precedent. Users have no convention to draw on; recognition is essentially zero. Without significant onboarding, the icon doesn't communicate.

Working with established conventions

When a convention exists for the function you need, the safe path is to use the established form even if you have a design opinion. The icon's recognizability comes from convention strength, not from intrinsic merit. A custom "share" icon, however well-designed, doesn't have the convention strength of the platform-native share icon.

The exceptions:

• The convention is dying. The floppy disk for save is increasingly anachronistic. Reaching for it because it's "the convention" may not serve users who don't recognize the source.
• The convention conflicts with a stronger one. If your product's brand uses a specific iconographic language, forcing in an external convention may break the visual coherence. In these cases, label the icon to compensate.
• You're operating in a domain with a stronger convention. Some domains have icon vocabularies more specific than the generic UI conventions.

When to invent vs. when to label

When a function needs an icon and no established convention exists, the choice is between inventing a custom icon (risky for recognition) and using a text label (safe but less compact).

Use text: for any infrequent function, any function where misclick is costly, any function where the audience varies in sophistication.

Use a custom icon (with paired label): when space is tight and the function is used frequently enough for users to learn through repetition. Pairing with a label lets the icon develop convention strength gradually while supporting recognition immediately.

Use a custom icon alone: essentially never, unless you're reproducing an existing convention from a related context. Inventing a new arbitrary icon for icon-only use is almost always a mistake.

Working with new conventions

Some functions are too new to have established conventions yet. AI assistance is the current canonical example: dozens of products are introducing AI-powered features simultaneously, and a convention is still stabilizing. Currently:

• The sparkle (often a four-pointed star or stylized starburst) is the most common.
• Some products use a chat-bubble variant.
• Some use a brain icon.
• Some use a robot or "bot" icon.
• Some use a wand or magic-wand icon.

None of these has reached the convention strength of the hamburger menu. Users may or may not recognize each, and the recognition rates vary by audience.

The pragmatic guidance: pick the most-common convention for your audience, pair with a label when first introducing it, and pay attention as the convention stabilizes. Be ready to update your icon if a different form wins.