Last updated
April 27 2024
FAQs
How do I add my cards to Apple Wallet?
If you have Barcodes Unlimited, you can add any card that has the format set to Aztec, Code 128, PDF417 or QR. These are fully supported by Apple Wallet on iPhone, and are fully supported except for Code 128 on Apple Watch. You do so by going to Edit mode for the card and toggling this option on.
Deleting cards from Apple Wallet
When you delete a card in app it is also removed from Apple Wallet, but you can manually remove the card from within the Wallet app too.
How can I get my Apple Wallet passes to show on my Lock Screen when nearby?
You can edit a card to add up to 10 relevant locations to the Apple Wallet pass, and the distance to display at up to the maximum allowed by Apple Wallet. Then when nearby the pass will conveniently show up on your Lock Screen!
Does Barcodes have access to my location?
No, but Siri does. Barcodes tells Siri when you take actions in the app, and if Siri notices a pattern it can automatically surface these actions in the app. That's why you might notice that Siri may suggest Barcodes after you have been using it regularly to scan into your gym or at your local checkout!
Why does the app require payment for full functionality?
Barcodes does not sell your user data, so sustainable development requires in-app purchases in order to fund sustainable development. You can choose to use Barcodes for free with limitations, or upgrade to Barcodes Unlimited for full feature access with a monthly or once off payment as suits you best.
How can I make a suggestion?
Email me at barcodes@smallcolossus.com I would love to hear it!
Apple Wallet pass types
Pass type | Relevant date | Relevant locations | Apple Watch support | Grouping |
---|---|---|---|---|
Generic | Yes | Max 10 locations, small activation radius (maximum approx. 100m / 328ft) |
Aztec, PDF417 or QR | Grouped |
Event ticket | Yes | Max 10 locations, large activation radius (maximum approx. 1000m / 3280 ft) |
Aztec, PDF417 or QR experimental support for others* |
Separate |
Boarding pass | Yes | Max 10 locations, large activation radius (maximum approx. 1000m / 3280 ft) |
Aztec, PDF417 or QR | Separate |
Store card | No | Max 10 locations, small activation radius (maximum approx. 100m / 328ft) |
Aztec, PDF417 or QR experimental support for others* |
Grouped |
Coupon | No | Max 10 locations, small activation radius (maximum approx. 100m / 328ft) |
Aztec, PDF417 or QR experimental support for others* |
Grouped |
*experimental support involves trying to write a strip image containing the barcode, which is then shown instead
Apple Watch support on Apple Wallet
Apple Watch supports Aztec, PDF417 or QR natively. If your bacode is a different type and you use a compatible card type, then an image of the barcode is added to the card. This is a workaround, and imperfect. Barcodes is also available for Apple Watch and is recommended instead of Apple Wallet passes for this instance.
Grouping
If you select event or boarding type for your cards, they will not be grouped and appear below each other in Apple Wallet. If you use a different type of card, then they will be grouped next to each other. The event and boarding card types have a different appearance, so there are tradeoffs if you don't want the cards grouped together.
Apple Wallet Notes
These limitations mentioned above all arise from Apple's implementation and design of Apple Wallet, and Barcodes can't change them.
Relevant date and locations
If you supply relevant locations, your iPhone can use this to show the passes when you are nearby. The distance is at most the distance shown for the type, but can be reduced in the app for closer distances. It is not possible to extend it further. If a card type supports a relevant date and both a date and a location are provided, the card will only show up when the date and the location are a match.
More information on layout and pass design here from Apple, including pass shapes.
Anything else?
Please feel free to contact me at barcodes@smallcolossus.com with any feedback, suggestions or queries at all!