Your designer sends over a QR code for an upcoming app launch.

Someone scans it on an iPhone. The App Store opens. Looks good.

But what happens on Android? What does a laptop visitor see? And if someone changes the destination after the artwork has gone to print, will the same QR code still work?

A QR code that scans successfully isn't necessarily ready to print. Once it's on 2,000 flyers, correcting a mistake becomes a lot less convenient.

QR is only the beginning

Let's say your app is available in the App Store and on Google Play. You could print two QR codes, but then you're asking people to figure out which one they need before they even reach the app.

Another option is a single public URL with device-aware routing. The QR code contains that URL; the routing service decides where to send the request.

For example, a link like https://go.example.com/get-app could route iPhone visitors to an App Store listing, Android visitors to Google Play, and desktop visitors to an app website. You need to configure the desktop fallback; it shouldn't be assumed.

This doesn't detect whether an app is installed, open a particular in-app screen, or measure actual installations. It's a simpler job: get a visitor to the intended download destination.

What I'd check before printing

I'd spend less time comparing QR generator designs and more time following the actual link on the devices people will use.

First, open both store destinations directly. Make sure they lead to the right app—not an outdated listing, an unrelated app with a similar name, or an unavailable store page.

Then scan the final QR code and follow the full journey:

Test What I want to see
iPhone, Safari Correct App Store listing
Android, Chrome Correct Google Play listing
Desktop browser Intended website or fallback
iPhone Camera Correct destination after scanning
Android QR scanner Correct destination after scanning
Relevant in-app browser Acceptable behavior in that channel

That last row is easy to miss. If your campaign mainly runs in Instagram, email, or a messaging app, check it there too. A link behaving correctly in Safari doesn't establish what will happen in every embedded browser.

And don't overlook region availability. A valid App Store URL isn't proof that the app can be downloaded in every market.

One detail from working on an app-routing product

While working on a mobile app-routing product, we distinguished between inspecting the configured destinations and testing the live redirect.

A preview can show which iOS, Android, and web URLs are saved, without triggering the redirect or recording another visit. That's useful for checking setup.

But a configuration preview cannot prove the end-to-end journey. It won't tell you whether a particular mobile browser or QR scanner reaches the correct store listing.

I think of these as two different tests: Is the link configured correctly? And does it work correctly for the visitor?

Both matter before printing something you can't easily change.

Try changing a destination without replacing the QR

Here's the check I'd do before relying on an editable link for printed material:

  1. Create a test public URL with destinations you control.
  2. Generate and save a QR code for that URL.
  3. Scan it on iPhone and Android.
  4. Change one destination behind the same public URL.
  5. Scan the original QR code again. If you're using an editable managed URL, the printed QR should still contain the same URL while the service uses the updated destination.

If you encoded a direct App Store listing instead, changing that listing's URL won't magically update the printed code. It's an easy difference to miss until a campaign is already out in the world.

Use a test link rather than experimenting on a live campaign.

Don't forget the physical print

A QR image that looks fine on a large monitor may be hard to scan on a small sticker or a glossy poster.

Print a proof at the actual size. Check the contrast and the blank space around the code. Try it at the distance people will stand from it, in roughly the lighting they will have.

I'd also scan the proof with both iPhone and Android. A laptop preview is not a substitute for testing the printed thing.

And please don't call clicks installs

If a link reports 200 clicks, it reports 200 recorded clicks under that service's counting rules. That isn't the same as 200 app installs—or even proof that every visitor successfully reached the store.

If you're trying to measure installs, you'll need separate measurement and an appropriate attribution setup. For a basic QR distribution campaign, first make sure the link takes people where you intended.

The five-minute release check

Before the artwork goes to print, I'd want answers to these questions:

  • Are the iOS and Android store listings correct and accessible where the campaign will run?
  • Does the shared URL work on actual iPhone and Android devices?
  • What happens on desktop or when a platform destination is missing?
  • Does a physical proof of the final QR artwork scan reliably?
  • If destinations are editable, does the same QR survive a destination change?
  • Are we reporting clicks separately from installs?

It's not complicated testing. It's just a lot cheaper to do it before the flyers arrive.