Progressive Web Apps (PWAs) and native Android apps are not mutually exclusive. Many products ship both: a PWA for broad reach and a native app for deeper platform integration. The challenge is making links work seamlessly between them. When a user taps a link, should they land in the PWA or the native app? What if they have both installed? What if the native app uses a Trusted Web Activity (TWA) to wrap the PWA?<\/p>\n\n\n\n
This guide covers how App Links interact with PWAs and TWAs on Android, and how to configure both experiences to coexist. For the App Links foundation, see the Android App Links complete guide<\/a>. For web-to-app bridging strategies, see deep linking for web<\/a>.<\/p>\n\n\n\n When you have both a PWA and a native app for the same domain, a link conflict arises:<\/p>\n\n\n\n Android resolves this through intent priority:<\/p>\n\n\n\n This means: if a user has both your PWA and native app installed, and the native app has verified App Links, the native app always wins. The PWA never gets the link.<\/p>\n\n\n\n A Trusted Web Activity<\/a> wraps your PWA in a native Android shell. It uses Chrome's rendering engine but runs full-screen without browser UI. From the Play Store's perspective, it's a native app. From the user's perspective, it looks like a native app. From the deep linking system's perspective, it behaves like a native app.<\/p>\n\n\n\n TWAs use the same Digital Asset Links verification as regular App Links. The TWA's domain must have an When a link to your domain is tapped, the TWA opens full-screen (no browser bar) if verification passes.<\/p>\n\n\n\n TWAs handle deep links by loading the corresponding URL in the web activity. The path from the deep link maps directly to a URL in your PWA:<\/p>\n\n\n\n Your PWA's client-side routing handles the rest. If your PWA uses a framework router (React Router, Vue Router, etc.), the route resolves normally within the TWA.<\/p>\n\n\n\n In your TWA's If you only have a PWA (no native app), deep linking works through the browser. When the user installs the PWA ("Add to Home Screen"), the PWA opens when they tap its home screen icon, but links from other apps still open in Chrome.<\/p>\n\n\n\n To make links open the installed PWA instead of Chrome, wrap it in a TWA and publish to the Play Store. The TWA gives you App Links support.<\/p>\n\n\n\n The most common pattern. Ship both a PWA and a native app. The native app handles all deep links via verified App Links. The PWA serves as the fallback for users who haven't installed the native app.<\/p>\n\n\n\n The PWA acts as a universal fallback because it's just a website. If the native app's App Links fail for any reason, the URL loads in the browser, and your PWA handles the rendering.<\/p>\n\n\n\n Use a TWA to wrap your PWA and publish it on the Play Store. This gives you:<\/p>\n\n\n\n The tradeoff: TWAs have limited access to native APIs compared to a fully native app. If you need push notifications, sensors, or Bluetooth, you'll need a native bridge or a full native app.<\/p>\n\n\n\n Use a native Android app that loads some screens via WebView (from your PWA's domain) and renders others natively. Deep links route to either the native screen or the WebView screen based on the path:<\/p>\n\n\n\n Your PWA can detect whether it's running in a browser, installed as a standalone PWA, or inside a TWA:<\/p>\n\n\n\n If your PWA detects that the user should be using the native app (e.g., they need a feature only available natively), you can redirect:<\/p>\n\n\n\n PWA service workers can interfere with deep linking by caching the wrong response for App Links verification requests.<\/p>\n\n\n\n Never cache If the service worker serves a cached (potentially outdated) Tolinku deep links<\/a> work with both PWAs and native apps. A single Tolinku URL resolves to:<\/p>\n\n\n\n This means you don't need separate link strategies for PWA and native. One Tolinku link covers all scenarios. Configure your Android settings in the Tolinku dashboard<\/a> for the native app, and your PWA naturally serves as the web fallback.<\/p>\n\n\n\n For Android Instant Apps (another alternative to PWAs), see the Instant Apps deep linking guide<\/a>. For the full App Links setup, see the Android App Links guide<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Connect Progressive Web Apps to native Android apps with App Links. Handle TWA deep linking, manage the web-to-native transition, and configure both experiences.<\/p>\n","protected":false},"author":2,"featured_media":1282,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"App Links for Progressive Web Apps on Android","rank_math_description":"Connect Progressive Web Apps to native Android apps with App Links. Handle TWA deep linking and manage the web-to-native transition.","rank_math_focus_keyword":"app links PWA android","rank_math_canonical_url":"","rank_math_facebook_title":"","rank_math_facebook_description":"","rank_math_facebook_image":"https:\/\/tolinku.com\/blog\/wp-content\/uploads\/2026\/03\/og-android-app-links-pwa.png","rank_math_facebook_image_id":"","rank_math_twitter_title":"","rank_math_twitter_description":"","rank_math_twitter_image":"https:\/\/tolinku.com\/blog\/wp-content\/uploads\/2026\/03\/og-android-app-links-pwa.png","footnotes":""},"categories":[10],"tags":[25,23,20,69,326,327,41],"class_list":["post-1283","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-android","tag-android","tag-app-links","tag-deep-linking","tag-mobile-development","tag-pwa","tag-trusted-web-activity","tag-web-to-app"],"_links":{"self":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts\/1283","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/comments?post=1283"}],"version-history":[{"count":5,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts\/1283\/revisions"}],"predecessor-version":[{"id":2577,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts\/1283\/revisions\/2577"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/media\/1282"}],"wp:attachment":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/media?parent=1283"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/categories?post=1283"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/tags?post=1283"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}PWA vs. Native App: The Link Conflict<\/h2>\n\n\n\n
User taps https:\/\/yourapp.com\/products\/123\n \u2192 Should the PWA open? (installed via "Add to Home Screen")\n \u2192 Should the native app open? (installed via Play Store)\n \u2192 Should Chrome open? (if neither is the default)\n<\/code><\/pre>\n\n\n\n\n
Trusted Web Activities (TWA)<\/h2>\n\n\n\n
TWA and App Links<\/h3>\n\n\n\n
assetlinks.json<\/code> file that includes the TWA's package name and signing key.<\/p>\n\n\n\n[{\n "relation": ["delegate_permission\/common.handle_all_urls"],\n "target": {\n "namespace": "android_app",\n "package_name": "com.example.twa",\n "sha256_cert_fingerprints": [\n "YOUR_SHA256_FINGERPRINT"\n ]\n }\n}]\n<\/code><\/pre>\n\n\n\nTWA Deep Link Handling<\/h3>\n\n\n\n
Deep link: https:\/\/yourapp.com\/products\/123\nTWA opens: https:\/\/yourapp.com\/products\/123 (full-screen, no browser UI)\n<\/code><\/pre>\n\n\n\nConfiguring TWA Deep Links<\/h3>\n\n\n\n
AndroidManifest.xml<\/code>:<\/p>\n\n\n\n<activity\n android:name="com.example.twa.LauncherActivity"\n android:exported="true">\n\n <!-- Default launch URL -->\n <meta-data\n android:name="android.support.customtabs.trusted.DEFAULT_URL"\n android:value="https:\/\/yourapp.com" \/>\n\n <!-- App Links for deep linking -->\n <intent-filter android:autoVerify="true">\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="https"\n android:host="yourapp.com" \/>\n <\/intent-filter>\n<\/activity>\n<\/code><\/pre>\n\n\n\nCoexistence Strategies<\/h2>\n\n\n\n
Strategy 1: PWA Only (No Native App)<\/h3>\n\n\n\n
Strategy 2: Native App Takes Priority<\/h3>\n\n\n\n
User has native app \u2192 link opens in native app\nUser has PWA only \u2192 link opens in browser (PWA renders the page)\nUser has neither \u2192 link opens in browser (PWA renders the page)\n<\/code><\/pre>\n\n\n\nStrategy 3: TWA Wraps the PWA<\/h3>\n\n\n\n
\n
Strategy 4: Hybrid (Native Shell + Web Content)<\/h3>\n\n\n\n
fun handleDeepLink(uri: Uri) {\n when {\n \/\/ Native screens\n uri.path?.startsWith("\/products") == true -> openNativeProductScreen(uri)\n uri.path?.startsWith("\/settings") == true -> openNativeSettings()\n\n \/\/ Web-based screens (loaded from PWA)\n uri.path?.startsWith("\/help") == true -> openWebView(uri.toString())\n uri.path?.startsWith("\/legal") == true -> openWebView(uri.toString())\n\n \/\/ Default: native home\n else -> openNativeHome()\n }\n}\n<\/code><\/pre>\n\n\n\nDeep Link Routing Between PWA and Native<\/h2>\n\n\n\n
Detecting the Context<\/h3>\n\n\n\n
\/\/ Detect the display mode\nfunction getDisplayMode() {\n if (document.referrer.includes('android-app:\/\/')) {\n return 'twa'; \/\/ Running inside a Trusted Web Activity\n }\n if (window.matchMedia('(display-mode: standalone)').matches) {\n return 'standalone'; \/\/ Installed PWA\n }\n return 'browser'; \/\/ Regular browser tab\n}\n\n\/\/ Adjust behavior based on context\nconst mode = getDisplayMode();\nif (mode === 'browser') {\n \/\/ Show "Install our app" banner\n showInstallBanner();\n} else if (mode === 'twa') {\n \/\/ Running as TWA; hide any "open in app" prompts\n}\n<\/code><\/pre>\n\n\n\nRedirecting from PWA to Native App<\/h3>\n\n\n\n
\/\/ Try to open the native app via intent URL\nfunction openNativeApp(path) {\n const intentUrl = `intent:\/\/${path}#Intent;` +\n `scheme=https;` +\n `package=com.example.nativeapp;` +\n `S.browser_fallback_url=${encodeURIComponent(window.location.href)};` +\n `end`;\n\n window.location.href = intentUrl;\n}\n<\/code><\/pre>\n\n\n\nService Worker Considerations<\/h2>\n\n\n\n
\/.well-known\/assetlinks.json<\/code> in your service worker:<\/strong><\/p>\n\n\n\n\/\/ In your service worker\nself.addEventListener('fetch', (event) => {\n const url = new URL(event.request.url);\n\n \/\/ Don't cache Digital Asset Links or Apple App Site Association\n if (url.pathname.startsWith('\/.well-known\/')) {\n return; \/\/ Let the network handle it\n }\n\n \/\/ Cache everything else normally\n event.respondWith(\n caches.match(event.request).then(cached => cached || fetch(event.request))\n );\n});\n<\/code><\/pre>\n\n\n\nassetlinks.json<\/code>, App Links verification may fail.<\/p>\n\n\n\nTolinku Integration<\/h2>\n\n\n\n
\n