I counted my sign-ins yesterday. From 6:00 AM to 9:00 PM, I was asked to enter or verify an identity seventeen times. Not by mischief, by normal apps I use. Email, banking, streaming, a grocery order, a couple of work tools, my dog's vet portal (?), my kid's preschool app, a parking meter, a gas station's loyalty rewards thing. Some of those were biometric, which was painless. Some were full passwords. One was an SMS code that took three minutes to arrive.
Every one of those sign-ins had a reason. Most of them even had a good reason.
But collectively, they had an effect. By lunch I had been reminded, seventeen times, that I am a user-of-systems, and that every system knows a little about me, and that the cost of getting to the thing I wanted, a coffee order, a parking meter, a dog's prescription, was to hand over an identity.
When I set out to build CardCue Pro, the question I got stuck on early was: does a gift card app need to know who you are?
The honest answer is no. Gift cards, from the app's point of view, are a stack of numbers and metadata. A Starbucks balance of $14. A PIN. A barcode. An expiration date. The app's job is to remember that stack of things and surface it at the right moment. None of that job requires knowing that you are you.
So the app doesn't ask.
Cue has no accounts. There is no sign-up screen. There is no email verification. There is no "create a password" dialog. There is no OAuth flow, no Sign-In-with-Google, no passkey, no magic link, no 6-digit SMS code. You open the app and you're in. If you get a new phone, your cards come along through iCloud, that's Apple's doing, not ours, and you open the new phone's app and you're in there too.
I want to stop and say: this was not a casual decision. There is a conventional wisdom in software that every serious app should have accounts, because accounts are where retention lives, where analytics live, where you collect the email addresses you'll eventually need when you pivot, where you build a defensible moat. I've worked at companies that treated "account creation" as the most important metric of the week. I am not pretending I don't know why people build accounts.
I built CardCue Pro without them anyway. Not out of purism, out of fit. The job of the app is to remember things on your behalf; the more it knows that it doesn't need, the less trustworthy it becomes. An app that remembers my gift cards and remembers my email and remembers my login history and remembers my device fingerprint is a more dangerous piece of software than one that remembers only the cards. The dangerous version is what the industry usually ships. The safer version is what the product actually needs.
While I'm here: the "nothing leaves your phone" architecture is not a marketing line, it's a set of technical choices made in sequence. Card images run through VisionKit, locally. OCR runs through Apple's on-device text recognizer, locally. The AI that extracts merchant and balance runs through Apple Intelligence's Foundation Models (iOS 18+), locally. Sensitive-content detection, for the barcode image, runs through Apple's on-device SCS framework. None of those steps phone home. No card number ever touches a server we run, because there is no server we run. The nearest thing to "the cloud" in Cue is your own iCloud, encrypted end-to-end, between your devices.
If you're a developer and you want to see how this works frame-by-frame, the Privacy Architecture press kit walks through it with specific framework names and iOS version gates.
If you're not a developer, what you need to know is: the app knows about your cards. It does not know about you. When you tell a friend about it, the honest answer to "which account did you sign in with?" is none, it doesn't have accounts, nothing leaves my phone. That's the whole pitch. The friend is usually quiet for a second; the second is the point.
Some product decisions are features. Some are absences. The absence of an account system in Cue is, on any growth-focused dashboard, a liability. I can't email my users. I can't track DAU by cohort. I can't retarget them with a push notification on day 14 we miss you. If someone uninstalls, they're gone. If someone loves it and their phone dies, their cards are gone unless iCloud saved them. There is no Recovery Team.
All of that is a real cost. I paid it on purpose. The alternative, the version of CardCue Pro that has accounts, that hits my backend, that stores your cards in my database, is a version I do not believe, on balance, should exist. Not because someone would definitely misuse that data, but because it wouldn't need to exist in the first place. The product works without it.
The dog-vet portal and the preschool app and the gas station loyalty card all have their reasons. I don't begrudge them. But by the end of the day, I hope you notice: of all the things you used on your phone today, the one that remembered your gift cards was the one that never asked who you were. That's not a mistake.