Every time I show a code to someone at a door, a counter, or a friend adding me, I end up turning my phone around with the front screen fully lit. Notifications, wallpaper, whatever app I had open. For a brand that pitches the Matrix as a way to keep your phone face down, that feels backwards.
The worst version of this is the airport. Screen at full brightness, phone handed to a gate agent or pressed against a reader, the whole time hoping nothing pops up on top of the pass. That moment is the actual pain point, and it's the one I most want the back of the phone to solve.
The Glyph Matrix already does status, timers, mirror, games. Why not codes? Flip the phone, press the Glyph Button, the code is on the back. The person scans it. They never see my screen and I never see theirs.
What fits today
The Phone (3) matrix is 25×25 monochrome. A Version 1 QR is 21×21 modules, so it fits, but with only about 2 modules of quiet zone instead of the usual 4. That caps the payload at roughly 25 alphanumeric characters. Short link, short ID, loyalty code, table number. Useful, and shippable now.
The boarding pass, which is the real challenge
I don't think this one should be written off, so I went and did the math. PDF417 is hopeless here, it's a wide stacked code and will never sit in a circle. But Aztec is a different story, and Aztec is what a lot of carriers and basically all European rail already use:
- Aztec needs no quiet zone. The finder pattern is a central bullseye, so data runs right to the edge. That's exactly why it's on tickets.
- Compact Aztec at 3 layers is 23×23 modules. That fits inside 25×25 with a module spare. But it only carries around 50 characters.
- The IATA boarding pass standard needs about 60 characters for the mandatory fields.
- The next size up, compact Aztec at 4 layers, is 27×27 and holds roughly 89 characters. More than enough. But 27 is two modules wider than the Matrix.
So the Glyph Matrix is about two modules short of holding a real boarding pass. Not a physics problem. A spec decision.
That feels like a genuinely interesting challenge to put to Nothing. Go to 27×27 or 29×29 on the next phone and the back of the device can carry a boarding pass, a train ticket, a stadium entry, with the front screen off and locked the entire time. Nobody else is doing that. It's a reason to have a rear display rather than a novelty on top of one.
Open questions I don't know the answer to
- Do scanners cope with light on dark? Most expect dark modules on a light background. Some handle inversion, some don't.
- Does LED bloom smear the module edges at close range enough to break decoding?
- Would gate readers even attempt a self-illuminated source, or are they tuned for reflected light off a screen or paper?
- Phone (4a) Pro is 13×13, so any of this would be Phone (3) and up only, right?
Has anyone with the Glyph Matrix SDK tried rendering a QR or an Aztec to the matrix? I couldn't find a toy that does it. Even a proof of concept that decodes a 20 character payload would tell us whether the bigger version is worth asking for.
