#iosdev

SecondCopy — Mode A is alive

I've got the Misrecogniser running end-to-end. The app now routes OCR + what3words + Ezra (GPT) into a three-line caption that sits comfortably in the APD register—grounded in what the camera sees, nudged by place, and allowed to be a little sideways. It will miscaption and misrecognise; it will also land on those odd, enlightening phrasings I wanted.

What’s happening on each label

Photo → OCR: pull concrete nouns/verbs from the page/scene.

w3w: fold in 1–2 words from the location (no slash soup).

Ezra prompt: ask for three lines, lowercase, field-note tone; line 2 must anchor to at least one OCR keyword.

Post-process: de-fluff, enforce anchors, keep it legible.

Output: ZPL to the Zebra QLn420 over Wi-Fi, plus a PNG “second copy”.

Quality of life

Preview now renders as a true 4×4″ square (matches the printed label).

Captions lean observational/philosophical rather than cryptic riddles.

Why I like it

SecondCopy treats misrecognition as material. The label is a tiny field report: context + place + a thinking error that occasionally hits the truth at an angle.

Next job — Mode B (Relay to Ezra)

I'm turning this from a private tool into a public submission app:

Users create as in Mode A.

Instead of printing locally, they tap Relay to Ezra.

The app uploads PNG + ZPL + metadata to a small cloud inbox (Firebase).

A home listener watches the queue and auto-prints to the Misrecogniser in the studio.

The user still keeps a “second copy” in Photos.

The Waiting Game...

We want to give the Habitica team time to get back to us on our design choices, and sometimes you just need to take some time to deal with other life stuff, so that is what we are going to do today.

Starting tomorrow we are looking into some other projects that we can work on, so that any time we need to pause or wait on feedback we have things to post about.

After a bit of sorting through the help-wanted tickets on @habitica’s GitHub issues list @array-of-frost and I settled on a small ticket for fixing a UI issue. Currently, when you view a user’s profile on the iOS app, you can see their Level but not their class (they’d like it to show both):

Since they plan to do a design overhaul of the user profiles eventually we don’t want to bother changing too much - just enough to add the missing class info. Still, there are a couple of different ways we could fix this we decided to start by creating some (admittedly shitty) mockups to show a couple of solutions we thought would work well by editing current screenshots of my profile.

Solution 1 (On the Left below)

We put the class info in the profile header right next to where the level label currently is.

The Pros of this solution: The info is in the same place as before.

Cons: having so much info in such a small place makes the profile header feel cramped and busy and the text small and hard to read.

Solution 2 (On the Right Below)

We put the class and level info into a table row below the Username row.

Pros: The header area feels less cluttered, it keeps the design a bit more consistent since all the other user stats (bio, username, etc) are down  in the tableview, and it’s a lot less fiddly to implement in code than solution 1.

Cons: There may be other design considerations (Like keeping the UI of the iOS app consistent with the Android app) that we’re not aware of that would make this solution a no-go.

And Now We Wait

AURA by Photek from the album Solaris (2000) on Astralwerks.