How to Plan Mobile App Deep Links and Fallbacks
To plan mobile app deep linking, define the exact destination and fallback for every link that should open your app. Decide what happens when someone is signed out, has not installed the app, cannot access the content, or follows an outdated link. Include verified links in the build plan, and require access checks at the destination: possessing a link must never count as permission.
Which destinations should your links support?
Start with the things people need to reach directly: a booking, product, shared document, invitation or support conversation. Describe the destination in plain language before choosing its link format.
“Open the app” is too vague. “Open the booking details for the selected booking” gives the team something to build and test.
For each destination, record:
- Who will send or share the link.
- Whether the content is public or private.
- Which record identifies the destination.
- What the person should see first.
- What should happen if that destination is unavailable.
Keep the first release focused. If sharing products matters but sharing account settings does not, support the product journey first. Use your app MVP scope to decide which destinations belong in the initial build.
What should go into a destination and fallback table?
Use one row per link purpose. Make the fallback a useful next step, with a short explanation when the original destination cannot open.
The following is an illustrative planning example for a booking app:
| Link purpose | Intended destination | Signed-out behaviour | Fallback |
|---|---|---|---|
| View a public service | Service details | Open without sign-in | Service list if removed |
| View a private booking | Booking details | Sign in, then check access | Booking list or access message |
| Accept an invitation | Invitation review screen | Sign in, then validate invitation | Expired or unavailable invitation message |
| Read a support reply | Relevant conversation | Sign in, then check access | Support home with an explanation |
Add installation behaviour to each row too. A public service might have a useful web page. A private booking might need a page explaining how to open or install the app without exposing booking details.
Avoid making the home screen the automatic answer to every failure. It gives the person no explanation of what happened to the link they followed.
What should happen when someone is signed out?
Plan sign-in as a step within the journey. After successful sign-in, the app should attempt to continue to the requested destination.
Write the full sequence into the requirements:
- Recognise a supported destination.
- Keep only the information needed to resume it.
- Ask the person to sign in when required.
- Check whether that account can access the destination.
- Open the content or explain why it is unavailable.
Specify what happens if sign-in is cancelled, fails, or uses a different account. For example, offer a clear way to switch accounts when appropriate, without revealing private details about the requested record.
Keep the return destination within the app's supported routes. Do not let an arbitrary link parameter decide where the person goes after sign-in.
Where should links lead when the app is not installed?
Choose an installation fallback for each journey. Do not promise that installing the app will automatically restore the original destination unless that exact journey has been implemented and tested.
A public product or service can have a web page with enough information to continue. An app-only feature can have a landing page explaining what the person needs and offering an installation route.
Decide whether preserving the original destination through installation is essential. If it is, include it as a separate acceptance criterion and test it from the original link through installation to the final screen.
Otherwise, provide an explicit recovery step, such as returning to the message and opening the link again after installation. Make that instruction visible before the person leaves for installation.
Never place private booking details or account information on the fallback page merely to make it feel more complete.
What do verified links add to the plan?
Verified links associate a web domain with an app so that supported web links can be handled by that app. On Android, the App Links documentation describes this as a verified association between your app and your website, so verified links can open the app without a chooser.
Ask the developer to document which domains and destinations the app will handle. Include domain verification, the web fallback and link-opening tests in the release scope.
Keep the promise narrow. Do not describe verified links as a guarantee that every tap will open the app. Android, for example, documents App Links as supported only on certain Android versions and on devices with Google services.
Verification also does not answer whether a person may view a booking or document. Keep link handling and account permissions as separate requirements.
How should access checks work?
Treat every incoming link as an untrusted request to navigate.
Require the service providing private content to check the signed-in account's permission before returning that content. Apply the same rule to actions reached through a link, such as accepting an invitation or changing a booking.
A useful acceptance condition is: changing the record identifier in a link must not reveal another account's information.
For invitations, define who may accept, whether the invitation expires, and what happens after it has already been used. Review those conditions when acceptance is attempted.
For actions with consequences, open a review screen and require confirmation. A link to cancel a booking should show the booking and cancellation choice before making a change.
Keep sensitive information out of link text and parameters. Specify the minimum destination information the app needs.
What if the content is missing or the connection fails?
Give these situations different handling.
If content has been removed, explain that it is no longer available and offer a relevant list or search screen. If access is denied, use a message that does not confirm private details unnecessarily.
If the connection fails, offer retry and a way back. Avoid calling something deleted when the app has not successfully checked it.
Also define behaviour for an unsupported destination or an older app version. Choose a web fallback, an update prompt or a clear unsupported-link message.
Write the message and next action alongside each failure state. “Something went wrong” is rarely enough to help someone recover.
How should you test the complete journey?
Test links from the places people will actually encounter them, including messages, email, web pages and notifications where relevant.
For each supported destination, check:
- App installed and app absent.
- App closed and already open.
- Signed out and signed in.
- Correct account and an account without access.
- Available, removed and malformed destinations.
- Working connection and failed requests.
- Cancelled sign-in and successful return.
- Repeated opening of the same link.
Check the back button too. Agree whether it should return to a parent screen, the previous app screen or another sensible destination.
Record expected screens and messages before testing. The Android app testing guide can help place these journeys within wider release checks.
Which common mistakes should you avoid?
The first mistake is planning only the successful tap. Installation, sign-in, permissions and missing content need explicit outcomes too.
Another is using one generic fallback everywhere. A public listing and a private conversation need different recovery paths.
Avoid assuming that a hard-to-guess identifier provides permission. Require the same access decision whether someone arrives through normal navigation or a shared link.
Finally, include shared links in maintenance planning. When destinations change, decide how older links should behave. Add those checks to app maintenance after launch.
What questions do founders often ask?
Does every screen need a deep link?
No. Prioritise destinations people need to share, revisit or open from outside the app. Leave temporary screens and unfinished steps out unless there is a clear use case.
Should a link open content immediately after sign-in?
That should be the planned outcome when the content still exists and the account has access. Include a clear alternative when either condition fails.
Can we add installation recovery later?
Yes, if the first release provides a useful fallback and clear recovery instructions. Avoid promising automatic continuation until it has been verified through the complete journey.
What should we give the development team?
Provide the destination table, access rules, installation behaviour, failure messages and test checklist. Together, these define what each link promises and how the app should respond when it cannot fulfil that promise.