ONE by ON3 — UX Flow Map

A complete visual representation of every current user journey in the ONE by ON3 application. Mapped from the actual source code — routes, pages, components, entities, actions, workflows, and backend functions. This is documentation only; no functionality has been modified.

11 Journey Lanes
165 Flow Nodes
33 Routes
4 Workflows
19 Backend Functions

Legend

Page / Screen
User Action
Decision
Automated (Workflow / Webhook)
External Service
Entry / Exit
Data Entity

1 · Authentication & Onboarding

13 nodes
3 paths

How a visitor joins, verifies, and enters the platform. Every new session requires OTP verification.

Path 1

Visitor

Entry / Exit
Lands on

Welcome / Landing

/welcome

Page / Screen
Join Free / Sign In

Platform Auth (Email / Google / Apple)

User Action
New user

Onboarding Wizard

/onboarding

Page / Screen
Customer intent → auto-approved

Home (Approved)

/

Page / Screen

Path 2

Returning User

Entry / Exit

Platform Login

User Action

Post-Login OTP Gate (verifyOtp · every session)

User Action
OTP verified

Home

/

Page / Screen

Path 3

Provider Intent Selected

Decision
provider_status: pending

Pending Approval (profile_status: submitted)

/pending-approval

Page / Screen
Admin alerted

Admin Reviews Profile

⚙ Admin Alert – New User (app_user_auth trigger)

Automated (Workflow / Webhook)
Admin approves

Home (profile_status: approved)

/

Page / Screen

2 · Service Discovery (Customer)

14 nodes
3 paths

How customers find services — through browsing, AI natural-language search, the catalogue, or by registering unmet demand.

Path 1

Home

/

Page / Screen
Browse

Browse Services

/services

Page / Screen
Ask AI

Natural Language Search (matchService AI)

User Action
AI-matched categories

Filtered Results

Page / Screen
Tap card

Service Detail

/services/:id

Page / Screen

Path 2

Home / Services

/

Page / Screen
Full Catalogue

Professional Catalogue (3-level taxonomy)

/catalogue

Page / Screen
Filter

Catalogue Results

Page / Screen
Select service

Service Detail

/services/:id

Page / Screen

Path 3

No Providers Found

Decision
No Providers Available

Services Wanted Feed (Community)

/community

Page / Screen
Notify Me / Request

Register Demand (ServiceDemand entity)

⚙ ServiceDemand

Data Entity
Created

Demand Status: open

⚙ ServiceDemand.status

Data Entity
Listing approved later

Auto-Notify on Match (matchDemandToListing)

⚙ Match Demand to New Listing (entity trigger on ServiceListing update → approved)

Automated (Workflow / Webhook)

3 · Booking & Payment Flow

19 nodes
4 paths

The core transaction: agreement acceptance → Stripe Checkout → webhook confirmation → document generation. Provider must have Stripe Connect set up.

Path 1

Service Detail

/services/:id

Page / Screen
Loads

checkProviderPaymentReady (stripe_payments_enabled)

⚡ checkProviderPaymentReady

Automated (Workflow / Webhook)
payments_ready = true

Book & Pay

User Action
Open modal

Request Modal (hours, price, message)

User Action
Continue

Agreement Acceptance Gate (AgreementAcceptance entity)

⚙ AgreementAcceptance

User Action
Accept → stripeCreatePayment

Stripe Checkout (direct charge on Connected Account)

External Service

Path 2

checkout.session.completed

⚡ stripeWebhook

Automated (Workflow / Webhook)

ServicePayment: paid

⚙ ServicePayment

Data Entity

ServiceRequest: paid

⚙ ServiceRequest

Data Entity

generateBookingDocuments (PDF Agreement + Receipt)

⚡ generateBookingDocuments

Automated (Workflow / Webhook)

Branded Emails + Attachments (SendEmail)

Automated (Workflow / Webhook)
Redirect back

My Requests (stripe=success)

/my-requests

Page / Screen

Path 3

checkout.session.expired

⚡ stripeWebhook

Automated (Workflow / Webhook)

ServicePayment: cancelled

⚙ ServicePayment

Data Entity

ServiceRequest: cancelled

⚙ ServiceRequest

Data Entity
Redirect back

My Requests (stripe=cancel)

/my-requests

Page / Screen

Path 4

payment_intent.payment_failed

⚡ stripeWebhook

Automated (Workflow / Webhook)

ServicePayment: failed

⚙ ServicePayment

Data Entity

Notification: Payment failed

⚡ createNotification

Automated (Workflow / Webhook)

4 · Service Request Lifecycle

28 nodes
5 paths

The full state machine of a booking — from request through acceptance, completion, review, and dispute. Both customer and provider sides shown.

Path 1

Request: pending

⚙ ServiceRequest.status

Data Entity
Provider notified

Provider: My Requests (Received tab)

/my-requests

