At the moment Beacon UI does not expect to have extensions installed, when navigator.userAgent is of mobile nature. It does check their presence (pings are received by extension), but will not provide corresponding user-actions (render corresponding buttons).
Thus, there is no attempt to connect with extension at all. Noticed this, while adapting our wallet extension for mobile-first browsers.
At the moment Beacon UI does not expect to have extensions installed, when
navigator.userAgentis of mobile nature. It does check their presence (pings are received by extension), but will not provide corresponding user-actions (render corresponding buttons).Thus, there is no attempt to connect with extension at all. Noticed this, while adapting our wallet extension for mobile-first browsers.
With this consideration, UI is up to be decided, but desired effect is reflected by this PR: https://github.com/airgap-it/beacon-sdk/pull/791
https://github.com/airgap-it/beacon-sdk/assets/39278927/c25297bd-2d77-4166-b43c-ac8c52dea809
https://github.com/airgap-it/beacon-sdk/assets/39278927/cdbf877c-9ec2-4568-a86d-6d38d673956f