How to link to apps on the app store
Master System Design with Codemia
Enhance your system design skills with over 120 practice problems, detailed solutions, and hands-on exercises.
Introduction
Linking to an App Store page is mostly about choosing the right URL format for the context. A normal HTTPS link is best for websites, messages, and email, while app-to-App Store handoff from iOS often uses the itms-apps scheme for a more direct launch. This article covers both forms, shows how to open them safely, and explains when SKStoreProductViewController is a better user experience.
The Universal Web Link Format
For most purposes, use the normal App Store HTTPS URL. This works in browsers, on mobile devices, and on desktop.
Typical format:
If you know the app name slug, Apple also supports URLs like this:
The important part is the numeric App Store app ID. That is the most stable identifier in the URL.
Linking from an iOS App
Inside an iOS app, a common approach is to open the App Store directly with UIApplication.
The itms-apps scheme skips the browser step and usually opens the App Store app directly. That makes it a good choice for upgrade prompts or "rate this app" flows.
Use HTTPS When the Link Leaves Your App Context
If the link is shown on a website, in documentation, or in a cross-platform UI, prefer HTTPS.
HTTPS links are more portable and degrade more gracefully outside iOS.
Present the Store Inside Your App
If you want users to stay inside your app while viewing the store page, use SKStoreProductViewController.
This is useful for upgrade nudges because it keeps the user inside your app flow rather than sending them out to the App Store app.
Region and Localization Notes
App Store URLs often contain a storefront region such as /us/ or /gb/. If you omit the explicit region, Apple can often resolve the correct storefront automatically, but region-specific links are still common in marketing material.
If your app is available only in certain storefronts, test the link in those regions before shipping campaigns or in-app prompts.
Finding the App ID
The app ID is not the bundle identifier. It is the numeric App Store identifier assigned in App Store Connect.
Examples:
- bundle identifier:
com.example.myapp - App Store ID:
1234567890
Many broken links come from mixing those up.
Linking to Ratings and Reviews
Some teams also want a review page link rather than the app landing page. That is possible, but the exact URL pattern is more brittle than the main app page. If your goal is in-app review prompting, SKStoreReviewController is usually the better API for supported contexts.
That means the decision tree is often:
- app page link for install or upgrade
- '
SKStoreProductViewControllerfor in-app store display' - '
SKStoreReviewControllerfor rating prompts'
Common Pitfalls
- Using the bundle identifier where the App Store numeric ID is required.
- Using
itms-appsin places where a normal web URL would be more portable. - Sending users out of the app when an in-app store sheet would give a better experience.
- Hard-coding a storefront region without verifying that the app is available there.
- Treating rating prompts and store-page links as the same problem.
Summary
- Use the HTTPS App Store URL for web, email, and general sharing.
- Use
itms-appswhen opening the App Store directly from an iOS app. - Use
SKStoreProductViewControllerwhen you want the store page inside your app. - The critical identifier is the numeric App Store ID, not the bundle identifier.
- Choose the link style based on context: portability, direct launch, or embedded store experience.

