Mobile Wallets Reviewed for Actual Daily Use

I used mobile wallets as my only wallet for three months, with real amounts, on purpose. Here is what that surfaced that a feature list does not.

What went wrong in practice

Backup prompts that appear after funding. Two of the wallets I tried allowed me to receive funds before completing the seed phrase backup. That ordering is backwards and it is how people end up with funded wallets they cannot recover.

Network selection buried in settings. Sending a token on the wrong network is the most common expensive mistake, and several interfaces make the network a setting rather than a visible field on the send screen.

Fee estimates that were consistently wrong during congestion. One wallet’s suggested fee produced stuck transactions three times in a busy week. The speed-up function worked, at additional cost each time.

Token display requiring manual addition. Receiving a token the wallet does not recognise shows nothing, which produces a genuinely alarming ten minutes for anyone who has just sent a large amount.

Biometric unlock that did not protect the seed phrase view. On one wallet, viewing the recovery phrase required only the device unlock rather than a separate authentication. Anyone with access to an unlocked phone could read it.

That last one is the only finding I would call a security failure rather than a usability complaint.

What worked well

Transaction simulation, where present. Same as on desktop. It caught one approval I had misread.

Address book entries with labels. Removes the need to copy from transaction history, which defeats address poisoning entirely.

Clear separation between accounts. Wallets making it easy to run a separate account for unfamiliar contracts encourage the practice that matters most.

QR-based sending. Fewer opportunities for clipboard substitution.

The threat model for a phone

A mobile wallet’s keys sit on a device that also runs everything else you install, connects to networks you do not control, and can be lost or taken.

That is not an argument against using one. It is an argument about size: a mobile wallet should hold what you would carry as cash.

The specific risks, in order of how often they actually cause losses: phishing sites visited on the phone, malware from sideloaded applications, cloud-synced screenshots of the recovery phrase, and physical device compromise.

Only the last one is really about the phone. The rest apply anywhere.

What I would look for

1. Backup enforced before the wallet can receive funds
2. Network shown on the send screen, not in settings
3. Separate authentication to view the recovery phrase
4. Transaction simulation
5. Address book with labels
6. Hardware wallet pairing, for when the balance grows

The arrangement I settled on

A mobile wallet holding a small spending balance, a hardware wallet for the rest, and a working balance at a platform we ran a full withdrawal through for buying.

Three tiers, each sized by what losing it would mean. The mobile wallet is the one I would be irritated to lose and not much more than that.