What a hardware wallet simulator can and cannot show
A device has a screen the size of a stamp, two buttons and a signing chip. An app mockup reproduces none of that — and it is often the app you were after anyway.
Published: · Last reviewed:
A hardware wallet simulator usually means one of two things: an emulator that runs a device's firmware, or a mockup of the phone app that pairs with the device. My Larp Wallet is the second — it composes an application screen that opens on your phone, where a screenshot comes out at the phone's own resolution, and it simulates nothing about the device itself.
Two different things share one name
Search for a hardware wallet simulator and you land on two unrelated products. One is an emulator: the device firmware, compiled for a desktop, showing the tiny screen in a window so developers can test a build without flashing hardware. Those come from the device projects themselves and are built for people writing firmware.
The other is a mockup of the phone app — the one that pairs with the device over USB or Bluetooth and shows accounts, balances and a token list. That is a normal mobile interface. Most people searching want the second one and do not know the distinction exists.
A device screen is not a small phone screen
A common device display is 128 by 64 pixels and monochrome; colour panels run around 240 by 240. A phone screenshot of this tool is 1179 by 2556 on an iPhone 14 Pro. That is not a difference of scale. It is a difference of kind.
At 128 pixels wide, a 42-character address does not fit. Firmware splits it across pages, or shows the head and the tail with the middle elided, and the font is chosen so an eight cannot be read as a B. None of those constraints exist in an app layout, so an app layout shrunk into a device frame reads as wrong immediately.
What no mockup reproduces
- The signing. A key sits in a chip that never releases it. The device signs; the computer never sees the secret. A drawing has no chip.
- The physical confirmation. The security comes from a button press on a screen the host machine cannot alter. A rendered image has no press behind it.
- Seed generation and backup. Entropy, word lists, verification prompts. This tool never asks for a seed phrase and has nowhere to type one.
What this tool does simulate
One thing: the application screen. Tokens, quantities, unit prices, the accent colour, the avatar, the account name, with live market prices moving in the fiat column. It opens on the phone at its own address, ready for a listing image, a deck slide, a tutorial frame or a demo of software that has no data yet.
For a device product, that covers the companion app, which is where most of the design work sits. It is a mockup and it is presented as one. It holds nothing, connects to no chain and is not proof of a balance.
Documenting a device, in practice
Photograph the device for the physical steps, on a plain surface with the screen bright enough to survive the exposure. Use the project's emulator when you need the exact firmware wording. Redraw the small screen by hand when you need a clean asset — at that size it is an afternoon in a vector editor, not a rendering problem. Compose the phone side separately. It is a separate screen.
Questions
Can this tool draw a hardware wallet device screen?
No. It draws a mobile application screen, which you screenshot on your phone: 1179 x 2556 pixels on an iPhone 14 Pro. A device screen is a different object: often around 128 pixels across, sometimes monochrome, with a font picked so a 42-character address stays legible at that size. A phone layout squeezed into a device frame gets the type size wrong on sight.
What do people actually need when they look for a hardware wallet simulator?
Three different things. Firmware developers want an emulator that runs the device build, which some device projects publish themselves. Trainers and support teams want the device flow, which is best photographed or redrawn pixel by pixel. Everyone else is documenting the phone app that pairs with the device, and that is an ordinary application screen.
Why can a mockup not show a signing confirmation?
Because the confirmation is the point of the hardware. The device shows the address and amount on its own screen, from its own chip, and you press a physical button. An image of that screen carries none of it. A picture can illustrate the step in a tutorial; it can never stand in as evidence that a transaction was approved.
Compose the screen instead of describing it
Your tokens, your amounts, your accent — laid out in the browser, then opened on your phone at your own address. A mockup, and we never pretend otherwise.
- Unlimited tokens, amounts and accents
- Add it to your home screen; it opens like an app
- Live market prices that keep moving
- Your own address, mylarpwallet.com/you
Cancel in one click · Secure payment by Stripe · Try the free demo
Keep reading
- Guide: What a larp wallet isThe three meanings the sources confuse, where the line between a mockup and a deception falls, and what the product makes.
- Bitcoin wallet simulator: composing a BTC screen that reads rightA Bitcoin screen has three numbers that must agree: a quantity cut from eight decimals, a dollar value that moves every few…
- What a portfolio wallet simulator has to get rightA portfolio screen is a total, a change, and a sorted list. The sorting is what most mockups get wrong, and it is the first…
- Which tokens you can put in a wallet mockupFive marks are drawn from measurements. Everything else is an upload or a generated badge — and that limit is a…