Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beacon UI on mobile #594

Open
AndreasGassmann opened this issue Sep 28, 2023 · 0 comments
Open

Beacon UI on mobile #594

AndreasGassmann opened this issue Sep 28, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@AndreasGassmann
Copy link
Member

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.

@AndreasGassmann AndreasGassmann added the enhancement New feature or request label Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant