Greg Hadała

Case study

FogoHead of Design2025 — 2026

Fogo Sessions

Session-based wallet for Fogo: one approval instead of constant wallet prompts and gas fees — designed in two weeks.

Fogo Sessions for Fogo
Client
Fogo
Role
Head of Design
Timeline
2025 — 202613 months
Skills
AI Prototyping, AI-Augmented Workflows, Claude Code, Web3 UX, Design Leadership, Design System, Product Design, UX Design, UI Design

Fogo Sessions is a session-based sign-in layer for the Fogo blockchain. It removes the repeated wallet approvals and gas fees that slow down DeFi trading: users connect once, approve a scoped session, and trade freely until it expires.

The design challenge was turning a technically complex system — scoped permissions, auto-expiry, gasless transactions, support for any wallet — into a three-step flow (connect, approve once, use) that feels invisible yet safe. Plain-language permission requests, clear boundaries and visible trust signals carry that. Design took two weeks; implementation one month.

Features

  • Connect a wallet

    Sign in with a wallet you already have. Phantom, Trust and MetaMask are detected, any Solana- or Fogo-compatible wallet works, and there is a path for people who have none.

  • New session

    Starting a session is the whole onboarding: no seed phrase to store. The app asks by name, access can be limited to four tokens, and unlimited access is called out before anything starts.

  • Wallet

    Familiar patterns first: total balance, send, receive and get tokens, then the token list with each token's session allowance. The banner keeps the session expiry and access level in view.

  • Token detail

    One token in depth: price and hourly change, a chart with time ranges, the same three actions, and holdings beside the session limit for that token.

  • Activity

    A day-by-day log of transfers, searchable, with a plain empty state for a quiet day. Send and receive stay one tap away, without leaving the session.

  • Continue on mobile

    Scan the QR code to pick the same session up in a mobile browser, so what starts on a desktop can be finished on a phone.

Challenges

  1. 01

    Designing against moving requirements

    Session scope, expiry rules and the permission model were still being defined while I designed, so I used flexible patterns that could absorb spec changes without rework.

  2. 02

    Two weeks from brief to handoff

    No room for extended discovery, and the design system was built from scratch in the same window. I designed the critical path (connect → approve → trade) first, handled edge cases alongside implementation, and chose established patterns over novel UI to keep engineering guesswork to a minimum.

  3. 03

    No time for usability testing

    Instead, I relied on heuristic reviews, DeFi UX conventions and fast internal feedback, and kept the flow linear and the interaction surface small to reduce risk.

Next case study

Insights Hub

Pyth Network

Analytics for Pyth Network: 2,800+ price feeds and 125+ publishers made searchable and comparable — designed and shipped in 8 weeks.

Read on