Why a wallet simulator should run in a browser tab

An installer asks for trust, permissions and an update channel you keep forever. A tab asks for none of that, and it still draws the screen.

Published: 20 September 2026 · Last reviewed: 25 September 2026

What an install asks for

An installer is a request for permissions, and the list is longer than it looks: run code outside the browser sandbox, read and write files, stay resident after you close the window, update itself later without asking again. You grant all of it at once, to whoever holds the signing key, for as long as the thing stays on the machine.

For most software that trade is worth making. For a tool whose only job is to draw a picture of a screen, it is a strange price. Composing a token list does not need your filesystem.

What a tab asks for

Almost nothing. A browser based wallet simulator runs in a sandbox that cannot read your disk, cannot see your other tabs, and cannot start itself tomorrow. Storage is scoped to one origin. Closing the tab ends the program. Undoing an install is a chore. Undoing a tab is a keystroke.

Rendering happens locally: the screen is drawn by your browser, never on a server. What the server keeps is your wallet's configuration, images included, so it reopens on another device, for your account only.

The structural part

The security argument is not a promise about our conduct. It is about what the tool is made of. There is no field for a seed phrase, no wallet connection, no chain read and no transaction signed. A program that never touches a real wallet cannot empty one, whatever its author intends and whatever a future update does.

That matters more here than in most categories, because a fake wallet installer is the oldest theft in crypto. Software shaped like a wallet is the last software anyone should download from a link. A mockup that stays in a tab removes the question.

What the browser costs

Three real costs. Pretending otherwise would be dishonest.

• The render depends on the machine. Font hinting, colour profiles and GPU compositing are not identical across devices, so the same screen can land a hair differently on a phone and on a laptop.
• Memory bounds the page. Every sheet, chart and icon is drawn live, and an older phone with a dozen tabs open can drop the page while it holds all of that.
• Live prices need a connection. Offline, the numbers stop moving and the screen keeps whatever they last were.

The first two share a workaround: compose on the least loaded device you have, and close the other tabs first.

Installing it changes nothing

You can add it to a home screen, and it opens full screen with no browser chrome. That is the same page on the same origin under the same sandbox rules — no store, no package, no new permission granted. It looks like an install and behaves like a bookmark, which is the right amount of trust for a tool that produces mockups.

Questions

What can a tab reach that an installed app cannot?

The other way round. An installed app can read files, sit in your login items and update itself on its own schedule. A tab reads nothing outside its own origin, runs no process once you close it, and cannot see your other tabs. An avatar or token icon you drop in is drawn by the browser, then saved with your wallet on your account so it reopens on your other devices, and only you can open it.

Why does a wallet mockup never ask for a seed phrase?

Because it has no use for one. The tool draws a picture from numbers you type. It reads no chain, signs nothing and holds nothing, so a key would buy it no information it needs. Any tool shaped like a wallet that asks for a phrase before it will show you anything is asking for the one thing that empties an account.

What does running in a browser cost?

Three things. Fonts and colour management differ slightly between machines, so two devices can render the same screen a hair apart. A live wallet, with its charts and sheets, is a heavy page for an older phone with twenty tabs open. And live prices need a connection: offline, the numbers freeze at whatever they were.