iOS & Android · Case Study

InReserve

Your tokens. Your keys. One wallet that handles every Ethereum standard — ERC20, ERC721, ERC1155 and ERC875 — in a single portfolio view, with a built-in DApp browser and multi-network support.

Chain activity
InReserve wallet portfolio
DApp browser
🏭IndustryCryptocurrency & Web3
📱PlatformsiOS (Swift), Android (Kotlin)
🛠️ServicesMobile App Development, Blockchain Integration, UX & UI Design, Security Architecture, Deployment

We built InReserve for users who want full control over their digital assets without juggling multiple apps. The wallet normalizes ERC20 currencies, ERC721 collectibles, ERC1155 gaming tokens and ERC875 tickets into a single portfolio view.

4ERC Standards
2Native Platforms
100+DApps Accessible
App screens

Every screen, designed for clarity.

Portfolio view with token balances
PortfolioAll tokens, real-time prices
Transaction history
ActivityTransaction history
DApp browser
DApp BrowserOpenSea, Uniswap, more
Network switching
NetworksMulti-chain switching
Import wallet
ImportSeed, keystore, private key
Discover DApps
DiscoverExplore decentralized apps
01

Multi-token support

ERC20, ERC721, ERC1155 and ERC875 tokens — currencies, collectibles, gaming items and tickets — all live in one unified feed. No separate tabs, no juggling balances across apps. Every asset surfaces with its real-time price, contract details and quick-send actions.

Multi-token support
02

Secure key management

Private keys are generated and stored on-device inside the secure enclave — they never leave the phone or touch a server. Every outbound transaction is gated by biometric MFA, and seed phrases can be backed up to encrypted keystore files or imported from any standard wallet.

Secure key management
03

Built-in DApp browser

Connect to OpenSea, Uniswap, PancakeSwap and hundreds of decentralized apps without ever leaving the wallet. WalletConnect and injected web3 are supported out of the box, so signing, swapping and minting feel as native as a browser tab.

Built-in DApp browser
04

Multi-network support

Switch between Ethereum, BSC, Polygon and Avalanche with a single tap — one wallet, every EVM-compatible chain. Custom RPCs, testnets and gas-fee presets are configurable per network, so power users get full control without sacrificing the simple default experience.

Multi-network support
Built with

Native apps. Decentralized infrastructure.

Mobile
Swift (iOS)Kotlin (Android)
Blockchain
Ethereum LedgerWeb3 (Open-source)
Storage
Blockchain-native
Challenges & Solutions

Hard problems in blockchain security.

01
The problem

Security had to meet the highest bar in the industry. Users trust a wallet with real money. Encryption, key management, seed phrase handling and authentication all had to be airtight from day one, not bolted on after launch.

Our fix

We implemented industry-standard encryption protocols with secure enclave storage on both iOS and Android. Private keys never leave the device. Seed phrase recovery uses a guided flow with verification steps. Multi-factor authentication adds a second layer before any outbound transaction.

02
The problem

The wallet had to support four different ERC token standards in one interface. ERC20 fungible tokens, ERC721 NFTs, ERC1155 multi-tokens and ERC875 event tickets each behave differently on-chain. The UI had to make them all feel like the same experience.

Our fix

We built a unified token engine that normalizes all four ERC standards into a single data model. The UI renders balances, transaction history and transfer flows identically regardless of the underlying standard. Thanks to that backend development approach, adding a new token type is a configuration change, not a UI rewrite.

03
The problem

The app had to serve beginners and experienced traders equally. A first-time crypto user needs guidance and simplicity. A power user needs speed, network switching and DApp access. This is one of the harder problems in mobile app development: one interface had to flex across both without feeling dumbed down or overwhelming.

Our fix

We designed a progressive interface that starts simple and reveals power features as the user grows. New users see balances and send/receive. Experienced users unlock network preferences, DApp browsing and advanced transaction settings. The same app, two levels of depth.

FAQ

Questions before the first block.

Building a crypto wallet app typically costs between $80,000 and $250,000 in 2026. A basic single-chain wallet with send, receive and key management starts near $80,000. A production wallet with multi-chain support, DApp browser, NFT rendering, multiple ERC standards and advanced security usually lands between $150,000 and $250,000.

Private keys in a mobile wallet are encrypted using the device's secure enclave (iOS) or Android Keystore. The key never leaves the device in plaintext. Seed phrase recovery adds a backup path. Multi-factor authentication gates outbound transactions. Together these layers protect assets even if the device is compromised.

A modern Ethereum wallet should support at minimum ERC20 (fungible tokens like USDT), ERC721 (NFTs like collectibles), ERC1155 (multi-tokens used in gaming) and ERC875 (event tickets and attestations). A unified token engine normalizes all four standards so the user sees one consistent interface regardless of the underlying type.

A DApp browser in a wallet embeds a WebView that injects a Web3 provider into every page. When a decentralized app requests a transaction, the wallet intercepts it, shows the user the details and signs the transaction with the stored private key. The user never leaves the wallet to interact with OpenSea, Uniswap or any other DApp.

Native development (Swift for iOS, Kotlin for Android) is the safer choice for a crypto wallet. Secure enclave access, biometric authentication and hardware-backed key storage are platform-specific features that work most reliably through native APIs. Flutter can work for the UI layer but the security-critical parts should stay native.

A blockchain wallet app with native iOS and Android builds typically takes 5 to 8 months. Expect 3 to 4 weeks of security architecture and discovery, 16 to 24 weeks of development covering wallet flows, token rendering, DApp browser and security features, 2 to 3 weeks of security audit and beta testing and 1 to 2 weeks for store submissions.

Multiple networks are handled through a network preferences layer that lets users toggle between Ethereum, Binance Smart Chain, Polygon, Avalanche and other EVM-compatible chains. Each network has its own RPC endpoint and chain ID. Token balances and transaction history load per-network but the UI presents them in a unified feed.

A crypto wallet needs at minimum a smart contract audit (if applicable), a penetration test covering the mobile app and API layer, a key management review covering storage, backup and recovery flows and a dependency audit of all open-source Web3 libraries. Most teams engage a third-party security firm for an independent assessment before going live.

Start your project

Building a crypto wallet or Web3 app?

We build native blockchain apps with secure key management, multi-token support and DApp integration.