Frontend correctness when every number is money.

Financial interfaces have no harmless data bugs.

I joined a Paperclip Labs engagement as the frontend engineer. Paperclip’s designers delivered detailed Figma work, and I turned it into production interfaces that held up under live market data, wallet connections, responsive layouts, and protocol rules.

Because users were moving money, loading states, stale data, token units, and transaction progress all had to be exact.

• Morpho Midnight. Frontend work on the beta interface for Morpho’s fixed-rate, fixed-term credit protocol before its public launch in July 2026.
• Morpho Blueprint. An open-source, white-label template for deploying branded lending and borrowing interfaces across EVM networks.
• Morpho Mini. A mobile-first Farcaster mini-app for Coinbase Wallet, covering supply, borrow, collateral, and rewards.

I built product screens and contributed to the shared component library used across the projects. The work included turning Figma variants into reusable components, handling dense financial data, and keeping desktop and mobile behavior consistent.

For Blueprint, I kept brand, chain, vault, and theme choices in configuration. Another team could run a different deployment without forking the product code.

• Presentation is part of correctness. Precision, loading order, stale data, signs, and unit labels can all change a financial decision.
• Configuration needs clear limits. Teams should be able to change brands and deployments without creating separate versions of the product.
• Shared code is not enough. Large codebases also need common naming, state handling, and review standards.