Turn a poster into installs without printing two codes
One QR code can send every scanner to the right app store: iPhones to the App Store, Android to Google Play, from a single square on your poster or packaging. The visitor scans, lands on their store's install page and taps 'Get' — no typing a name into search and picking a wrong result.
The mistake that wastes install codes is hard-coding one store link. Point the code at the App Store and every Android scanner hits a dead page; do the reverse and iPhones are stranded. The code has to route by device, pointing at a page that reads the phone and forwards it, not a baked-in store URL.
Fill the form to generate a QR code
Why one code beats two store codes
Printing two codes labelled 'iPhone' and 'Android' works, but it doubles the space, splits attention and invites people to scan the wrong one. A single smart-routing code is cleaner and converts better, because the visitor never has to know or choose which store they're on — the page behind the code checks the device and forwards it.
That routing page is something you host and control. Encode a short link you own that redirects by user-agent, so if a store URL changes or you add a third platform later, you update the page rather than reprinting everything already in the wild.
- iOS user-agent forwards to the App Store listing.
- Android forwards to the Google Play listing.
- Anything else lands on a plain web fallback or landing page.
Where installs actually come from
Install codes earn their keep on things a phone can't tap directly: posters, packaging, event banners, table talkers, the back of a receipt. A code on a website is pointless because the visitor is already on a device that could just tap a button. Put the code where the app is being talked about but the phone can't reach the link any other way — that's the gap it fills.
Give it a one-line reason to scan next to the code. 'Scan to install' plus a single benefit beats a bare square, because you're asking someone to commit storage and a download, not just open a page.
Size, contrast and the fallback
Match the size to the scan distance: a code on packaging held in the hand can be 2 cm, one on a wall poster read from two metres needs to be far bigger. Keep strong dark-on-light contrast and a clean margin. Always give the routing page a web fallback too, so a desktop scan or an unusual device lands on a real page instead of a broken store link.
How to make a one-code install link
- Set up a routing page you host. Create a page that reads the visitor's device and forwards iOS to the App Store and Android to Google Play, with a web fallback for everything else.
- Wrap it in a short link you own. Encode that short link, not a store URL. The mistake is baking in one store, which strands every user on the other platform.
- Add a reason to scan. Put 'Scan to install' and one clear benefit beside the code, since you're asking for a download, not just a page view.
- Size it to the surface and test both phones. Scale the code to its scan distance, then test with a real iPhone and a real Android to confirm each lands on the correct store.
Technical details
- Maximum characters: 2953
- Recommended error correction: Q (quartile) — install codes live on posters and packaging that get handled and creased, so higher recovery keeps a scuffed code scanning.
- The code carries a URL to a routing page you host; the device detection and store forwarding happen on that page, not inside the code.
- Always host a web fallback so desktop or unusual-device scans reach a real page instead of a broken store link.
Frequently asked questions
- Can one QR code work for both the App Store and Google Play?
- Yes. Point the code at a routing page you host that reads the device and forwards iPhones to the App Store and Android phones to Google Play. The single code handles both because the choice happens on the page, not in the code.
- What happens if I encode the App Store link directly?
- Every Android user hits a dead or wrong page and won't install. A hard-coded store URL only serves one platform. Use a device-routing link instead so each scanner reaches their own store, and add a web fallback for desktops and unusual devices.
- Where does an app download code actually belong?
- On surfaces a phone can't tap: posters, packaging, banners, event stands, receipts. On a website it's pointless, since the visitor is already on a device that could tap an install button directly. The code fills the gap where the link is otherwise unreachable, which is the whole reason to print one.
- Can I update the store links after printing the code?
- Yes, if the code points at a short link you control. Change the routing page and every printed code follows, so a moved listing or a new platform doesn't force a reprint of posters and packaging already out there. You edit the page you host, not the square in the wild.
- How do I stop people scanning and not installing?
- Give them a reason right next to the code. A bare square asks for a download with no motivation, so pair it with 'Scan to install' and one concrete benefit. You're asking for storage and time, so the payoff needs to be visible before they scan.
- Does the download start straight from the scan?
- No. The scan opens the store listing; the person still taps 'Get' or 'Install' and confirms. Nothing downloads to their phone automatically, which is the behaviour they expect and the only way the stores allow it to work. The code gets them to the listing, not past the install button.