A public, prioritized list of what we're building to help you make better micro-money decisions. Send a Card and Family Sharing are already done, a native CarPlay app needs Apple's approval, 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, so a balance change could update the banner without you opening the app.
Status: built, switched off, no date. For now Live Activities are foreground-only: open CardCue Pro near a saved store and the Live Activity follows the card to the register. If you arrive with the app closed, you get a chirp instead. iOS does not let an app start a Live Activity from the background, and push-to-start has not produced one.
Bought a virtual card, or got one emailed straight from the brand (a Home Depot eGift, say)? The plan: open it in Mail, tap Share, pick CardCue Pro, and the share extension reads the brand, code, PIN, balance, and expiry from 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. That is Send a Card, available now.
Status: in test. The share extension is not in the App Store app yet. Until it is, add an emailed card by scanning it, typing it in, dictating it, or opening a .pkpass file.
Tap "Add to Apple Wallet" on a digitized gift card to get a real .pkpass in iOS Wallet, alongside your credit cards. Add to Apple Wallet puts a static copy of the card in Wallet; open Wallet to show it.
Status: being verified on the current App Store build. Until it is confirmed there, we do not list it as available now.
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: for the monthly and yearly Pro subscriptions only.
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 is live. The escrow server and the claim web page are live; sending, claiming, and recall all run from the app.
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 it matters: driving is where the "I just drove past Target" miss happens, the highest-value moment for CardCue Pro. Status: the CarPlay screens are written but not switched on. A native CarPlay app needs Apple's CarPlay entitlement, which Apple grants only by case-by-case review, and CardCue Pro does not hold it yet, so there is no date.
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.
Today a secure cloud AI reads cards by default, and on-device scanning with Apple Vision is the free alternative: one tap away on the camera, and it can be made the default in Settings, with reduced extraction quality on unusual cards. This item is about closing that quality gap.
Why exploring: we tried an Apple Intelligence reader on the device and switched it off after it failed on real cards. We plan to test Apple's on-device models again on iOS 27. No date.
Households have asked for more than handing a card over: nearby alerts that route to whichever family member is closest to the store, and a household view of expiring value. We decided against both: no family alert routing, and no view into anyone else’s cards. Every wallet stays private. To hand a card to someone, use Send a Card.
Status: decided against for v1 and v2 (June 2026).
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.