Driving app installs from a desktop website

Someone finds your site on a laptop. They read about your product. They want it. Your product is a phone app.

That gap is where a lot of intent quietly dies.

Why it is genuinely hard

The visitor cannot complete the action on the device they are using. Anything you do has to move them to a different device without losing them in the transition — and every transition step is an opportunity to abandon.

The failure mode is not that people refuse. It is that they intend to do it later, and later never arrives.

The options, ranked

QR code — best. The visitor holds up their phone, scans, and lands on the store. One action, no typing, no data handed over, no context switch. Modern phone cameras scan natively without an app.

Send by SMS — works, costs more than it looks. You collect a phone number, text a link, they tap it. Effective, but you are asking for personal data before delivering value, adding a privacy consideration, and taking on SMS infrastructure and cost.

Send by email — weak. Requires the visitor to leave your site, open email, find the message, and tap through. Every one of those steps sheds people, and the email often arrives when they have moved on entirely.

"Search for us in the App Store" — worst. Requires them to remember your name later and get the spelling right. Also drops them into search results alongside competitors.

The ranking is essentially by number of steps and how much you ask of the visitor. QR wins because it is one action and asks for nothing.

Making the QR handoff work

Put it where the intent is. Not buried in the footer. Next to the primary call to action, where someone has just decided they want the thing.

Say what it does. "Scan to download the app" beats an unlabelled code by a wide margin. An unexplained QR is a request for blind trust.

Make it big enough. Roughly one tenth of the scanning distance. For a laptop screen at arm's length, 150–200px is a reasonable floor. Smaller codes fail more often than people expect.

Only show it on desktop. A QR code on a phone is absurd — the visitor cannot scan their own screen. Detect the device and show a direct install button on mobile instead.

Point it at a routing link. The person scanning could be on iOS or Android. The QR must route by device, or half of them land in the wrong store.

Do not waste the fallback page

If someone opens your install link on desktop, they will land on your web fallback. That page is doing real work and deserves attention.

A good desktop fallback:

• Acknowledges they are on desktop rather than pretending otherwise
• Shows a QR code prominently
• Explains what the app does, since they may be encountering it fresh
• Offers something they *can* do now — a web version, a signup, a newsletter

A bad one shows a store page they cannot act on, or an error.

Measuring the handoff

The desktop-to-mobile transition is measurable if the QR encodes a link you control: how many people scanned, from which page, at what time.

The useful ratio is desktop visitors to scans. If it is low, the problem is almost always placement or labelling, not the mechanism. Move the code closer to the call to action and say what it does.

A pattern worth stealing

For products where a web version exists alongside the app, the strongest desktop pattern is usually:

1. Let them start on the web immediately — no install required
2. Once they have real value in the product, offer the app for mobile
3. Use a QR code for that handoff

This inverts the usual order. Instead of asking for an install before any value has been delivered, you deliver value first and let the app be the natural next step. Conversion on that second ask is far higher, because it is no longer a leap of faith.

How Bridgly fits

Bridgly links come with QR codes generated from the same routing URL, plus an embeddable QR widget you can drop onto a website — which is exactly the desktop-to-mobile handoff described here.

The widget renders server-side and is configurable, and scans are tracked alongside clicks, so the handoff appears in the same analytics as every other channel.

Web fallbacks are configured per link, so desktop visitors reaching an install link get a real page rather than a dead end.

Start free · Read: QR codes for app downloads

The short version

• Desktop visitors cannot install; your job is to move them to their phone.
• QR is the best handoff — one action, no typing, no data collected.
• Place it beside the CTA, label it, size it properly, show it only on desktop.
• Point the QR at a routing link so both platforms work.
• Treat the desktop fallback page as a real surface, not an error page.