App Download Page with a QR Code
Getting an app installed from the physical world is a short, fragile sequence: someone sees your poster, scans, lands in the right store, and installs. Every unnecessary step in the middle loses a meaningful share of them.
A download page with a QR code is how you keep that sequence short while still handling the fact that you have at least two stores and one web fallback.
This page covers routing iOS and Android correctly, what the landing page should say, printing the code for the surfaces it will live on, and the honest limits of what you can measure.
Every paid plan starts with a 14-day free trial, with no payment details to start. How the trial works
Two stores, one printed code
You cannot print two codes and expect people to identify their own platform reliably — a lot of people genuinely do not know what to look for, and a poster with two squares invites the wrong choice.
One code, one landing page, and two clearly labelled store buttons is the setup that works and never routes anyone wrongly. It costs one extra tap and it is honest about what is happening.
The alternative is device-based redirection straight into the correct store. It saves the tap, and it fails in the awkward cases — a tablet, a desktop browser, an unusual user agent — so if you use it, always keep a visible fallback for both stores on the page you redirect from.
What the landing page has to say
The page has about five seconds to justify the install. Name what the app does in one line, show one screenshot, and put the two store buttons immediately below. Nothing else above the fold.
The single most useful addition is size and requirement information: how large the download is, and the minimum OS version. A user on mobile data who discovers a 180 MB download after tapping through is a lost install and a bad first impression.
If there is a web version, link it below the store buttons. Some people will never install anything, and giving them a route is better than losing them entirely.
Printing for the surface
Packaging and product inserts are the highest-converting placement, because the person already bought something and is at home with time. Print 2 to 3 cm and caption it with the benefit, not the instruction.
Posters and standees in a venue are read from two or three metres, so 20 to 30 cm. Vehicle livery and billboards are, realistically, not scannable at all — people cannot aim a camera at something they are passing.
Receipts and till-side cards work in a specific case: an app that gives the customer something on their next visit. Without that payoff, a code on a receipt is thrown away with the receipt.
Keep the destination editable
App store URLs change. Apps get renamed, bundle identifiers move, a regional store gets added, an app gets pulled and relaunched. Any of those turns a printed code into a dead end if the code encoded the store URL directly.
Point the printed code at a short link you own instead, and repoint it whenever the store situation changes. Packaging in circulation has a life of years, which is exactly the horizon over which store URLs go stale.
This also lets you run a temporary message — a maintenance notice, a launch delay, a beta signup — without reprinting anything.
Beta and TestFlight distribution
Beta links are the case where an editable destination stops being a nice-to-have. TestFlight links expire, beta cohorts fill up, and Play Console testing tracks change membership.
A stable printed code pointing at a page you control means you can move testers between builds and cohorts without ever reprinting a card. For a hardware product shipping with a beta app, that is the difference between a supported launch and a support queue.
Say clearly on the page that it is a beta, and what that means. Testers who did not realise they were installing pre-release software leave the worst reviews you will ever get.
What you can and cannot measure
You can measure scans, and clicks on each store button. That tells you which placement drives interest and which platform your physical audience carries — both genuinely useful.
You cannot measure installs from the scan itself. Once the user is handed to the App Store or Play Store, attribution belongs to the store's own console or to a mobile-attribution SDK, and a link shortener has no visibility into it.
So compare like with like: scans and store-button clicks against store-console installs over the same period. And use a separate link per placement, or the comparison is meaningless.
Step by step
- 1Build a short download pageOne line describing the app, one screenshot, two labelled store buttons, plus download size and minimum OS version.
- 2Point a short link at itNever encode a store URL directly — store URLs go stale over the life of printed packaging.
- 3Generate a code per placementSeparate links for packaging, poster, receipt and insert, so you can compare them.
- 4Size for the surface2 to 3 cm on packaging and inserts, 20 to 30 cm on posters and standees. Skip vehicles and roadside billboards.
- 5Compare scans with store installsRead scans and store-button clicks from the link, and installs from the store console for the same period.
Frequently asked questions
Is an app download page with a QR code free?
Yes, creating the page and its QR code is free. An editable destination for printed codes and full scan analytics are paid features.
Should I print separate codes for iOS and Android?
No. Print one code to a landing page with two clearly labelled store buttons. Two printed squares invites people to pick the wrong one.
Should the page auto-redirect by device?
You can, and it saves a tap, but it fails on tablets, desktops and unusual user agents. If you do it, always keep visible fallback links to both stores.
Can I change where the code points after printing?
Yes, if it points at a short link you own. Necessary in practice: store URLs change when apps are renamed, relaunched or added to new regional stores.
Can I track installs from the scan?
No. You can track scans and store-button clicks; the install itself is only visible in the store console or through a mobile-attribution SDK. Compare the two over the same period instead.
What is the best placement?
Packaging and product inserts, because the person already bought and is at home with time. Posters work at 20 to 30 cm; vehicles and roadside billboards effectively do not work at all.
Ready to set it up? It's free to start.
Create your free app download page →