Page / Screen

Accept

User Action

Request: accepted

⚙ ServiceRequest.status

Data Entity

Provider: Mark Complete

User Action

Request: provider_completed

⚙ ServiceRequest.status

Data Entity

Path 2

Request: paid

⚙ ServiceRequest.status

Data Entity
Payment confirmed

Customer: My Requests (Sent tab)

/my-requests

Page / Screen

Customer: Mark Complete

User Action

Request: requester_completed

⚙ ServiceRequest.status

Data Entity
Other side?

Both sides completed

Decision
Yes

Request: completed

⚙ ServiceRequest.status

Data Entity
Auto

Award Credits + Green Points (Wallet + Transaction)

Automated (Workflow / Webhook)

Path 3

Request: completed

⚙ ServiceRequest.status

Data Entity
Leave review

Review Dialog (rating + text)

User Action
Submit

Review Saved (requester_rating / provider_rating)

⚙ ServiceRequest

Data Entity

Booking Documents (Agreement + Receipt PDFs)

⟨BookingDocuments⟩

Page / Screen

Path 4

Request: accepted / completing

⚙ ServiceRequest.status

Data Entity
Dispute

Dispute Dialog

⟨DisputeDialog⟩

User Action

ServiceDispute created

⚙ ServiceDispute

Data Entity

Request: disputed

⚙ ServiceRequest.status

Data Entity
Admin reviews

Admin: Disputes tab

/admin

Page / Screen

Path 5

Provider: Decline

User Action

Request: cancelled

⚙ ServiceRequest.status

Data Entity

Provider: Ask More Info

User Action

Request: info_requested

⚙ ServiceRequest.status

Data Entity
Customer sees

Customer: Reply with Info

User Action
Reply sent

Request: pending

⚙ ServiceRequest.status

Data Entity

5 · Provider Journey

22 nodes
4 paths

How a member becomes a provider: Stripe Connect onboarding, listing creation, approval, and demand-matched opportunities.

Path 1

Profile

/profile

Page / Screen
Provider intent

Provider Payments Card

⟨ProviderPaymentsCard⟩

User Action
Set up payments

stripeOnboarding (Stripe Connect)

⚡ stripeOnboarding

External Service
Stripe redirect

Stripe Connected Account

External Service
Capabilities update

account.updated webhook

⚡ stripeWebhook

Automated (Workflow / Webhook)
card_payments active

stripe_payments_enabled: true

⚙ User

Data Entity

Path 2

Create Listing

/create-listing

Page / Screen

Listing Form (title, desc, category, compensation, credentials)

User Action
Service not in catalogue

Propose New Service (screenProposedService AI)

⚡ screenProposedService

User Action

Submit for Review

User Action

ServiceListing: pending

⚙ ServiceListing.status

Data Entity
Auto

Admin Alert – New Listing

⚙ Admin Alert – New Listing (entity trigger on ServiceListing create)

Automated (Workflow / Webhook)

Path 3

Admin: Listings tab

/admin

Page / Screen

Admin Approves

User Action

ServiceListing: approved

⚙ ServiceListing.status

Data Entity

sendActivationEmail

⚡ sendActivationEmail

Automated (Workflow / Webhook)

matchDemandToListing (notify waiting customers)

⚡ matchDemandToListing

Automated (Workflow / Webhook)

Listing Live on Services

/services

Page / Screen

Path 4

Opportunities

/opportunities

Page / Screen

getDemandAggregates (provider_email filter)

⚡ getDemandAggregates

Automated (Workflow / Webhook)
Unmet demand found

Offer This Service

User Action
Prefill URL params

Create Listing (prefilled)

/create-listing

Page / Screen

6 · Community & Social Feed

16 nodes
3 paths

The social layer: posts, sponsored ads, spotlight, services wanted, and engagement actions.

Path 1

Community

/community

Page / Screen

Community Pulse (stats summary)

⟨CommunityPulse⟩

User Action

Services Wanted (demand feed)

⟨ServicesWanted⟩

User Action

Spotlight Ad

⟨SpotlightCard⟩

User Action

Post Feed (posts + sponsored ads interleaved)

Page / Screen

Path 2

Create Post (FAB)

⟨CreatePostDialog⟩

User Action

Post Types (moment, post, question, article, poll, event, job, video, gallery, voice_note)

Decision
Submit

CommunityPost created

⚙ CommunityPost

Data Entity
Auto

Admin Alert – New Post

⚙ Admin Alert – New Post (entity trigger on CommunityPost create)

Automated (Workflow / Webhook)

Post appears in feed

/community

Page / Screen

Path 3

Community Post Card

⟨CommunityPostCard⟩

User Action

Celebrate

User Action

Support

User Action

Recommend

User Action

Comment (CommunityComment)

⚙ CommunityComment

User Action

Report (ReportDialog)

⟨ReportDialog⟩

