Product Design & Front-End Proposal

Capacitor

Prepared by: Gloww Studio Date: July 5, 2026 Valid for: 14 days
Prepared exclusively for the Capacitor team. This proposal covers the redesign of seven core screens and a production front-end build with full interaction design, so the mobile app ships calm, credible, and delightful for the one-month alpha sprint.

Capacitor deserves an app as sharp as its thesis

( 01 )

Capacitor turns live news into tradeable moments, on your own or through an AI agent wired into venues like Polymarket. With $50k committed to the mobile sprint, the app now has to earn trust in the first session, not just function.

( 02 )

We already know each other's pace from past work, so this proposal skips the pitch and goes straight to the plan: seven screens redesigned and shipped as a real front end, every micro-interaction covered, so the app is a delight to use, not just a set of designs.

A sharp thesis, quietly undermined by the interface.

( 01 )

The feed overwhelms

"It is a little bit too much, too much information." Every card is trying to be the detail page. Density is killing decisiveness.

( 02 )

Sources carry no weight

A Bloomberg headline and an anonymous account currently look identical. Without visual trust signals, every recommendation feels arbitrary.

( 03 )

The agent chat is a dead end

Users leave the conversation to check open positions or place a trade. The most differentiated feature in the app has the least capable surface.

( 04 )

Onboarding doesn't convert

The goal is deposit + first trade in session one. Nothing in the current flow is engineered toward that moment.

( 05 )

Readability fights the trader

Contrast and hierarchy issues run through the app, the telltale marks of Figma Make output without a designer's pass. Numbers you trade on should never need a squint.

( 06 )

The workflow burns money

~$600 in Figma Make credits and three plan upgrades to get here. Iteration speed is currently priced per prompt.

Calm surfaces, credible signals, one continuous flow to the first trade.

( 01 )

A feed that breathes

Strict card hierarchy: event, source, expected move, one action. Everything else moves to the detail page, where depth is a choice instead of a burden.

( 02 )

Trust, made visible

Source logos, a credibility score, and community signal in one compact system, so a Bloomberg event reads differently from a rumor at a glance.

( 03 )

An agent chat with hands

Rich inline components: position cards, trade confirmations, P&L snapshots inside the conversation. Check, adjust, and execute without ever leaving the chat.

( 04 )

Onboarding to first trade

The flow is choreographed toward one outcome: funded account, first position, first session. Every screen either moves toward it or gets cut.

( 05 )

Readable at trading speed

Contrast-checked color, tabular numbers, and a type hierarchy tuned for glanceable decisions, in daylight and at 2am. Your existing brand, applied properly to the product.

( 06 )

A workflow that compounds

A Capacitor design system wired into a Claude + Figma workflow, replacing per-credit Figma Make iteration. Your devs build against tokens, not screenshots.

Scope of work. Four weeks to alpha-ready.

Phase 01( Week 1 )
  • Full app audit
  • Brand & contrast fixes
  • Design system setup
  • Feed card logic
Foundation
Phase 02( Week 1–2 )
  • Seven screens designed
  • Trust-signal system
  • Agent chat components
  • Onboarding flow
Screen design
Phase 03( Week 2–4 )
  • Production front-end build
  • Micro-interactions
  • Motion & transitions
  • Device QA
Front-end build
Phase 04( Week 4 )
  • Polish pass
  • Handover to devs
  • Claude + Figma workflow setup
Handover

Seven screens. Designed, built, and delightful.

( 01 )

Onboarding & funding

From install to funded account, engineered for the first-session trade.

( 02 )

Feed

The calm, scannable event stream with trust signals and one clear action per card.

( 03 )

Event detail

The full story: sources, expected upside, market context, and the trade sheet.

( 04 )

Trade flow

A confident order sheet: amounts, odds, confirmation, and the post-trade moment.

( 05 )

Agent chat

Conversation with rich inline components: positions, confirmations, and P&L in the thread.

( 06 )

Positions & portfolio

Open positions, history, and performance at a glance.

( 07 )

Profile & settings

Account, venues, agent permissions, and notifications.

( + )

Production front end, not a Figma file

Every screen ships as working front-end code with the micro-interactions built in: press states, transitions, loading choreography, haptic-ready feedback. What you review is what your users touch.

Investment

UI/UX design, 7 screens

Feed, detail, trade, chat, onboarding, portfolio, profile

Front-end build + interaction design

Production code, all micro-interactions covered

Design system + agent workflow

Capacitor tokens in Gloww, Claude + Figma setup
Total
$3,500
( Payment schedule )
  • 50% on kickoff / $1,750
  • 50% at handover / $1,750
One flat fee for the full sprint. Design and build together, priced as one engagement. Alongside the fee, the 0.25% equity and token allocation discussed on our call apply to this engagement.
Gloww

Four steps to get started

The sprint clock starts the day the deposit lands. Alpha in a month is realistic, if we start this week.

Step 01

Say yes

Reply with your approval or any final questions.

Step 02

Send the deposit

A 50% deposit ($1,750) locks the sprint into this month's schedule.

Step 03

Share access

Current build, brand files, and a channel with your devs for the front-end handshake.

Step 04

Kickoff

We book the kickoff session within the week and Phase 01 begins.

( Let's build )

Let's ship the app Capacitor's alpha deserves.

Send a message Approve & kick off
■  This proposal is valid through July 19, 2026.
( 01 )What exactly counts as a "screen"?▾
One of the seven core surfaces listed above, including its key states: empty, loading, error, and success. Small variations (a filter sheet inside the feed, a confirmation step inside the trade flow) are part of the screen, not extras.
( 02 )What does "front end included" mean in practice?▾
You receive working front-end code, not just Figma files. Components, motion, and micro-interactions are implemented and QA'd on device, then handed to your devs to wire into the trading logic and backend.
( 03 )How many revision rounds are included?▾
Two structured rounds per phase, async over Loom and shared boards, the same rhythm as our previous work together. Because design and build are one engagement, feedback lands once instead of twice.
( 04 )What happens to the Figma Make workflow?▾
It retires. The Capacitor design system lives in Gloww's setup with a Claude + Figma workflow, so future iterations reference real brand tokens instead of burning credits per prompt.
( 05 )Can this really land within the one-month alpha window?▾
Yes. That's why design and build overlap in the schedule. Screens move into code as they're approved, so week four is polish and handover, not the start of development.