Design source

Screen Archetypes

The representative screens Antho should influence first.

iOS Screen Archetypes

Status: draft v0.2

Antho should design archetypes, not every app screen. Codex will map these archetypes to real SwiftUI views.

Build 84 changes the starting point: Home, Connexion, and Mes coachs are no longer abstract asks. They are implemented reference surfaces. The remaining archetypes below should inherit from that reference set instead of restarting the visual direction.

Archetype 1: Home / Dashboard

Purpose:

  • orient the player
  • show current progress
  • suggest next action
  • expose C4-DY guide

Must include:

  • player identity
  • LTI level/progress
  • next recommended action
  • recent activity or challenge prompt
  • route to Ateliers/Challenges/Friends/Messages
  • C4-DY contextual entry

Design questions:

  • Build 84 answer so far: Home is a premium training cockpit with social/progress shortcuts, not a feed.
  • Open: which Home elements become reusable on the rest of the app: action tiles, player capsule, progress ring/capsule, bottom menu, Mon Caddie entry, and Mes coachs entry?
  • Open: where does Mon Caddie live without becoming a fifth tab?

Archetype 2: Atelier Detail + Score Entry

Purpose:

  • understand the exercise
  • enter score with low friction
  • capture misses
  • return progress feedback

Must include:

  • Notice
  • Consignes
  • Pedagogie
  • Tips Linecard
  • Distance
  • attempts
  • success/failure entry
  • miss tendency when failure happens

Design questions:

  • Should score entry be inline, bottom sheet, or separate step?
  • How do we keep text readable while preserving a premium look?
  • What is the visual hierarchy between pedagogy and scoring?
  • How does the Antho Home tile style translate into the Ateliers list without losing scan speed?
  • Which parts of score entry can be premium artwork, and which must remain native controls?
  • This is a first-priority gap because Ateliers are a primary Home route.

Archetype 3: Challenge Detail / Ranking

Purpose:

  • know what the challenge is
  • know who is participating
  • play or review results
  • understand final ranking

Must include:

  • challenge source
  • participants
  • deadline/status
  • locked pedagogical content when created from exercise
  • editable distance only where allowed
  • ranking/result state

Design questions:

  • How does a challenge feel different from a normal atelier?
  • What is the best visual state when waiting for others?
  • How should final ranking notification route into the screen?
  • How should Classement inherit the Antho style without becoming a casino/game leaderboard?
  • What is the shared rule between challenge ranking, global ranking, friends, and badge/social proof?

Archetype 4: C4-DY Companion

Purpose:

  • guide the user through the app
  • answer questions
  • suggest contextual next actions
  • eventually support voice

Must include:

  • C4-DY identity/avatar
  • short prompt
  • action suggestions
  • chat access
  • contextual memory signal without exposing technical detail

States:

  • first launch tour
  • returning user next step
  • challenge invitation waiting
  • training suggestion
  • coach/student context
  • low quota/free user state

Design questions:

  • Player-facing label is Mon Caddie today; C4-DY is still useful internally but should not leak into player copy without a deliberate decision.
  • Is Mon Caddie a floating button, bottom bar companion, dashboard card, contextual sheet, or all three depending on context?
  • What makes Mon Caddie feel like a LineCard companion instead of generic chat?
  • How does Mon Caddie appear on Apple Watch/notifications later?
  • How should Antho's Home Mon Caddie button reconcile with the older validated floating button?

Archetype 5: Badge / Level Unlock

Purpose:

  • reward progress
  • make achievement memorable
  • encourage sharing or next action

Must include:

  • badge/level artwork
  • short achievement title
  • why it happened
  • next suggested action
  • share/social route if relevant

States:

  • badge unlocked
  • level up
  • challenge won
  • streak/progression milestone

Design questions:

  • Should the animation feel like Apple Activity, golf trophy, or LineCard-specific?
  • Where does the unlocked badge live after notification tap?
  • Should unlocks be shareable as image/link?
  • Current product symptom: a Centurion notification can arrive, but the badge is not obvious after tapping the notification.
  • The atlas should capture the badge route, replay state, and profile/progress hub treatment before implementation.

Archetype 6: Profile / Progress Hub

Purpose:

  • show identity, badges, progress, history
  • make unlocked achievements findable

Must include:

  • profile header
  • current LTI level
  • badges owned/locked
  • recent results
  • friends/challenges summary

Design questions:

  • How does the user find the Centurion badge after notification tap?
  • What should be public vs private?
  • How does this differ for Joueur, Capitaine, and Coach?
  • How does the Build 84 player/progress capsule expand into a full Profile/Progress screen?
  • Which visual layer communicates LTI, badges, recent results, and identity without overcrowding the screen?

Archetype 7: Mes coachs / Coach Studio

Purpose:

  • bridge player-student and coach workflows
  • manage students, plans, feedback, reports
  • keep the current booking/navigation behavior intact

Build 84 already includes:

  • Mes coachs entry from Home
  • active coach / pending / course counters
  • book-course CTA direction
  • native booking navigation under the Antho shell

Must include next:

  • roster
  • active coach cards
  • pending request cards
  • scheduled lesson cards
  • student detail
  • plan composer
  • lesson note
  • monthly report

Design questions:

  • Does Coach Studio keep the same dark app grammar or need a denser professional surface?
  • How does LineCard keep LTI as the moat?
  • What is the difference between a player-facing Mes coachs surface and a coach-facing Coach Studio cockpit?