Dapp browser

A web browser built into a self-custody wallet app, so decentralised applications load with the wallet already available for signing, without needing a separate browser extension.

Definition

A dapp browser is the in-app browser found in most mobile wallets. A site opened inside it can talk to the wallet directly, because the wallet is the browser, which is how a DEX becomes usable on a phone at all.

Why mobile needs it

On a desktop the wallet is an extension injected into an ordinary browser. Mobile browsers do not support that arrangement, so a DEX opened in the phone’s normal browser has nothing to connect to. The wallet app supplies the browser instead, and the connection works without any bridging step.

WalletConnect solves the same problem from the other direction, pairing a wallet app with a site open elsewhere. Which one is smoother depends on the wallet and the site.

What to watch for

The address bar is smaller, and on some wallets partly hidden. Every phishing risk that applies on desktop applies here with less of the context you would normally use to spot it, so the case for a saved bookmark inside the wallet rather than a search or a pasted link is stronger, not weaker.

Signature prompts are also more cramped on a phone screen. The transaction details are still there, and still the thing that decides whether you keep your funds.

Practical limits

Trading interfaces built for a desktop layout are frequently reduced on mobile: charts are simplified, some order types are missing, and depth information may be omitted. Confirm that the actions you rely on, particularly setting a stop, are actually available before treating a phone as your only access to an open position.

Where you will run into it

In mobile wallet apps, as the route to a DEX that has no native app of its own.