you might want to search for deep linking.
https://developers.google.com/web/updates/2017/02/improved-add-to-home-screen#android_intent_filters
The New and Improved Add to Home screen
Paul Kinlan By Paul Kinlan Paul is a Developer Advocate Chrome first
introduced the "Add to Home screen" banners in Chrome 42. This was a
big step for the web as it provided users the ability to easily keep a
favorite site on their home screen, much like native apps. We've heard
from developers like Alibaba that users re-engage 4 times more often
with their site added to home screen. We've also seen that tuning the
heuristics for add to home screen to prompt sooner yields to 48% more
installs.
We are happy to share that the team has worked on an improved add to
home screen experience that makes web apps first-class citizens of
Android. Instead of simply being a shortcut icon, web apps will now be
integrated with Android. This means that users that add a PWA to their
home screen will be able to find it anywhere they see other apps (e.g.
in the app drawer or searching for apps), and open the site from
intents. We see this as the first step among a number of improvements
to come and intend to make it the default experience for add to home
screen in the coming months.
The improved add to home screen experience is already available in
Chrome Canary and will be rolling out to Chrome 57 beta over the next
few weeks.
Note: it has been rolled to all users on Chrome's stable channel as of
Chrome 59. To test your site, visit your PWA. You can start install
from the three dot menu > "Add to Home screen" or through the add to
home screen banner.
This new experience is a huge improvement over the original version of
add to home screen, but there are some differences between these
installed Progressive Web Apps and Android Apps.
Updating your app's icon and name You now have the ability to update
your Progressive Web App's icon and name and have it reflected to the
user. Changing your icon or name in the manifest will update the icon
on the home screen after the user has subsequently opened the site.
Android Intent Filters When a Progressive Web App is installed via
this new improved add to home screen experience it will be registered
with the system to be a target for the URL space for its domain. This
means that the when a user clicks on a link that is contained within
the scope of your Progressive Web App, your app will be opened instead
of Chrome opening with your PWA running.
When you install a Progressive Web App, we look at your Web App
Manifest and other meta-data and create an APK (Android Package Kit)
that is installed on to the user's device, which may take a short
moment the first time any user installs your Web App.
Note: Whenever the Web App Manifest changes we need to generate a new
APK, it is thus not a good idea to have frequently updating manifests.
It is especially important to ensure that you don't use user specific
identifiers in the manifest (such as a custom start_url per user) as
this generate an unique APK which means that your install time will be
a lot longer than you expect. In that APK we define an Android Intent
Filter that defines when your web application should be opened. For
example, to open the https://airhorner.com app whenever that link is
clicked, Chrome would create the following .
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data
android:scheme="https"
android:host="airhorner.com"
android:pathPrefix="/" />
</intent-filter>
This is incredibly powerful, but not very flexible. This
simply says when a link that is clicked or intercepted
in Android for the entire domain of https://airhorner.com/ open the
App.
But what if you don't want your PWA to open for all paths on your
domain? That is where the scope web app manifest property comes in to
play. The scope is a....
