Deep Link management (Dynamic Link)
There is a increase number of users that are not using the desktop browser to navigate by internet, but they are using the mobile device browser to do it. In that case, the mechanism to exchange information and comply with the current protocols is using deep links. As there are many vendors using this, but also other applications related to global protocols (oidc) there are a lot of apps linked to the schemas used to trigger a concrete operation (openid://..., credential-offer-uri://..., etc.). This approximation could be OK, if we could use a concrete domain (app.vendor.io), but the case is this must be generic, so when you trigger a deep link, this triggers a wallet. The problem is there is just 1 schema but a lot of vendor in the same device. So, in Android there is no problem because user can choose what is the app he wants to use for that deep link, but that is not the case of iOS, where the operative system is triggering the app automatically (the user can not choose).
Also other apps as Google authenticator are using schemas as openid://, so this makes this feature more difficult.