Readme's description of the behaviour of mobile apps. about detect-provider HOT 6 CLOSED

Would it make more sense if we changed the wording to something like this?

The MetaMask extension provider is synchronously injected, while the MetaMask mobile provider (only available when accessing a dapp inside of the mobile app) is asynchronously injected.

from detect-provider.

@mcmire
It looks good. 👍

[nit]
I think you may want to write that deeplink is recommended as a countermeasure in case the presence of window.ethereum cannot be detected.

from detect-provider.

@uji We could certainly remind people about deeplinking as a way of bypassing the need to detect the provider. That would assume your dapp is so simple that you don't need to connect to the user's wallet at all -- you just want to spawn an action in MetaMask, such as a payment request. Is that use case what you had in mind?

from detect-provider.

@mcmire I was thinking of use cases that connect to the user's wallet.
In this case, I thought I needed to transition to the browser inside of the mobile app using deeplink.
Is this a correct understanding?

from detect-provider.

@uji Hmm, I'm not sure I'm quite understanding. Are you wanting to link from somewhere outside of the mobile app to your dapp inside of the mobile app?

from detect-provider.

@mcmire
I want to use MetaMask Ethereum provider in a Dapp running in browsers outside of the MetaMask mobile app(such as Google chrome).
windows.ethereum isn't injected those browsers, so I thought I needed to use deeplink to transition to the MetaMask mobile app browser.

from detect-provider.