One App Download Shortlink for iOS and Android

You have one app and two store URLs — and every bio, SMS, and ad slot only gives you room for one link. An app download shortlink fixes this: a single short URL that detects each visitor's device and routes iPhones to the App Store and Android phones to Google Play. This guide explains why separate store links quietly bleed installs, how device detection actually works in plain language, and how to measure what each platform sends you.

Why separate store links kill conversion

Posting both store URLs feels thorough, but in the places where apps are actually promoted it backfires:

• Social bios — most platforms give you exactly one link field. Two store URLs won't fit, and a link-in-bio page adds an extra tap where a chunk of visitors drop off.
• SMS and messaging — two long store URLs look like spam and eat your character budget. One short, readable link gets tapped.
• Paid ads — one ad, one destination URL. Running separate iOS and Android campaigns just to route people correctly doubles your setup and splits your budget.
• Every wrong-store click — an Android user landing on the App Store sees a "get it on iPhone" page and bounces. That's a motivated installer you paid to lose.

A single smart link removes the decision entirely: everyone taps the same URL, and the server does the sorting. It also keeps your copy clean — one memorable link like opn.my/get-yourapp works in a bio, a text, a podcast read, and a print ad without modification. (For more on making links earn clicks on social platforms, see our shortlink best practices for social media.)

How device detection works, in plain language

The user agent: your browser's name tag

Every time a browser requests a page, it sends a short label called a user agent — a line of text that effectively says "I'm Safari on an iPhone" or "I'm Chrome on Android." Every website you visit already receives it. The shortlink server reads that label and picks the destination: iPhone user agents go to your App Store URL, Android user agents go to Google Play. No app, no permission prompt, no personal data involved.

Why the redirect must be a 302, not a 301

Redirects come in two flavors. A 301 means "moved permanently," and browsers helpfully cache it — the next time you use the link, the browser skips the server and jumps straight to the remembered destination. Great for speed, fatal for device detection: the answer depends on who's asking, so it must never be remembered. A 302 means "temporary — ask me again next time," forcing a fresh decision on every visit. opn.my serves app download links with an uncached 302 for exactly this reason. Our explainer on how URL shorteners work digs deeper into redirect mechanics.

The edge cases worth knowing

Device detection is reliable for phones, but be honest about the edges: iPads running desktop-class browsers can identify themselves as computers, so they may receive the desktop fallback instead of the App Store. A good fallback page shows both store options anyway, so nobody dead-ends. Link scanners and bots also follow links; decent analytics filter those out so your numbers reflect humans.

What should desktop visitors get?

A laptop can't install your mobile app, so you need a deliberate fallback. opn.my lets you choose one of two behaviors per link:

• A hosted download page — a simple page with your link's QR code plus App Store and Google Play badges. The visitor scans the code with their phone and lands in the right store seconds later. This is the safest default because it serves every device, including desktop-mode iPads.
• A straight store redirect — desktop visitors go directly to one store you pick. Useful when your audience is overwhelmingly on one platform or you want people on the store's web page for reviews and screenshots.

One boundary to keep in mind: this is store routing, not deferred deep linking. The link opens the correct store listing; it doesn't carry the visitor to specific content inside your app after install.

Set it up in about a minute

1. Open the app download link generator on the opn.my homepage — the "One link for your app — every store" section.
2. Paste your App Store URL, your Google Play URL, or both (at least one).
3. Pick a custom alias (3–32 characters) so the link reads well out loud, and choose your desktop behavior: download page or direct store redirect.
4. Create the link. You also get a QR code for print and screens — pair the link with the code the way we describe in our app download QR code guide.

You can create 3 links without an account and 10 with a free one, links live up to 90 days with a configurable expiration, and destinations are screened so malicious URLs are blocked. The how-to-use guide covers aliases, QR downloads, and expiration step by step.

Measure installs per platform

Because every tap passes through the shortlink, opn.my's built-in click analytics show total clicks, countries and cities, the device split between iPhone and Android, browsers, and referrers — with bot traffic filtered out. Create a separate link per channel (bio, SMS campaign, ad set) and you get a per-channel, per-platform picture of where installers come from. Compare those click counts against installs in App Store Connect and the Play Console to estimate store-page conversion for each platform. That's the quiet superpower of an app download shortlink: it doesn't just route people correctly, it tells you which of your channels is actually filling the funnel.