{"id":1833,"date":"2026-07-24T09:00:00","date_gmt":"2026-07-24T14:00:00","guid":{"rendered":"https:\/\/tolinku.com\/blog\/?p=1833"},"modified":"2026-03-07T03:50:11","modified_gmt":"2026-03-07T08:50:11","slug":"custom-url-schemes-guide","status":"publish","type":"post","link":"https:\/\/tolinku.com\/blog\/custom-url-schemes-guide\/","title":{"rendered":"Custom URL Schemes for Mobile Apps: Setup and Pitfalls"},"content":{"rendered":"\n

Custom URL schemes (myapp:\/\/products\/123<\/code>) were the original way to open a specific screen in a mobile app. They are easy to implement but fundamentally flawed: no ownership verification, no fallback, and no security. This guide covers when they are still useful, how to set them up, and when to migrate to Universal Links and App Links instead.<\/p>\n\n\n\n

For the comparison between URL schemes and Universal Links, see URI schemes vs Universal Links: which should you use?<\/a>. For a complete deep linking overview, see the complete guide to deep linking in 2026<\/a>.<\/p>\n\n\n\n

How Custom URL Schemes Work<\/h2>\n\n\n\n

A custom URL scheme registers a prefix (like myapp:\/\/<\/code>) with the operating system. When any app or browser opens a URL with that prefix, the OS launches the registered app and passes the full URL.<\/p>\n\n\n\n

myapp:\/\/products\/123\n  \u2193\nOS looks up which app registered "myapp:\/\/"\n  \u2193\nLaunches that app with the URL\n  \u2193\nApp parses the URL and navigates to ProductDetail(id: 123)\n<\/code><\/pre>\n\n\n\n
iOS Setup<\/h2>\n\n\n\n
Registering the Scheme<\/h3>\n\n\n\n
In your Info.plist<\/code>:<\/p>\n\n\n\n
<key>CFBundleURLTypes<\/key>\n<array>\n  <dict>\n    <key>CFBundleURLName<\/key>\n    <string>com.yourcompany.myapp<\/string>\n    <key>CFBundleURLSchemes<\/key>\n    <array>\n      <string>myapp<\/string>\n    <\/array>\n  <\/dict>\n<\/array>\n<\/code><\/pre>\n\n\n\n
Or in Xcode: Target > Info > URL Types > Add a URL scheme.<\/p>\n\n\n\n
Handling the URL<\/h3>\n\n\n\n
UIKit (AppDelegate):<\/strong><\/p>\n\n\n\n
func application(_ app: UIApplication,\n                 open url: URL,\n                 options: [UIApplication.OpenURLOptionsKey: Any] = [:]) -> Bool {\n    guard url.scheme == "myapp" else { return false }\n\n    let host = url.host          \/\/ e.g., "products"\n    let path = url.path          \/\/ e.g., "\/123"\n    let query = url.query        \/\/ e.g., "ref=email"\n\n    return router.handle(host: host, path: path, query: query)\n}\n<\/code><\/pre>\n\n\n\n
SwiftUI:<\/strong><\/p>\n\n\n\n
@main\nstruct MyApp: App {\n    var body: some Scene {\n        WindowGroup {\n            ContentView()\n                .onOpenURL { url in\n                    router.handle(url)\n                }\n        }\n    }\n}\n<\/code><\/pre>\n\n\n\n
Testing on iOS<\/h3>\n\n\n\n
# Open a custom URL scheme in the Simulator\nxcrun simctl openurl booted "myapp:\/\/products\/123"\n<\/code><\/pre>\n\n\n\n
Or in Safari on a real device, type myapp:\/\/products\/123<\/code> in the address bar (Safari will ask "Open in MyApp?").<\/p>\n\n\n\n
Android Setup<\/h2>\n\n\n\n
Registering the Scheme<\/h3>\n\n\n\n
In your AndroidManifest.xml<\/code>:<\/p>\n\n\n\n
<activity android:name=".DeepLinkActivity"\n          android:exported="true">\n    <intent-filter>\n        <action android:name="android.intent.action.VIEW" \/>\n        <category android:name="android.intent.category.DEFAULT" \/>\n        <category android:name="android.intent.category.BROWSABLE" \/>\n        <data android:scheme="myapp" \/>\n    <\/intent-filter>\n<\/activity>\n<\/code><\/pre>\n\n\n\n
Handling the Intent<\/h3>\n\n\n\n
class DeepLinkActivity : AppCompatActivity() {\n    override fun onCreate(savedInstanceState: Bundle?) {\n        super.onCreate(savedInstanceState)\n\n        val data = intent.data ?: return\n        val host = data.host       \/\/ e.g., "products"\n        val path = data.path       \/\/ e.g., "\/123"\n        val query = data.query     \/\/ e.g., "ref=email"\n\n        router.handle(host, path, query)\n    }\n}\n<\/code><\/pre>\n\n\n\n
Testing on Android<\/h3>\n\n\n\n
# Open a custom URL scheme on a connected device\nadb shell am start -a android.intent.action.VIEW \\\n  -d "myapp:\/\/products\/123" \\\n  -c android.intent.category.BROWSABLE\n<\/code><\/pre>\n\n\n\n
Limitations of Custom URL Schemes<\/h2>\n\n\n\n
1. No Ownership Verification<\/h3>\n\n\n\n
Any app can register any URL scheme. There is no verification that myapp:\/\/<\/code> belongs to your company. If another app registers the same scheme:<\/p>\n\n\n\n