QR Code to App Store and Google Play: Use One Scan for Both
Build one QR code that sends iPhone users to the App Store, Android users to Google Play, and desktop users to your website without maintaining separate assets.
What this page solves
- One QR code asset for iOS, Android, and desktop traffic
- Cleaner offline campaign execution across posters, packaging, and retail
- Fewer scan failures caused by sending everyone to the wrong store
- Better analytics because every scan passes through one smart routing layer
Why one store QR code is not enough
A QR code that points directly to the App Store works only for iPhone users. A QR code that points directly to Google Play works only for Android users. As soon as you print separate QR assets, operational complexity goes up and campaign consistency goes down.
The better pattern is to let the QR code resolve to one smart URL first. That URL decides where to send the user based on device and context. This keeps creative simple while preserving a platform-specific destination after the scan.
For app growth teams, this matters because offline traffic is already harder to debug than web traffic. Reducing routing mistakes before launch is usually worth more than trying to explain bad install numbers afterward.
Two store codes
Each code knows one store
- App StoreiPhoneAndroid · wrong store
- Google PlayAndroidiPhone · wrong store
Two assets to print, two sets of numbers to merge.
One smart code
The URL decides per device
- iPhoneApp Store
- AndroidGoogle Play
- DesktopWebsite
One asset, and every scan passes through the same routing layer.
How to set it up
Create one smart link instead of two store URLs
Start with a routing URL that sits in front of the App Store and Google Play destinations.
This is the URL your QR code should encode. The QR code should not point directly to a store page unless the campaign is single-platform.
Add your iOS, Android, and website destinations
Configure App Store for iPhone users, Google Play for Android users, and a landing page for everyone else.
The web page covers desktop scans, unsupported environments, and campaign preview links shared internally.
Generate the QR code from the smart link
Once the routing is configured, generate one branded QR code and export it in print-safe formats.
For posters or packaging, prefer SVG or high-resolution PNG so print quality does not hurt scan reliability.
Test on real devices before launch
Scan with at least one recent iPhone, one recent Android device, and one desktop camera workflow if relevant.
Testing only in a browser preview is not enough. You want to confirm final routing behavior, not just that the QR image renders.
Track scans and downstream install signals
Use the same smart link as the measurement layer for channel, placement, and platform reporting.
This is what lets you compare poster placements, packaging variants, and campaign geography later.
Recommended routing behavior
A practical routing matrix keeps the scan experience predictable across environments:
One QR code
Every scan resolves to the same smart URL first, and that URL picks the destination.
- iPhone scanRedirect to App Store or deeplink landing flow
- Android scanRedirect to Google Play or Android app/open flow
- Desktop scanOpen a web page with app badges and campaign context
- Unsupported in-app browserSend people to a page that works there instead of forcing a broken store handoff
Common mistakes
- • Encoding the QR code with a store URL instead of the routing URL
- • Skipping the website destination and leaving desktop users at a dead end
- • Printing before verifying final behavior on both major mobile platforms
- • Using two different QR codes in one campaign and fragmenting analytics
- • Changing the store URL later without preserving the public QR destination
Launch checklist
- • One smart URL created for the campaign
- • App Store destination configured and tested
- • Google Play destination configured and tested
- • Website destination for desktop configured
- • QR code exported in a print-safe format
- • Creative includes a clear call to action near the code
- • Analytics naming convention added for campaign and placement
Related Appy resources
Use these if you want to move from setup to execution quickly.
- Branded QR Code Generator to create the final campaign asset from one routing URL.
- How to Create One Link for App Store and Google Play if you want the smart-link setup behind the QR code.
- Smart link features for routing, website destinations, and campaign analytics.
Continue exploring
How to Create One Link for App Store and Google Play
How one smart link sends iPhones to the App Store, Android phones to Google Play and desktops to your website, how to build it for free in minutes, and what to test before printing it.
One Link for the App Store, Google Play, and Huawei AppGallery
A Google Play link is a dead end on a Huawei phone. Learn how one smart link routes every Android visitor to a store that actually exists on their device.
Instagram & TikTok Deep Links for App Installs: Route to App, Store, or Web
Learn how to route Instagram Stories, profile links, and paid ads plus TikTok bio and ad traffic to deeplinks, app stores, or your website with one smart link.
Looking for something else? Browse all topics on the blog.
Build one QR code for every platform
Use a single smart QR flow for App Store, Google Play, and website traffic instead of maintaining separate offline assets.