A QR code for app downloads is a single scannable code that sends iPhone users to the App Store and Android users to Google Play, decided at the moment of the scan. The trick is that the code does not point at a store. It points at a smart link that reads the device and forwards to the right store, with a web page as the fallback for anyone on a desktop. One printed code, both platforms, no wrong turns.
This is the practical version: why a raw store link fails half your audience, how the device-detecting link works, how to build one, and where to place it. If you are new to codes, how to create a QR code covers the basics first.
The Problem: Two Stores, One Code
Your app lives in two places. iPhone users install from the Apple App Store, Android users from Google Play, and each store has its own URL. A QR code can hold only one address, so if you encode the App Store link, every Android scanner hits a page they cannot use, and the other way around.
Printing two codes, one per store, pushes the choice onto the reader, who now has to know which phone they hold and pick the matching square. Most will not. The result is lost installs at the exact moment someone wanted your app. The fix is to make the code route itself.
How the Device-Detecting Link Works
One short link sits between the code and the stores, and it decides the destination on every scan.
When a phone opens the link, the request carries the operating system. The link reads it and redirects: iOS to the App Store, Android to Google Play, everything else to a fallback web page. The scanner sees none of this, they tap and arrive at the correct store. This is the same routing engine described in smart links explained, applied to app stores instead of countries or languages. Apple documents its App Store marketing links and Google its Play Store linking (both accessed 2026-07-18), and the smart link simply picks the right one per device.
The code itself is not clever. It encodes one link. All the intelligence is in that link, which is why an app-download code has to point at a smart link and never at a bare apps.apple.com or play.google.com URL.
How to Build One
Four steps, and the order matters.
- Collect both store URLs. Your App Store product link and your Google Play listing link. If you ship on other stores, such as AppGallery, keep those too.
- Create the smart link. Set the iOS destination, the Android destination, and the desktop or other fallback. This is one short link with device rules.
- Generate the QR from that smart link. Encode the short link, not a store URL. Keep it dynamic so you can edit the stores and read the scans later.
- Set the fallback deliberately. Send desktop scans to a landing page with both store badges or a send-to-phone option, not to a store they cannot use.
Because the code encodes a short link you control, this is a dynamic code by definition, which matters for the reasons in dynamic vs static QR codes: you can swap a store URL, add a platform, or fix a mistake without reprinting.
If you would rather not wire the routing yourself, Elido's smart links do the device detection and QR codes generate the code over the same short link, so the routing and the scan data live in one place. You can set one up on the free plan.
Land People on the Right Screen, Not Just the Right Store
Getting the store right is half the job. The other half is where the app opens after install.
By default a fresh install lands on a generic home screen, even if the scan came from an ad for one specific feature. A deferred deep link carries that intent through the install so the app opens on the exact screen, which is where campaign installs usually leak users. The mechanics are in what is a deep link and, for the setup without a heavy SDK, deep links without an SDK. For a plain install campaign the store routing is enough; add deferred deep linking when the scan promises a specific destination inside the app.
Where to Put It
An app-download code earns its place anywhere a phone is already in hand and your app is the next step.
Posters and transit ads, product packaging and inserts, event booths and badges, restaurant tables, receipts, business cards, and the end screen of a video all work. The pattern is the same as any print placement: give each surface its own short link so the poster, the packaging, and the booth are separate rows you can compare. Design still matters, so keep the quiet zone, contrast, and a clear call to action like "Scan to get the app", per branded QR code design.
What Does Not Work
Three setups that look fine and lose installs:
Encoding one store URL. A code that holds the App Store link is dead weight for every Android scanner, and the reverse. This is the most common mistake, and a smart link fixes it outright.
No desktop fallback. Scans happen on laptops too, at a desk, off a shared screen. Without a fallback those people hit a mobile store page they cannot install from. Send them to a page that gets the link to their phone.
A static code straight to a store. Even for one platform, encoding the store URL directly means no scan data and a dead code if the listing URL changes. Route through a short link so the code stays editable and measurable.
Get the routing right and one code carries your whole install funnel: scan, correct store, and, when you need it, the exact screen inside the app.
Related on the Blog
Поширені запитання
How do I make a QR code for both the App Store and Google Play?
Point one QR code at a smart link, not at a store URL. Collect your App Store link and your Google Play link, create a smart link that detects the visitor's device and redirects iPhone users to the App Store and Android users to Google Play, then generate the QR code from that single smart link. Set a web fallback for anyone who scans on a desktop. Because the store choice happens at scan time, one printed code serves both platforms.
Can one QR code link to both app stores?
Yes, through a smart link in the middle. A QR code can only encode one address, so you cannot put two store URLs in it directly. Instead you encode a single smart link that reads the device on each scan and forwards to the correct store. The scanner never sees the redirect, they just land in the App Store or Google Play depending on their phone.
How does the code know which store to open?
The smart link behind the code reads the request, including the operating system reported by the phone, and picks the destination. iOS devices go to the App Store, Android devices go to Google Play, and other devices go to a fallback web page you set. The QR code itself is not smart; the short link it points to does the routing, which is why the code has to encode a smart link rather than a plain store URL.
What happens when someone scans the app code on a desktop?
That depends on the fallback you set. A desktop or laptop cannot install a mobile app, so a good smart link sends those scans to a landing page: your website, a page with both store badges, or a send-to-phone form. Without a fallback, a desktop scanner lands on a store page they cannot act on. Always set the desktop destination deliberately rather than leaving it to chance.
Can I track app downloads from a QR code?
You can track scans precisely and installs with extra setup. A dynamic app-download code routes through a redirect, so every scan is logged with time, device, and placement. Counting installs is a separate step that needs the store's own attribution or a measurement partner, because the app stores do not report an install straight back to the QR code. Scan counts alone already tell you which poster or placement is working.
Спробуйте Elido
Вставте URL - отримайте коротке посилання
Без реєстрації. Посилання живе 30 днів. Зареєструйтесь, щоб зберегти назавжди.
Безкоштовно, без реєстрації · 2 на день