Summary
In an earlier version of beacon, before the new UI was introduced, the mobile view was different on iOS and Android. On Android, only one button was displayed "Open Wallet", on iOS, a list of all mobile wallets was displayed.
On iOS, the deeplink is invoked with the name of the specific wallet that was selected, eg. umami:// or airgap-wallet://.
On Android, the generic tezos:// deeplink is used.
This is done because iOS does not allow you to select a specific app if multiple apps listen to the same deeplink.
In the new UI, the list of wallets is displayed on both iOS and Android. This means that on Android, the user has to select his wallet 2 times (once in the beacon UI, afterwards in the system UI).
Advantages of using specific deeplinks:
- The correct app is opened
- Works on iOS, gets rid of additional, unnecessary step on android
Disadvantages of using specific deeplinks:
- Beacon-SDK needs to be updated to support new wallets
Describe the expected behaviour
To be discussed.
Summary
In an earlier version of beacon, before the new UI was introduced, the mobile view was different on iOS and Android. On Android, only one button was displayed "Open Wallet", on iOS, a list of all mobile wallets was displayed.
On iOS, the deeplink is invoked with the name of the specific wallet that was selected, eg.
umami://orairgap-wallet://.On Android, the generic
tezos://deeplink is used.This is done because iOS does not allow you to select a specific app if multiple apps listen to the same deeplink.
In the new UI, the list of wallets is displayed on both iOS and Android. This means that on Android, the user has to select his wallet 2 times (once in the beacon UI, afterwards in the system UI).
Advantages of using specific deeplinks:
Disadvantages of using specific deeplinks:
Describe the expected behaviour
To be discussed.