Designing in public: mockups, a gold rule and a better scanner
How Hangar 64's screens get made: two or three mockups, a pick, a build, a phone test. And the small rules that came out of it.
I'm not a trained designer, so I built a process that makes up for it: never build the first idea. Every screen gets two or three mockups first, made as real web pages or in Canva, using the app's actual colors and cars. I pick one, it gets built, and then I test it on my own phone before it ships.
One color, one meaning
Gold was everywhere at first: the in-stores card, follow buttons, highlights. Then I noticed gold also marks Super Treasure Hunts, the rarest cars in the app. If everything is gold, nothing is special.
So I made a rule: gold only means STH and Premium. The in-stores card turned green with a small pulsing dot, follow buttons became rose hearts, and the case page lost its gold box. It took a few passes through the app, but now gold means something again.
The scanner that looked like a barcode reader
The first scanner showed a big rectangle in the middle of the camera. Testers kept pointing it at the barcode. The rectangle looked like every barcode scanner they'd ever used.

The fix was a thin strip with corner brackets, the shape of one line of text, with a faint example code inside and a small crossed-out barcode underneath. Then I learned something from testers holding real cards: the code isn't in the same place on every package. Mainline and Silver cards have it at the top of the back, Premium cards just above the barcode, and RLC boxes and blisters each in their own spot. "Where's the code?" now has a tab for each.
Cutting a feature I liked
The scan result first had a "Not right?" row showing every other version of the car. It was clever, but in testing it felt like too much on an already busy screen. I replaced it with one quiet line: "Not the right car? Scan again." Removing it made the screen better.
What's next
The next build is about people: friends, shared garages and seeing what others found this week. It'll go through the same loop: mockups, a pick, a build, a test.