How subbed works

1. Overview

The core idea is intentionally simple: the creator identity comes first. Tokens are represented as being attached to a Twitch handle, making the creator relationship visible throughout Explore, Analytics, Payments, and Launch.

2. Launch flow

The launch screen uses three clear sections: creator, token, and optional first buy. The right-side preview updates immediately so the user can see how the token will appear before submitting.

• Choose a Twitch creator or type a handle.
• Set name, ticker, description, artwork, and optional links.
• Choose an optional first-buy amount.
• Submit the final action to the future Pons integration.

3. Creator linking

Creator identities are represented by Twitch handles and can later be resolved against the Twitch API if you choose to add authenticated Twitch data. The UI is already shaped for name, avatar, handle, follower count, and linked tokens.

4. Pons handoff

The current build does not invent a contract or transaction API. It provides a clean front-end boundary where the actual Pons launch request can be wired once the exact interface is confirmed.

5. Wallet connection

The header includes a working demo connection state. Replace the local UI toggle with your preferred EVM connector when the on-chain pass begins.

6. Front-end states

Search, navigation, creator selection, image upload preview, form controls, sorting, filtering, mobile navigation, modal states, and scroll reveals all work in the current project.

7. Next integration pass

Once you are happy with the front-end, the clean next step is to wire real wallet auth, the Pons launch call, chain reads, and real Twitch creator lookup—without changing the overall interface.