All Applinks is doing on Android is using the package name you specify in the metadata.
There's really not a lot going on here. Webpage scheme that you can parse to build an intent from. This couldn't be more than 50 lines of code. It would be less if they decided to use a custom URI scheme like "applinks://example.com?packagename=example.com" instead of parsing every webpage you go to looking for the applinks headers.
There's really not a lot going on here. Webpage scheme that you can parse to build an intent from. This couldn't be more than 50 lines of code. It would be less if they decided to use a custom URI scheme like "applinks://example.com?packagename=example.com" instead of parsing every webpage you go to looking for the applinks headers.