Android Deep linking: Use the same link for the app and the play store

Question

I have a website which enables the user to make a search query. The query might take some time to complete (minutes to days), and I would like to enable the user to download

Answer 1

Adam's solution is pretty good if you want to build it yourself.

There's an open-source SDK that does exactly this, by Branch Metrics (full disclosure, I work there).

Basically, you set your URI scheme on the Branch dashboard, create a link with the data you want to pass (in this case, the query parameters, but you decide), and the SDK has a method with a callback that gives you said query parameters (through install or regular deeplink by clicking the Branch link).

Answer 2

This question is pretty old but also very popular, so it's definitely worth knowing that now this use case is officially supported by Firebase, precisely Firebase Dynamic Links.

It supports just opening app and deferred deep linking, which means that after installing app, when app is starting, you can retrieve data (link) that was used to install the app.

It's built on top of App Linking, so you still need the same intent-filter as before.

In short, you need to add implementation 'com.google.firebase:firebase-dynamic-links:VERSION' and retrieve link from instance of FirebaseDynamicLinks class.

Of course you need to change links on website with those generated in Firebase console, but the good news is that these links are "dynamic" (as the name implies) so they work on all systems.

For all detailed info and set up with that use case up go here: https://firebase.google.com/docs/dynamic-links/use-cases/web-to-app

Answer 3

You can try using this scheme(to be sent to the user):

intent://details?id=X&url=Y&referrer=Z#Intent;scheme=market;action=android.intent.action.VIEW;package=com.android.vending;end";

X: Package name of the App

Y: Deep link scheme which should be defined in the App's manifest. (Please refer this) Here, they have used this URL as an example: "http://www.example.com/gizmos" , therefore Y should be replaced by this URL.

Z: Can be any data which you want to pass to the App via Google Play. Please take note that any data which you pass should not be '&' separated because the original parameters are itself '&' separated.

From what I experimented, this URL is understood by the browser and it redirects you to the App based on the package name and the deep-link scheme. Else it takes you to the Google Play.

PS: The Google Play makes a broadcast to the app. So make sure you receive the broadcast in a receiver.

Answer 4

This workaround might work:

1. At the server side, create a redirect rule to google play. For example, https://www.foo.com/bar/BlahBlah will redirect to https://play.google.com/store/apps/details?id=com.bar.foo&referrer=BlahBlah.

2. At the app, register the server side link as a deep link:

<data android:scheme="https"
          android:host="www.foo.com"
          android:pathPrefix="/bar" />

Now, if the app is installed, the URL will be caught and the path can be parsed to extract the BlahBlah part. If the app isn't installed pressing the link will redirect the user to the Play store with the referring URL.

Notes:

• /bar/BlahBlah was converted to &referrer=BlahBlah, because the play store receives a URL argument and the deep link mechanism works with URL paths (as far a I can tell)