Skip to main content





How to define Mobile App deep links

  • Edit
    Collaborate with us
    Edit this page on GitHub
  • We're working to improve this article. Please leave us your feedback about how you think it can be improved.

    To define a deep link to a Screen (<screen>) of a Module (<module>) of a Mobile App use the following syntax:


    Where <app-identifier> is the App identifier you defined when generating your Mobile App Package in lowercase.

    As a best practice the App identifier of your Mobile App should be lowercase.
    In deep links the <app-identifier> scheme must be lowercase, even if your App identifier has uppercase characters.

    To include values for Input Parameters in your deep link use the following syntax:


    If you use a RedirectToURL destination to open a external website, you can't call a deep link back to the mobile app from the external website in iOS devices. Instead if you need to open an external website, use the Open client action from the InAppBrowser Plugin with the Target set as Entities.Target.SYSTEMand the Url set as the external website url.

    Android Intents

    For Android end users with Chrome you can use Android Intents. Android Intents allow the redirection of end users that do not have your App available on their device to your App page in the Google Play Store or to another URL specified by you.

    When you generate an Android App in OutSystems 10 it already includes a `BROWSABLE` Intent filter.

    To define an Android Intent use the following syntax:


    To specify a custom fallback URL (<URL>) add a string extra S.browser_fallback_url=<URL>; to the Intent: