GoodBuild

Blog · MiniPay apps

Mobile-First Web3 Apps: Build for Phones and Low Data

For a large part of the world, the first computer is a phone on a limited data plan. A web3 app built for that person looks different from one built for a developer's laptop.

· 2 min read

Design rules

  • One main action per screen. The thing the user came to do, large and reachable with a thumb.
  • Plain words. Say "send" and "balance", not "transact" and "on-chain state".
  • Show money clearly. Amount, token and recipient before every signature.
  • Big tap targets. At least 44 pixels high.

Performance rules

  • Keep the page small. Every library is a cost the user pays in data.
  • Avoid autoplay video and large photos.
  • Show something useful before the chain data arrives, then fill it in.
  • Cache what does not change.

Wallet rules

  • Inside a wallet's own browser, like MiniPay, connect without asking.
  • In a normal phone browser, offer the wallet apps people actually have, and a WalletConnect option.
  • Say what to do if no wallet is found.

Games and phones

Games are a good test. They need to run smoothly with touch controls and make sound only after a tap. GoodBuild's 2D game kit builds canvas games without a heavy game engine for this reason: a few kilobytes, not megabytes.

Ask the builder for it

When you describe your app in GoodBuild, say "phone first" and name the one action. Then open the preview at phone width and judge it with your thumb, not your mouse.