Detect extension installation automatically and prompt for authentication

[markmhendrickson]

Instead of requiring a manual refresh of the app upon installing the extension, we should automatically detect installation and prompt the user to proceed with authentication, either in the introductory modal or by opening the extension automatically as possible.

Current screen

[markmhendrickson]

@aulneau @hstove do you know if automatic detection and opening of the extension here is possible upon return to the app's window? Or would @jasperjansz have to design some sort of updated state here where the user manually clicks to proceed to authentication with the newly installed extension?

[jasperjansz]

potentially related: https://docs.metamask.io/guide/onboarding-library.html#getting-started

[fbwoolf]

Right now, after install the full page tab opens for the wallet so a user can go thru auth, do we want to change that so it redirects back to the app and launches a popup to authenticate instead?

[fbwoolf]

I did not experience any different behavior than what we have now when I did the same process with Uniswap and MetaMask. Uniswap told me to install, I did, after install their full page tab was launched, I went back to Uniswap and had to manually close their modal and refresh before it detected I had installed MetaMask.

[fbwoolf]

I think what we would want to do here is just close the modal once they have clicked on the download button ...and then in the web wallet extension reload the app page once it is installed and trigger the popup to go thru authentication?

[jasperjansz]

@fbwoolf related issue that can actually be implemented: https://github.com/blockstack/stacks-wallet-web/issues/1275

[fbwoolf]

@jasperjansz great, thanks! I can assign myself to that one too and maybe it can close both.

[markmhendrickson]

@fbwoolf I believe you resolved this with #148 already, correct?

[fbwoolf]

@fbwoolf I believe you resolved this with #148 already, correct?

My work on this was never merged. It is still in draft status. We decided to include it with the future onboarding refactor.