A public, prioritized list of what we're building to help you make better micro-money decisions. Send a Card, Add to Apple Wallet, and Family Sharing are already done, CarPlay is up next, and the rest is queued or on the horizon. Ships when it's ready, not before. Updated whenever something moves.
Server-side push for the lock-screen and Dynamic Island banner. Balance updates land on the banner within seconds even when Cue is suspended in the background, before this, the banner froze the moment iOS suspended the app and only refreshed if you re-foregrounded.
Why now: promoted to v1 from v2 after the freeze became the most-noticed lock-screen rough edge in real-device use. APNs token-based push, Postgres trigger via pg_net, automatic sandbox/production routing per token.
One subscription through Apple Family Sharing, and everyone in your family gets the full Pro app with their own private wallet. There is no shared household wallet, no merged balances, and nobody can see anyone else's cards. Want to hand a card to a family member? That's what Send a Card is for.
Why this shape: wallets are personal. Sharing a subscription should not mean sharing your PINs, balances, or spending habits with the whole house. Status: enabled on the Pro subscription and ships with v1.0.
Pick a card, add a note, and send it by text, email, or AirDrop. The card leaves your wallet the moment you send it, waits safely in encrypted escrow for 14 days, and the first person to open the link claims it, so send it only through a channel you trust. You can recall it any time before it is claimed. If your friend doesn't have the app yet, the link shows them the card waiting and walks them through the download. Free for everyone. And it pays both ways: your friend gets a free month of Pro when they claim their first card, and you earn one for every new friend you bring in, up to six. See Send a card, get a month.
Status: Send a Card ships in v1. The escrow server and the claim web page are live; sending, claiming, and recall all run from the app.
Bought a virtual card, or got one emailed straight from the brand (a Home Depot eGift, say)? Open it in Mail, tap Share, pick CardCue Pro. The share extension reads the brand, code, PIN, balance, and expiry right out of the email and pre-fills a wallet entry for you.
Not to be confused with receiving a card from another CardCue Pro user: that arrives by text or email as a gift link, one tap to claim, and it ships in v1.0 with Send a Card.
The share extension is built and shipping, so you can pull eGift emails into your wallet today.
Tap "Add to Apple Wallet" on any digitized gift card and get a real .pkpass in iOS Wallet, alongside your credit cards. The pass embeds up to 10 store coordinates, so iOS surfaces it on the lock screen automatically when you're nearby, zero custom geofencing needed.
Shipped in v1: it was the most-requested feature from beta, and the pass-signing service is deployed and live.
A native CarPlay app for nearby cards while you're driving. List the stores you're approaching, with balances and distances. Tap a row to hand off the barcode to a passenger’s phone or get directions in the in-car display.
Why next: drivers are the highest-value moment for CardCue Pro, the "I just drove past Target" miss most often happens at 35 mph. Apple grants the CarPlay entitlement by case-by-case review, so timing is dependent on Apple's response window.
One important distinction. "CarPlay support" on this roadmap means a dedicated app icon on the CarPlay home screen, the kind that has its own list and detail templates inside the in-car display. That requires Apple's CarPlay entitlement, which is granted only by case-by-case written request.
It does not refer to the notification rail on CarPlay screens, which is a system surface that mirrors any iPhone notification automatically. CardCue Pro’s nearby-card alerts already appear in the CarPlay notification rail today, that’s an iOS feature, not an entitlement, and ships out of the box wherever your iPhone is paired with a CarPlay head unit.
Sign-in choices beyond Sign in with Apple. Same Supabase-backed account model on the back end, once a session exists, the rest of the app doesn’t care which identity provider minted it.
Why on deck: Sign in with Apple covers ~95% of our audience (iPhone owners). Adding Google + Facebook is purely additive for cross-device + future web-client users.
Generate a one-of-one stylized illustration for any card using Apple Intelligence + Image Playground. The output replaces the card’s default gradient on the wallet tile.
Why on deck: the underlying iOS API is still rolling out per-region (EU, China lagging). We pulled it from v1 to avoid showing the button to users who can’t actually use it.
Tap a gift link on a phone that doesn’t have CardCue Pro and an App Clip opens instantly: see the card, claim it on the spot, and the full app picks the card up the moment you install. No App Store detour standing between your friend and their gift.
Why on deck: the v1 claim flow (web page + install + tap the link again) works end to end; the App Clip removes its one rough edge. Pushed out of the v1 launch to keep the review surface small.
Things households keep asking about that go further than handing a card over: opt-in nearby alerts that route to whichever family member is closest to the store, and a household view of expiring value. Every idea here stays opt-in per person; nobody’s wallet is ever visible by default.
Design questions: what's genuinely useful vs. surveillance-adjacent, conflict resolution when two people redeem the same card idea, and whether any of it earns its complexity.
On our roadmap, targeted mid-2027: card reading that runs entirely on your device, with the same extraction quality you get today, no server round trip at all.
Why exploring: today the scanner reads cards with cloud AI by default (a "Scan on-device only" toggle already lives in Settings, with reduced extraction quality). This item is about closing that quality gap so on-device becomes the whole story.
Items move up when the work is starting, graduate to Available now when they ship, and drop off the list once the rest of the site documents them. We don’t list internal infrastructure work, bug fixes, or polish, just user-facing capabilities.
If something here is the reason you haven’t upgraded yet, let us know. We weight the queue by user demand, not by what’s easiest to build.