One Link, Different Destinations by Device: How It Works

If you have shipped an app on both stores and still run a website that converts, you know the bind: your Instagram bio, your email signature, and your podcast outro each give you exactly one link slot, and your audience is holding three different devices. Send everyone to the website and you bury the app behind an extra tap. Send everyone to the App Store and every Android visitor dies on an Apple page. This guide shows you how to fix it with one short link that reads the device and routes accordingly: iPhone to the App Store, Android to Google Play, desktop to your site.

The three destination problem

Pick any single destination and you sacrifice the other two audiences:

• Link to the App Store and Android users land on a page their phone cannot install from; few will go hunting for the Play listing themselves.
• Link to Google Play and you get the mirror image: every iPhone tap is wasted.
• Link to the website and mobile users get a landing page with a "Download on the App Store" badge: one more tap, one more page load, one more chance to bounce before the install.

What device based routing actually is

Device routing (also called device targeting or a device redirect) is a rule attached to the link itself. When someone opens the link, the server checks what kind of device made the request and forwards it to the URL you assigned for that device, falling back to a default destination for everyone else. It is the classic example of a smart link: one stable address, conditional behavior behind it. This article is a deep dive on that single feature; if you want the broad market tour instead, our roundup of the best URL shorteners covers the whole field.

No magic here, and nothing to install on the visitor side. Every HTTP request a browser makes carries a user agent string that announces the operating system: an iPhone identifies itself as iOS, a Pixel as Android, a laptop as Windows or macOS. Device routing is simply a server side redirect that reads that string before answering.

The user agent handshake

Here is the full journey of a single tap, start to finish:

1. A visitor taps your short link, for example flyn.to/getapp.
2. The request hits the short domain with the visitor's user agent attached.
3. The server checks your rules in order: is this iOS? Is this Android?
4. On a match, it answers with a 302 redirect to the URL you set for that system.
5. No match means the visitor goes to your default destination, which is where desktop traffic lands.

Because the decision happens on the server, it adds only milliseconds, needs no JavaScript, and works inside in-app browsers. The click is recorded either way: click counts are free on every Flyn plan, and the per device breakdown of those clicks is part of Pro click analytics.

Rule order and the fallback

Treat the fallback as a first class citizen, not an afterthought. Desktop browsers, tablets in desktop mode, smart TVs, game consoles, and unknown user agents all land there. The cleanest mental model: your default destination is your desktop URL, and the iOS and Android fields are exceptions layered on top. The same fields exist in the API (the deep links documentation covers the request shape), and Flyn files the whole capability under smart routing.

The whole setup takes about two minutes once you have your URLs. Device routing is part of Flyn Pro ($9 per month billed annually, $12 monthly), and you can build the link on the free plan first, then flip routing on when you upgrade.

Collect your three URLs first

• App Store URL: the canonical https://apps.apple.com/... address of your listing. The free App Store link generator builds a clean one from your app ID.
• Google Play URL: the https://play.google.com/store/apps/details?id=... address with your package name.
• Website URL: the page desktop visitors should see, which doubles as the fallback for everything else.

If all you need is a tidy standalone store link with click tracking, the App Store link shortener and Google Play link shortener pages handle that simpler job.

The walkthrough

1. Create or edit a link. Paste your website URL as the main destination; desktop visitors and unmatched devices will get it. (Sign up free if you have not.)
2. Open the Routing tab in the link editor.
3. Paste the App Store URL into the iOS field. The placeholder shows the expected apps.apple.com shape.
4. Paste the Play URL into the Android field.
5. Leave desktop alone. The editor says it plainly: Desktop uses the default destination. Your main URL already is the desktop field.
6. Save and test on a real iPhone, a real Android phone, and a laptop before you post anywhere.

Edit destinations later without touching the link

Destination editing works on every Flyn plan, and it applies to the routing fields too. Ship a new Android package, rebrand the app, or move the desktop landing page, then update the field: the short URL you already posted, and every QR built on it, keeps working unchanged.

Here is the part most people miss: a QR code is just a link rendered as pixels. If the link underneath routes by device, the printed code inherits that behavior forever. Scan the same poster with an iPhone and you land in the App Store; scan it with a Galaxy and you land in Google Play.

Why routing lives in the link, not the image

Generic generators that encode your App Store URL directly into the pixels freeze that decision permanently: an Android scan hits an Apple page and the poster is misprinted forever. The fix is to encode the short link instead and let the redirect decide at scan time. Flyn gives every link a standard green QR free, with custom colors on Pro; the free QR code generator and the QR codes feature page cover the basics.

Dynamic QR for anything printed

For print runs, pair device routing with a dynamic QR code, meaning a code whose destination you can change after printing. The combination shines on:

