Appearance
CoachMe planning workspace
One place to decide what we build, why it matters, and how it ships.
CoachMe is a multi-surface coaching platform: coach web, coach mobile, client mobile, and personal workspace behavior. This docs workspace connects Public V1 scope, internal build milestones, implementation architecture, and feature-level details so we can build without losing context.
Tags: Coach Web, Coach Mobile, Client Mobile, TypeScript DDD
Public V1 snapshot
The current plan is broad, but the first build should stay anchored to the highest-leverage coaching loop: onboard, assign, execute, review, and communicate.
| Metric | Count |
|---|---|
| Total features | 78 |
| Public V1 items | 50 |
| Feature sections | 14 |
| Product surfaces | 3 |
Product surfaces
Each surface should have its own UX shell while sharing identity, contracts, domain rules, design tokens, and implementation language.
Coach Web App
Tags: Primary workspace
Desktop-optimized workspace for dense coaching operations: client profiles, program building, questionnaire creation, progress review, messaging, and business reporting.
Coach Mobile App
Tags: Operations and review
A separate Expo app for coach operations and review: task inbox, client context, progress and nutrition review, messaging, risk signals, and lightweight actions; full mobile builder parity remains Post-V1.
Client / Personal Mobile App
Tags: Daily execution
The trainee and self-coaching experience for onboarding, Today view, workouts, meals, check-ins, offline logging, progress, reminders, and coach communication.
Recommended build order
This sequence supports feature-by-feature internal delivery while protecting technical foundations like auth, contracts, offline behavior, localization, and data ownership before public launch.
Foundation
Tags: Phase 1
Monorepo toolchain, auth baseline, PostgreSQL, OpenAPI contracts, shared mobile core, localization/RTL, Docker deployment.
Identity and onboarding
Tags: Phase 2
Coach registration, provider adapters, client invitations, validated client onboarding, role-based sessions.
Coach operations
Tags: Phase 3
Dashboards, task inbox, client profiles, goals, notes, messaging, client status, and coach attention workflows.
Forms and programs
Tags: Phase 4
Reusable questionnaire builder, assignment flows, exercise provider integration, coach-created custom exercises, program templates, workout execution.
Daily execution and progress
Tags: Phase 5
Client Today view, quick logs, offline workout logging, nutrition workflows, measurements, progress photos, and weekly recaps.
Primary docs
Use these pages to move between product decisions and engineering implementation without duplicating context.
Feature database
Tags: Product, Static reference
Feature plan with phases, authored working flows, and links to deeper technical pages.
Public V1 scope contract
Tags: Launch scope, Source of truth
Central contract for what must be planned, built, tested, and accepted before the first public launch.
Workflow state map
Tags: Authority, Lifecycle
Canonical cross-feature lifecycle states, gates, exception paths, and ownership boundaries for Public V1.
Roles and permissions
Tags: Authority, Access
Canonical Public V1 actors, operating contexts, lifecycle gates, protected-data access, minimized production telemetry, support/admin grants, and negative access-test rules.
Privacy and retention
Tags: Authority, Privacy
Canonical UAE/GCC-first privacy, consent, retention, export, deletion, anonymization, media purge, mobile cache purge, legal hold, and incident-response rules.
API contract standard
Tags: Authority, REST
Canonical REST route, DTO, error, pagination, idempotency, OpenAPI, compatibility, and contract-test rules for Public V1.
Event and outbox standard
Tags: Authority, Events
Canonical backend event envelope, transactional outbox, publisher, retry, ordering, dead-letter, replay, and consumer idempotency rules.
Offline sync protocol
Tags: Authority, Mobile Sync
Canonical Public V1 client and coach mobile sync rules for SQLite caches, local outbox operations, receipts, replay, conflicts, media retry, pruning, and diagnostics.
Environment runbook
Tags: Authority, Environments
Canonical Public V1 environment guidance for app-stack setup, secrets, deployment gates, backup, restore, rollback, and the docs-site appendix.
Toolchain contract
Tags: Authority, Toolchain
Canonical Public V1 toolchain guidance for Node.js, pnpm, Turborepo, scripts, codegen, migrations, tests, CI command shape, mobile builds, dependency updates, and release notes.
Integration register
Tags: Authority, Integrations
Canonical Public V1 matrix for external providers, self-hosted application boundaries, decision status, data and credential boundaries, terms and limits, cache and retention, failure behavior, launch evidence, and explicit deferrals.
Observability plan
Tags: Authority, Operations
Canonical Public V1 signal contracts for structured logs, metrics, error and crash reporting, synthetics, dashboards, alerts, safe client diagnostics, and developer diagnosis playbooks.
Test and release gate
Tags: Authority, Release
Canonical Public V1 merge, staging, production, mobile distribution, coverage, fixture, security, performance, evidence, approval, and post-release response gates.
Coach web design options
Tags: Design, Exploration
Seven static HTML mockups for the coach web direction, with Glass Calm as the current subtle lilac glass merge of the Apple-like structure and glassy reference/video depth.
Coach mobile direction: Rounds
Tags: Design, Mobile
The single coach mobile direction after the July 2026 cleanup, which retired the earlier eight-mockup gallery and the Ward and Line alternatives. The app is a session, not a screen: it plays the priority ranking as a finite run of one client at a time — handle, defer, or skip — and ends when the deck is empty. Revision B rebuilds it on the coach task inbox, which is what Public V1 actually ships.
Brand colour standard
Tags: Design, Brand, Accessibility
Periwinkle #9193FD is the brand colour, decided 25 July 2026. The full ramp, the measured pairing rules, and the two-step system that keeps it accessible — the brand fills large surfaces with ink text, a darker step carries white text.
Client mobile UX concept (guided, Today-first)
Tags: Design, Client mobile, UX concept
The single client mobile direction after the July 2026 cleanup, which retired the earlier option gallery. A "one thing, ever" Today home, a coach thread one tap away, and a guided workout session — the reasoning, the states, and the decisions since promoted into the committed feature docs, with the guided screen set showing what it looks like.
Technical architecture
Tags: Engineering, DDD
Modular monolith architecture, bounded contexts, data infrastructure, offline sync, auth, test plan, and build order.
Development readiness review
Tags: Readiness, Pre-dev
Critical gaps, scope risks, missing architecture/tooling/environment decisions, and the gate to satisfy before broad application development starts.
Domain model map
Tags: Domain, Graph
Living relation graph for bounded contexts, aggregates, entities, value objects, domain events, and cross-context dependencies.
Feature-area reference
Deep dives should use the same detail structure: overview, users, flows, requirements, dependencies, edge cases, acceptance criteria, and technical notes.
Client management
- Detailed profiles — Technical
- Measurements and photo timeline — Technical
- Questionnaire builder — Product
- Questionnaire builder — Technical
Program and training
- Program builder — Product
- Program builder — Technical
- Exercise library — Product
- Exercise library — Technical
- YMove integration — Technical
- Quick log buttons — Product
Coach workflow
- Coach task inbox — Technical
- Client risk flags — Technical
- Priority view — Technical
Forms and onboarding
- Coach login and registration — Technical
- Extensible authentication providers — Technical
- Onboarding workflow — Technical