VANKPA
The decision
A deep link should take the user to the relevant task or record rather than the app's home screen. It also needs a useful fallback when the app is absent or the session has expired. Treat links as part of the complete journey.
In practice
An appointment reminder should open the appointment the person needs to review. If login is required, preserve the intended destination after authentication. Do not expose private information merely because someone possesses a link.
- Test installed and uninstalled states, expired sessions, moved records, and unsupported devices.
- Review link permissions and web fallback behavior.
- Maintain links when routes change so older messages still provide a useful path.
When to take the next step
Plan deep links when emails, reminders, or shared records direct people into the app. Test the full destination journey before distributing the first production link.
Questions clients ask
Can a deep link bypass login?
Only if the specific resource is intended to be public; private records still require authorization.
What if the app is not installed?
Provide an appropriate web experience or clear installation path with the destination preserved where possible.