• Product packaging: one code sends each buyer to the right store listing for a companion app.
• Posters and flyers: an event app promo that never strands the wrong platform.
• Conference booths: visitors scan one code; you edit the destination the night before launch.
• Menus and receipts: loyalty app installs from either phone, same sticker.

Device routing answers "which storefront." Deep links answer a different one: "which screen inside an app." The same Routing tab carries an Open in native app toggle that, on mobile, opens supported destinations directly in the installed app instead of the browser: YouTube, Instagram, Twitter/X, LinkedIn, TikTok, Spotify and more, 16 platforms in all. Like the device fields, deep links are part of the Pro plan.

Store page or in app content

Use the two tools for what they are:

• Device routing to store URLs is for installs: send people who do not have your app to the correct store.
• Deep links are for content: send people who already have an app (yours or a platform's) straight to a video, a profile, or a product screen without a browser detour.

Build and test the URI before you ship

App URI schemes are fussy, and a wrong one fails silently to the browser. Build yours with the free deep link generator, then open it on a physical phone with the deep link tester before it goes in a campaign. Developers automating link creation should start at the deep links API docs.

One honesty note so you pick the right category of tool: Flyn routes the click perfectly up to the store handoff, but it does not do deferred deep linking (carrying content context through an app install) or install attribution. If you need those, you need an app centric platform like Branch or AppsFlyer OneLink, with the SDK work and pricing that category implies.

Shopping for this feature is confusing because two very different products share the name, and their prices differ by an order of magnitude.

App platforms vs rule based redirects

• App deep linking platforms (Branch, AppsFlyer OneLink, Bitly Mobile Deep Links) route users into your own registered app or its store listing. They require app registration or an SDK, and they are priced for app companies: Branch publishes no dollar pricing at all and gates real usage behind a demo, while Bitly's comparison table puts Mobile Deep Links on its Premium plan at $199 per month, annual only, with deep link reporting reserved for Enterprise.
• Rule based device redirects on a shortener (Flyn, Linkly, Geniuslink, Short.io) let you set any URL per device with no app and no SDK, priced for marketers.

You do not need an attribution SDK to send an Android tap to the Play Store. You need one rule on one link.

The price to unlock

All figures below come from each vendor's public pricing page as checked on Jul 31, 2026:

Switchy deserves a special caution: its deep link toggle only works when the destination app is on its supported list, so it is not a general purpose device router. We scored all of these head to head in our best link shorteners for device routing comparison.

Once the link exists, it upgrades every channel that only gives you one slot:

• The bio link. Your Instagram or TikTok bio is the canonical one slot surface; a device routed link makes the "download my app" line work for every follower.
• Email signatures and newsletters. One button, correct store per reader, website for the colleagues opening on a desktop client.
• Print and packaging. As covered above: one QR, every scan routed, destination editable after the print run.
• Podcast and video reads. You can only say one URL out loud. Make it a short, memorable slug that does the platform sorting silently.
• Paid social. One ad, one link, no duplicated campaigns per platform just to change the destination URL.

Measure the split you actually get

Every one of those channels now reports into a single link, which makes the analytics interesting. Click counts are free on every plan; the Pro analytics breakdown shows what share of your clicks came from iOS, Android, or desktop, which tells you where to spend next. If you want to go further and split traffic within a device bucket, Pro also includes A/B testing that rotates a link between two destinations.

Device routing fails quietly, so read these before the link goes anywhere public.

The iPad wrinkle

Safari on iPadOS requests desktop websites by default, which means many iPads present a Mac like user agent. Those visitors follow your default destination, not your iOS rule. Do not fight it, plan for it: keep a clear App Store badge on the desktop page so a misrouted iPad is one tap from the store.

The test matrix

Five checks, five minutes, before the link ships:

• Tap the link in Safari on a real iPhone: it should open your App Store listing.
• Tap it in Chrome on a real Android phone: Play listing.
• Open it in a laptop browser: website.
• Tap it inside the in-app browser of the platform where you will post it.
• Scan the QR with both phone cameras, since scans follow the same rules.

If you enabled the native app toggle, run the destination through the deep link tester as a sixth check.

The one link slot in your bio, signature, or poster does not have to pick a favorite platform. A device routed short link sends iPhone users to the App Store, Android users to Google Play, and desktop visitors to your website, and because the routing lives in the redirect, the same link works spoken, pasted, or printed as a QR code. Setup is two fields and a fallback in Flyn's Routing tab, and every destination stays editable after the link is in the wild.

If you landed here because Google shut down Firebase Dynamic Links in August 2025, the migration path is in our Firebase Dynamic Links alternative guide. Otherwise the path is short: create a free account (25 new links a month), build the link, and unlock the Routing tab with Pro at $9 per month billed annually. Your next launch deserves one link that gets everyone to the right place.