App launches
One download link for iOS and Android: a launch checklist
Prepare one app-download URL, choose a desktop fallback, and check each device and QR code with a reusable launch worksheet.
A single app-download link can send iPhone visitors to your App Store listing, Android visitors to Google Play, and desktop visitors to a website. Before you share it, check the destination for each audience and the fallback when a device is not recognized. The address alone does not tell you whether the journey works.
This checklist is for a store-download launch. Opening a particular screen inside an installed app is a separate deep-linking setup. You do not need that setup just to route visitors to your store listings.
1. Collect your destinations before making the link
Put three final URLs in your launch document: the public App Store listing, the public Google Play listing, and a useful website page. Open each one yourself. A draft store listing, a dashboard URL or a page requiring your login will not help a new visitor.
Use the website to explain what the app does and show its download options. It is also a deliberate fallback for people whose device cannot be identified. If your app is only available in selected store regions, include that information there; device routing does not change someone's store availability.
For an illustrative app called Acme, the plan might be: iPhone → Acme's App Store listing, Android → Acme's Google Play listing, desktop and unknown devices → https://example.com/acme. This is a planning example, not a tested live app or a claim that a particular URX slug is available.
2. Create the link and inspect each preview
- Create your account, then name your workspace. A workspace is the place for your team's projects and billing.
- In Your app, add a project name and Website. Expand iOS app for the App Store link and Android app for the Google Play link. Fill both store URLs when the app is available on both platforms.
- In Your link, choose an available slug. Use a stable product or campaign name that will still make sense when your next app version ships.
- In Preview, select iPhone & iPad, Android and Desktop. Inspect the full destination, then use the Create button to save the link.
- Open the saved link's destinations and confirm the fallback for everyone else. Previewing a device is useful configuration feedback; it does not replace opening the real URL on that device.
The destination reference explains project defaults and per-link overrides. If you reuse a project's destinations across several links, remember that changing the project can affect those links together.
3. Work through the launch checklist
Copy the table into your launch document. Replace every blank with evidence from your own link. Record the public URL, expected destination, actual result, device/browser, checked date and person responsible for each row. Keep internal test visits separate when you later review launch traffic.
| Surface / device | Expected result | Actual result and evidence |
|---|---|---|
| iPhone · normal browser | Correct App Store listing; app name and publisher match. | Not tested: add URL, browser, date and owner. |
| Android · normal browser | Correct Google Play listing; app and package match. | Not tested: add URL, browser, date and owner. |
| Desktop | Website page with a clear next step and download options. | Not tested: add final URL and page result. |
| iPad · default and desktop browsing | Record the destination you expect in each mode and compare the actual result. | Not tested: record mode and browser explicitly. |
| Social or email placement | The exact link opens from the app or email where it will be shared. | Not tested: record app, URL and any extra step. |
| Printed QR · iPhone and Android | Code scans and reaches the intended destination. | Not tested: record print size, phone and result. |
| Fallback / unknown device | A usable website or configured choice page. | Not tested: record configured fallback and available test evidence. |
Start with the browsers and sharing surfaces your launch actually uses. When a result differs, save the link you tapped and where you landed before changing a setting. Recheck the affected row after each correction. A simulated visitor cannot establish how a particular in-app browser or physical iPad behaves.
4. Check the QR code after it enters the artwork
Download the link's PNG or SVG from its QR tab. The URX QR code contains the redirect address, so you can change the destination behind it later. It does not contain a promise that the address will remain active regardless of account or link status.
Test the final exported artwork and a physical proof at the intended size. Keep the clear border around the code, use strong contrast, and avoid placing it over a busy image. Check with both phone platforms. A scan of the original SVG on your laptop is a different test from a scan of the finished poster.
For material already printed, change a destination on the existing link rather than deleting the link and creating a new address. After the edit has propagated, scan the same proof again and record the new result.
5. Separate clicks, scans and outcomes
Give each placement a name in your worksheet: launch email, Instagram bio or event poster, for example. If you need separate reporting, use distinct links or a consistent campaign-parameter plan supported by your account. Preserve that mapping when you change destinations.
A counted click tells you the link received a visit. A QR scan is a type of click. Neither proves an app installation, signup or purchase. Report those outcomes only when an appropriate app, store or conversion integration supplies them. See analytics and conversion events for the separate measures.
6. Give the link an owner after launch
Record who checks store URLs after a rename, publisher transfer or availability change. Keep the worksheet with the campaign assets so the person updating a poster can find the original public address and the last successful checks.
URX Free currently includes 25 links, 2 projects and 1,500 monthly clicks, with editable destinations and QR downloads. Above its monthly click allowance, Free visits first see a forwarding page. Free links inactive for six months are switched off after reminders and have a 90-day reactivation window. Review the current plans and inactivity policy before relying on a printed link for a long-running campaign.
Store routing is available on Free. URI-scheme and deferred deep links require Pro; native Universal Links and custom domains require Growth. Start with the features the journey needs, then check that journey again whenever its configuration changes.
Sources and product references
Reviewed October 11, 2026. Platform guidance and product limits can change; use these references when you repeat a check.
Make a link you can check.
Create a free Smart Link, then use the worksheet before putting it in your bio, email or print artwork.
Create a free Smart Link