Flow: Design Brief

Flow is a platform where anyone can earn money by contributing knowledge and work, powered by a personal AI that represents them and handles the complexity on their behalf.

We are designing something genuinely novel to feel immediately familiar. Most users will not understand Bittensor, may be skeptical of AI agents, and have never used a decentralized marketplace. The UI has to do the heavy lifting of making all three feel obvious & very intuitive.

The landing page has one job: answer "what's in it for me?" within 5 seconds. Not "we're building decentralized AI infrastructure" but "earn money doing what you're already good at. Your AI handles the rest."

The hero should show a real task, a real payout, a real person. Social proof from day one matters enormously here, especially for the African market where trust is earned through word of mouth, not just brand.

Key design note: Let's avoid crypto/AI jargon on any public-facing surface.

Keep it frictionless. Email or phone number to start, phone number first given the target market. No wallet setup on day one. No crypto knowledge required.

The onboarding asks three simple questions:

That's it. Jarvis takes those answers and builds the foundation of their profile. The user never sees "you're creating a knowledge base." They see "we're setting up your assistant."

Priority functionality: Phone/email auth, Google/LinkedIn SSO, skill tag selection (pre-populated list), optional portfolio upload.

This is the most critical UX moment in the entire product. If users don't understand or trust Jarvis, nothing else works.

Frame it as: "Meet your work assistant. The more it knows about you, the better work it finds you and the more it can handle on your behalf."

Introduce Jarvis through a short conversation, not a form. It asks about what they've done before, what they're proud of, what they want to earn. It feels like talking to a smart recruiter. Behind the scenes, it's populating their private knowledge base.

Then show them what Jarvis can do for them in plain terms:

Start Jarvis on low autonomy, it suggests, the user approves. Autonomy increases as trust builds. This is not a settings toggle; it's something that happens naturally as they use the platform.

Priority functionality: Conversational onboarding flow, knowledge base built from conversation + file/link uploads, Jarvis "capabilities preview" screen, notification preference setup.

The feed is the product here. It needs to feel like a smart inbox, not a job board. Jarvis has already filtered and ranked tasks before the user ever opens the app.

Each task card shows: what the work is, how long it will take, what it pays, and why Jarvis thinks it's a match. One tap to accept, one tap to decline. No lengthy application process.

For first-time users, the first task should feel almost too easy, a small, well-scoped task that builds confidence and gets them their first payout. The apprenticeship model from the doc maps directly here: complex tasks are decomposed and junior contributors get the appropriate slice.

The work itself should happen inside Flow where possible. Document editing, research submission, feedback forms, keep the user in the product rather than bouncing them to Google Docs or email chains. Jarvis handles communication with the task poster.

Task completion triggers a simple review flow. Did it meet the brief? Any feedback? This feeds the reputation system without the user ever thinking about reputation systems.

Priority functionality: Personalised task feed with Jarvis explanations, task detail view with clear scope/pay/timeline, in-app submission, messaging with Jarvis as intermediary, task history and earnings tracker.

This is where we either win or lose trust permanently. Payment must be:

The Bittensor/token layer sits underneath this entirely. The user sees "₦4,500 earned" not "0.003 TAO." The conversion and wallet mechanics are abstracted. Over time, as users become more comfortable, you surface the option to hold earnings as tokens, stake, and participate more deeply but this is a later chapter.

Priority functionality: Earnings dashboard, mobile money withdrawal, payment confirmation notifications, cumulative earnings history.

Users shouldn't encounter Bittensor as a concept until they're already earning and engaged. Then it's introduced as an answer to a natural question they'll have: "Can I earn more?"

Frame it as:

Introduce the token layer through a "Flow Score", a visible, growing number that represents their cumulative contribution to the network. Flow Score is about reputation, a running total of user's overall contribution to the platform over time, which eventually unlocks token rewards. It's not per-task pay, it's more like a loyalty/status layer that sits on top of earnings.

Priority functionality: Flow Score dashboard, token wallet setup (guided), token-to-cash conversion, "sponsor a learner" feature (later phase), staking interface (later phase).