Android App Links work by letting your app claim links to your own website: the app declares the domain in an intent filter with android:autoVerify="true", and Android checks a file on that domain when the app is installed. Once verified, a tap on https://yoursite.com/... opens your app directly, with no “Open with” chooser. For a website app, the app then has to load that exact URL in its WebView, or the user lands on the homepage instead.
Deep links vs Android App Links
A deep link is any link an app says it can open, while an App Link is a deep link to your own site that Android has verified. Google’s App Links overview says deep links work on all Android versions but are “subject to the system disambiguation dialog.” Verified App Links skip that dialog and open the matching content in your app.
There’s a catch for older or unusual phones. App Links are supported on Android 6 and later, and only on devices that have Google services.
What happens when someone taps a link
When someone taps a link, Android picks the app in a fixed order. The deep linking guide lists it:
- The user’s default app for that URI, if they set one.
- The only installed app that can handle it.
- Otherwise, a disambiguation dialog where the user picks.
Android 12 changed the fallback. Starting in Android 12 (API level 31), a web link reaches your app only if the app is approved for that domain. Links that aren’t verified App Links generally open in the browser by default. An unverified website app gets no chooser. It loses the tap to Chrome, silently.
The intent filter your app needs
The manifest declares which links the app handles with an intent filter. It needs:
- action
android.intent.action.VIEW - category
android.intent.category.BROWSABLE, so browsers can reach it - category
android.intent.category.DEFAULT - a
<data>tag with the scheme and host, such asandroid:scheme="https"andandroid:host="www.example.com"
Add android:autoVerify="true" to the filter to ask for verification. Keep separate filters for different hosts or schemes, because Google notes that several <data> elements in one filter “are actually merged together.” The app can end up claiming combinations you never meant.
How Android verifies your domain
Android verifies your domain by downloading a Digital Asset Links file from the site at install time. The verification guide says that with autoVerify in at least one filter, installing on Android 6.0 (API level 23) or higher makes the system check https://<hostname>/.well-known/assetlinks.json. That file names your package and its signing fingerprint. Our post on assetlinks.json covers what goes in it and which fingerprint to use when Play App Signing re-signs your release.
Two details trip people up:
- Verification is asynchronous. Google says to wait at least 20 seconds after install before checking.
- On Android 11 (API level 30) and lower, the app becomes the default handler only if the file matches for all hosts in the manifest. One forgotten subdomain breaks the whole set.
Fix the file later and newer phones catch up on their own: Android 15 (API 35) and higher re-verify periodically, but changes can take up to seven days to spread. Android 14 (API 34) and lower don’t re-verify in the background, so users there pick up the fix only on install or update.
Passing the tapped link to the WebView
A verified App Link only opens your app; the app still has to show the page that was tapped.
Say a customer gets an order email with https://shop.example.com/orders/1234. Verification works, the app opens, and then the WebView loads its start URL. The customer sees the homepage and has to find the order again.
The fix is to read the incoming intent early. Google’s deep linking guide says to call getData() and getAction() in onCreate() or onStart(). In Kotlin that’s val data: Uri? = intent?.data. If data is a URL on your domain, load it in the WebView instead of the start page. If it’s null, the app was opened from the launcher, so load the start page as usual.
How to test Android App Links with adb
Test on a real device with a few adb commands from the verification guide. Replace PACKAGE_NAME with your app’s package name.
- Check each domain’s state:
adb shell pm get-app-links PACKAGE_NAME - Force a fresh check after changing the file:
adb shell pm verify-app-links --re-verify PACKAGE_NAME - Simulate a tap:
adb shell am start -a android.intent.action.VIEW -c android.intent.category.BROWSABLE -d "https://www.example.com/some/page"
A state of verified means it worked. none means nothing is recorded yet, so wait and run step 2 again. A number of 1024 or higher, like the 1026 in Google’s sample output, is a verifier error. Google’s advice is to check the network connection and re-verify.
What this means for a WebToAPK Free app
WebToAPK Free’s documented options are the app name, package name, icon, colour, theme, navigation and content sections, so none of them adds an App Links intent filter for your domain. A website app built there opens from its launcher icon, and links tapped elsewhere on the phone keep opening in the browser. Inside the app, external links can also behave differently than in Chrome.
My take: most small business apps don’t need App Links. If your users arrive from the home screen, skip them. They earn their setup when you send links by email, SMS or notifications and want them to land in the app. If you need that today, a Trusted Web Activity or your own Android project is the route.
The real limitation of App Links is that failure is quiet. A wrong fingerprint or a missing host doesn’t show an error to the user on Android 12 and up. The link just opens in Chrome, so test with adb after every key or domain change.
FAQ
What is the difference between a deep link and an App Link?
A deep link is any link your app says it can open, and Android may show a chooser for it. An App Link is a deep link to your own website that Android has verified, so it opens in your app without a chooser.
Why do my links still open in Chrome on Android 12?
On Android 12 and higher, web links that are not verified App Links generally open in the browser by default. Check the domain’s state with adb shell pm get-app-links and fix whatever stops verification.
When does Android verify my domain?
Android verifies the hosts when the app is installed, as long as at least one intent filter has android:autoVerify=“true”. Verification runs in the background, so wait at least 20 seconds before checking.
Do App Links work on every Android phone?
No. Google’s docs say App Links are supported on Android 6 and later, on devices that have Google services.