User Action

7 · ONE LIVE™ Broadcasting

13 nodes
3 paths

Live broadcasting: creating a stream, browsing broadcasts, watching, and engaging.

Path 1

ONE LIVE

/live

Page / Screen

Filters (LIVE NOW, Featured)

User Action

Broadcast Grid (LiveCard)

Page / Screen
Tap card

Live Screen (BroadcastPlayer)

/live/:id

Page / Screen

Path 2

Go Live

⟨GoLiveDialog⟩

User Action

Stream Mode Picker (camera, embed, clip, tiktok)

⟨StreamModePicker⟩

Decision
Create

LiveBroadcast created (status: scheduled)

⚙ LiveBroadcast

Data Entity
Start

Broadcaster Live (camera / embed)

⟨BroadcasterLive⟩

User Action

Broadcast: live

⚙ LiveBroadcast.status

Data Entity

Path 3

Viewer watches

User Action

Live Comments (LiveComment entity)

⚙ LiveComment

User Action

Celebrate / Support / Recommend

User Action

Broadcast: ended

⚙ LiveBroadcast.status

Data Entity

8 · Wallet, Payments & ON3 Points

10 nodes
2 paths

Payment history, ON3 Points rewards, referrals, and the ONE Impact charitable allocation system.

Path 1

Wallet / Payments

/wallet

Page / Screen

Summary Cards (spent, earned, fees, proceeds)

⟨SummaryCards⟩

User Action

ON3 Points Card (balance + ledger)

⚙ ONEPointsLedger

⟨OnePointsCard⟩

User Action

Refer a Friend (processReferral)

⚡ processReferral

⟨ReferFriend⟩

User Action

Payment History (Transaction entity)

⚙ Transaction

⟨PaymentHistory⟩

User Action

Path 2

ONE Impact

/impact

Page / Screen

Impact Summary (balance, allocated, causes)

⟨ImpactSummary⟩

User Action

Cause Card

⟨CauseCard⟩

User Action
Support cause

Allocate Points (allocateImpactPoints)

⚡ allocateImpactPoints

⟨AllocateDialog⟩

User Action
Confirm

ONEImpactLedger entry

⚙ ONEImpactLedger

Data Entity

9 · Support, Legal & Trust

15 nodes
4 paths

Help centre, legal documents, GDPR centre, complaints, trust & safety, and reporting.

Path 1

Help & Support

/support

Page / Screen

FAQ

/faq

Page / Screen

Help Search

/help-search

Page / Screen

Report a Concern (Report entity)

⚙ Report

User Action

Path 2

Legal Centre

/legal

Page / Screen

Terms & Privacy

/terms

Page / Screen

Legal Document Versions (LegalDocumentVersion)

⚙ LegalDocumentVersion

Data Entity
Admin manages

Admin: Legal Documents

/admin/legal

Page / Screen

Path 3

GDPR Centre

/gdpr

Page / Screen
Data request

GDPR Request (GdprRequest entity)

⚙ GdprRequest

User Action

Complaints (Complaint entity)

/complaints

⚙ Complaint

Page / Screen

Trust & Safety

/trust-safety

Page / Screen

Path 4

Profile: Delete Account

/profile

User Action
Confirm DELETE

GdprRequest: deletion

⚙ GdprRequest

Data Entity
Auto logout

Sign Out

Entry / Exit

10 · Admin & Back Office

8 nodes
2 paths

Platform management: admin dashboard with 17 tabs, plus the separate back-office suite for staff roles.

Path 1

Admin Dashboard

/admin

Page / Screen

Platform Stats

⟨AdminStats⟩

User Action

17 Management Tabs

Decision

Path 2

Back Office

/backoffice

Page / Screen

Overview

/backoffice

Page / Screen

User & Role Management

/backoffice/users

Page / Screen

Settings

/backoffice/settings

Page / Screen

12 Prototype Pages (KYC, Wallets, Transactions, Alerts, Safeguarding, etc.)

/backoffice/*

Page / Screen

11 · Notifications & Real-time

7 nodes
2 paths

The global notification system: in-app Notification Centre with real-time subscriptions, plus the NotificationBell badge.

Path 1

Notification Source (createNotification)

⚡ createNotification

Automated (Workflow / Webhook)
Creates

Notification entity (9 categories)

⚙ Notification

Data Entity
Badge count

Notification Bell (unread badge)

⟨NotificationBell⟩

User Action

Notifications Centre

/notifications

Page / Screen

Notification Item (read / unread / CTA)

⟨NotificationItem⟩

User Action

Path 2

Real-time Subscription (base44.entities.subscribe)

Automated (Workflow / Webhook)
Event received

Live UI Update

User Action

This UX Flow Map is generated from the actual application source code as of the current build. It reflects real routes, components, entities, workflows, and backend functions — not theoretical or planned features. For review and documentation purposes only.