Meteor Wallet | Senior Frontend Developer Case Study | Kelvin Hong

Product context

Designing clear interfaces for irreversible actions

As a non-custodial wallet, Meteor Wallet interfaces directly with the blockchain, requiring the client application to coordinate data fetching, state management, and transaction construction without a centralized backend intermediary. Wallet products combine complex state, unfamiliar terminology, hardware integrations, third-party applications, and irreversible user actions. The frontend must explain what is happening without hiding what the user is authorizing.

Meteor Wallet overview interface showing account balance and main controls — Wallet overview: Build with secure storage for private keys and local state encryption.

Architecture

Sharing product logic while respecting platform differences

I built Meteor Wallet v2 across Android, iOS, web, and browser extension from a shared React Native foundation. Each platform required different handling for navigation, storage, permissions, specific platform constraints.

Implementation

Authentication, signing, and wallet integrations

I implemented passkey authentication, transaction signing, WalletConnect, Ledger support, on-chain data decoding, third-party application integrations, and production monitoring. I also maintained and improved MyNearWallet for the wider NEAR ecosystem.

Token send interface with address input and gas settings — Token transfer flow designed to prevent client-side double-spending by disabling submit triggers and managing precise transaction nonces.

Token swap interface showing conversion rate and slippage tolerance — Integrated decentralized exchange aggregators directly into the interface with real-time slippage calculations and price impact warnings.

Data Resilience

Consolidating fragmented blockchain transaction records

Displaying a complete, readable transaction history is a core challenge in decentralized wallets. Transaction logs are spread across blocks, and third-party indexing APIs are notoriously unreliable.

To address this, we completely decoupled from external indexing services by building our own custom indexing backend. For granular, real-time transaction details, the client queries raw blockchain RPC endpoints directly, caching each transaction locally on the device so it only hits the RPC node once.

Transaction history page showing incoming and outgoing transactions — Unified transaction history log with local-first device caching, powered by a custom indexer and direct node RPC querying.

Product Growth

Incentivizing engagement with embedded gamification

Gamified reward dashboard with interactive achievements — In-app gamification dashboard designed to drive user retention and engagement.

Daily task check-in interface with animated rewards — Daily streak check-in flow encouraging exploration of various wallet features.

End-to-End Build

Canton Network Wallet

I engineered a privacy-focused wallet build end-to-end (from UI to backend) specific to the Canton network. Due to the network's privacy requirements, transaction routing and data queries are handled through our custom backend rather than directly on-chain. This build included the main wallet interface, transaction history detail, and a passkey authentication flow with a fallback password mechanism for devices that do not support passkeys.

Canton wallet interface — Wallet dashboard interface designed for the Canton network.

Canton transaction history details — Transaction history details showing full on-chain transaction metrics.

Canton passkey setup page — Passkey enrollment interface with dynamic password fallback support.

Open Source

Maintaining MyNearWallet

I maintained MyNearWallet, an open-source web wallet that was the most widely used wallet in the NEAR Protocol ecosystem, supporting core web wallet infrastructure and ecosystem growth.

Process

A controlled AI workflow

AI-assisted workflows supported research, implementation, code review, security scanning, and documentation. Every output was reviewed against wallet behavior, security requirements, and production constraints.