Product & Brand
All in Hype
A crypto trading product designed 0-to-1 and handed off in eight weeks: brand, Telegram bot, mini app, and web app.
Overview
A full trading product moved from blank file to handoff in eight weeks
All in Hype was a trading terminal for the Hyperliquid ecosystem. Users could place spot, perpetual, and margin orders through Telegram, then move to a web app for charting, portfolio tracking, account management, and advanced control. There was no brand, interface, or component system when I started.
I was the only designer. I designed it 0-to-1 in eight weeks across four surfaces, brand, Telegram bot, mini app and web app, plus the component system underneath all of them. I completed the design work and handed off to the client's development team in July 2025.
The impact
The project went from no brand or interface to a working trading product in eight weeks. Telegram and web handled different jobs while sharing the same rules and component system.
8 weeks
Time to handoff
Started in May 2025
3+
Shipped surfaces
Brand, bot, mini app, web app
3
Trading modes
Spot, perpetual, and margin
Problem
Telegram speed and desktop control had to feel like the same product
Active traders wanted fast commands, advanced orders, live positions, and full control. Referred users needed a clear setup path and enough explanation to trust a trading product inside Telegram.
The work also crossed three interaction models. The Telegram bot used messages and inline keyboards. The mini app supported richer setup and account tasks. The desktop product needed charts, portfolio views, and advanced trading controls. I had about two months to define the brand and make those surfaces feel like one product.
A founder-led dual-wallet requirement added more risk. Users needed to understand a funding wallet, a trading wallet, transfers between them, private-key export, and recovery before placing a trade.
Design
Five surfaces needed one system and different interaction rules
The PRD came with three rough user profiles. I checked those assumptions through written responses from roughly 20-30 intended users, Discord chats, town halls, and a few voice discussions. I used that input to set priorities across the bot, mini app, and web product.
Active traders wanted short order flows and a clear view of open positions. DeFi users cared about account control, recovery, and fee transparency. Referred newcomers needed more help between account creation and their first trade.
Giving Telegram and web different jobs
I rejected copying the desktop interface into Telegram. The bot needed short actions, clear confirmation, and recovery from bad input. The web app carried charts, open positions, account controls, rewards, fee levels, and multi-panel trading.
This split let users place a fast order inside Telegram and move to the web when they needed more control.
Pushing back on the dual-wallet model
I recommended one wallet because it reduced setup and recovery risk. The founder kept the two-wallet requirement.
I reviewed the small number of products using a similar model and set two rules. Each wallet needed one fixed role, and every transfer needed a visible state. The funding wallet handled deposits and withdrawals. The trading wallet handled market exposure.
I kept setup status visible, placed private-key export behind warnings, and covered recovery when a transfer stopped halfway through. The founder made the product call. I made the chosen model understandable.
Splitting quick and advanced trading
I created Lite and Advanced modes for the web product. Lite focused on the chart, price, position, and fast order entry. Advanced used a multi-panel setup for users handling more signals and order details.
Reducing the glass effect before development
The founder wanted a glass-heavy style after Apple's Liquid Glass announcement. I designed the first direction, then recommended reducing the effect before implementation. A slow interface would hurt a product built around fast trades.
The final product kept the depth, hierarchy, teal accents, and component structure with less blur and transparency. Developers applied that reduction in production.
Building one system across five surfaces
I built the brand first. The triangle mark took cues from casino chips, supported by a dark base, teal accents, typography, and icons. Early approval gave the landing page, Telegram bot, mini app, and web product one visual direction.
The MVP supported spot market and limit orders, perpetual futures, margin orders with cross and isolated modes, individual and bulk cancellation, portfolio and position tracking, guided Telegram flows, single-line commands, and Lite and Advanced web modes.
I also designed the waitlist page, launch site, rewards, referrals, account model, and fee levels across desktop and mobile. The component library, color tokens, type rules, and reusable product patterns grew alongside the screens.
Reflection
Turning a disputed wallet model into a clear product
All in Hype went from an empty file to a launched MVP in about eight weeks. I delivered the brand, waitlist and launch pages, Telegram bot, Telegram mini app, web product, dual-wallet onboarding, trading flows, two web modes, rewards, fee levels, and the shared design system.
The founder's security team reviewed the implemented wallet flow after handoff. I had already made each wallet's purpose, transfer states, private-key export warning, and recovery path explicit in the interface.
The founder's dual-wallet request became the hardest product decision in the project. I argued for one wallet, then shaped the two-wallet model into fixed roles so users always knew where funds sat and what each transfer did.
