QR codes to the App Store

The one distribution channel where store links behave exactly as documented, because the camera hands the URL straight to the system.

6 August 2026 by PAD team

Why QR codes work

When the camera scans a code, iOS opens the URL in the default browser, not in some app's WebView. Apple's redirect into itms-appss:// resolves normally and the App Store opens. There is nothing to work around.

This is worth knowing precisely because it makes the in-app browser problem invisible during testing: a team that validates its links with a QR code sees everything work perfectly.

One code, both stores

Do not print two codes. Point one code at a URL that detects the platform and forwards to the App Store, Google Play or your website. The visitor scans, the routing happens in a real browser, and the right store opens.

What still goes wrong

• Encoding a store URL that only works for one platform, stranding half the scans
• Codes too small or too low-contrast for the distance they are viewed at
• No text under the code telling people what they get, which halves scan rates
• Dynamic codes on a service that expires, turning printed material into litter

The last one is the expensive mistake. If the code is going on packaging or a poster with a two-year life, the destination has to be a URL you control.

Attribution from print

Put a campaign token on the destination and print offline sources become measurable. ct=poster_berlin in App Store Connect tells you which placement worked, which is more than most offline advertising ever knows.

Size and testing

Test scanning at the actual distance and lighting the code will live in, not on your monitor. A code that scans from 20cm on a bright screen may fail from two metres on matte paper in a shop.