---
title: "One icon, three signals"
description: iOS 27 packs Wi-Fi, cellular, and battery into one circular glyph. It's genuinely clever—and the debate it sparked is even more interesting.
type: blog
date: 2026-09-11
authors:
  - name: PonyMux
    url: https://x.com/ponymux
seo:
  title: "One Icon, Three Signals — iOS 27's Status Bar Design"
  description: iOS 27 packs three status bar icons into one circle. What makes it work, what people got wrong about it, and a small design story from building a terminal sidebar.
  image: /og/blog/one-icon-three-signals.png
  x:
    creator: "@ponymux"
---

*By PonyMux · September 11, 2026*


<img src="/ui/ios27-status-icon.gif" alt="Three status bar icons merging into one circular glyph" style="border-radius: 16px;" />

Everyone's been talking about the iPhone Duo. The hinge, the cover
screen, the price. But the detail that stuck with me was much smaller
than all of that.

In the corner of the cover screen, the three status bar icons that have
lived side by side for almost twenty years—Wi-Fi, cellular, battery—got
folded into one small circle. Outer ring for battery. Wi-Fi fan in the
center. Four dots at the bottom for signal strength.

The first wave of reactions was mostly "that's clever," and it is. But
then the designers started arguing about whether it was actually
*readable*. That's where it got interesting.

## Why it works

The reason the combined icon doesn't look like a mess is that the three
signals use three different kinds of shape. Battery is a continuous
arc. Wi-Fi is a symbol. Cellular is a row of dots. Arc, symbol, dots—
they look fundamentally different from each other, so your eye can pick
them apart even when they're sharing the same space.

Apple didn't just make three icons smaller and cram them together. They
found three visual channels that don't interfere, and layered them. The
unfold animation makes this explicit: the circle splits apart, each
piece stretches back into its original shape, and you can see exactly
what was packed together. As someone put it: "the way the animation
explains the design."

<p class="pony-turn">The trick isn't making things smaller. It's finding the channels that don't collide.</p>

## What it costs

The criticism that followed is worth taking seriously. A battery
silhouette with a fill level is self-explanatory—you see the charge. A
notched arc is a gauge you have to learn. Same with cellular: "three out
of four bars" reads instantly, "three out of four dots" less so.

Then there's the failure state. When all three signals are low, the arcs
thin out, the dots get sparse, and the whole thing collapses into one
vague shape. With separate icons you can see at a glance which one is in
trouble. With the combined icon you have to look closer.

But here's the part most coverage skipped: the combined icon only
appears on the 5.4-inch cover screen. Unfold the phone, and iOS 27
reverts to the classic three. Control Center shows them separately too.
Apple isn't proposing a new universal language—they're acknowledging a
specific constraint, and accepting the tradeoff *there* while keeping the
old solution everywhere else.

That's actually the most interesting design decision in the whole thing.

<blockquote class="pony-point">
  <p>The best design decision here wasn't the combined icon. It was choosing not to use it on the bigger screen.</p>
</blockquote>

## A small related story

I've been thinking about all of this because I ran into a version of the
same problem while building [PonyMux](/). Much smaller scale, totally
different product, but the question was the same.


*PonyMux interface view: status.*


PonyMux has a sidebar with a list of terminal sessions. Each row needs
to tell you three things: an emoji the user picked to label the session
(like 🚀 or ✓), the runtime status (running, waiting, error), and
whether the session is hibernating.

The first version had all three, but in three different places. The
emoji sat on the left. The status spinner sat on the trailing edge. And
"zzz" for hibernation was inline in the subtitle, right after the
process name.

*PonyMux terminal row — phase 1.*


The first consolidation: the emoji got a proper circular home on the
left side, and the status indicator moved from the trailing edge into a
corner badge on that same circle. The row went from three locations to
two. But zzz was still sitting in the subtitle.

*PonyMux terminal row — phase 2.*


Then zzz moved into the same corner badge spot. This worked because a
sleeping session has no active status—the badge is always free when zzz
needs it. They take turns. Never collide.

*PonyMux terminal row — phase 3.*


Three things, one 24-pixel circle. Each step was just asking: does this
really need its own spot? And each time the answer was no, the row got
quieter without losing anything.

The reason this was easier than Apple's problem: the emoji is
self-explanatory (the user chose it), and the corner badge dimensions
are mutually exclusive—no "bad day" scenario where everything degrades
at once. Different constraints, lower stakes. But the underlying
question was the same.

If you're curious about how the status system works in practice—what
each state means, how notifications work, and how the facet bar ties it
together—there's a [full walkthrough in the docs](/docs/agent-status).

## One more thought

The iOS 27 icon is a good design. The criticism of it is also good
criticism. That's not a contradiction—it's just how real tradeoffs work.

Combining signals into one shape isn't always better than keeping them
apart. It depends on the space, the signals, and the ways they can fail.
On the cover screen, Apple decided the density was worth it. On the
unfolded display, they decided it wasn't.

<p class="pony-turn">Density doesn't come from compression. It comes from discovering that your signals were never competing for the same visual channel in the first place.</p>

Arc reads as quantity. Symbol reads as identity. Dots read as count.
Three different questions your eye answers in three different ways—
that's why they can share a circle. That's the part worth
remembering: not the specific solution, but knowing how to look for
channels that were already complementary.
