feat(#1360): Document how to configure Android App Link verification

[m5r]

Description

#1360

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

[m5r]

@jkuester @sugat009 could you take a look at the docs for setting up medic/cht-android#308 ?
Feel free to point out/add anything I might have missed

[jkuester]

Nice and detailed! I left a few comments about content and structuring of the docs within the site, but here is my overall vision:

• General overview of deep linking functionality (especially from a user's perspective) should go in features/integrations/android
• The technical instructions for how to create your assetlinks.json file and how to verify that deep links work with your app/instance should go in guides/android (either in a new page or as a section of guides/android/branding.
• An overview of the assetlinks.json file structure, its location and usage in the config should go in reference/app-settings/assetlinks.

With the right linkage connecting everything I think this would communicate the right things to the right people in the right places. (Open to other ideas here though!)

I have been working on testing these steps locally, but ran out of time today and did not want to block the rest of this review. I will leave another comment tomorrow regarding how my tests went!

[jkuester]

Just following up to say I was successfully in getting this process to work end-to-end, starting from scratch with a new Android flavor by following this documentation! In particular, the verification instructions were very handy when I typoed my package name and was trying to debug what was going wrong!

All in all, this is a tricky process, but this documentation is solid and makes it very straight forward to get things setup!

[jkuester]

This is great! Had a few minor thoughts that I left inline, but all in all we have some solid documentation here!