Lesson Player

Consume a focused lesson with chapter navigation, notes, transcript, resources, and progress into the next lesson. This example brings Lesson and Chapters together so learners and course teams can find the next task without losing context.

It includes representative records such as Why prioritization fails and Opportunity scoring. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Lesson Player
Use this template in Figr

Template facts

Screen

Detail

Primary action

Mark complete

Pattern

Detail

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product and growth teams need to mark complete while keeping progress, lesson and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Lesson gives users an obvious place to start.
  • Supporting view: Chapters keeps the related context close.
  • Primary action: Mark complete stays visible when people need it.
  • First signal: Progress shows a useful value (62%).
  • Second signal: Lesson gives additional context (8 of 13).
  • Sample record: Why prioritization fails.
  • Next record: Opportunity scoring.

States worth designing

  • Record not available: say what changed, protect progress, and offer a clear next step.
  • Details refreshing: say what changed, protect progress, and offer a clear next step.
  • Incomplete evidence: say what changed, protect progress, and offer a clear next step.
  • Action complete: say what changed, protect progress, and offer a clear next step.
  • Record read-only: say what changed, protect progress, and offer a clear next step.
  • History not available: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Lesson → Chapters → Mark complete → Review outcome

Patterns used

Detail, Lesson, Chapters, contextual actions, error recovery

Why these choices work

Emphasize record status, next action and recent changes. Put secondary history nearby without competing with the primary task.

Pay attention to lesson and chapters. People need to distinguish Why prioritization fails from Opportunity scoring. Keep progress visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Mark complete”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Course Detail, Assignment Submission, Course Catalog.

Start from this in Figr

Design a lesson player screen inside our existing product. Use our current components, tokens and content language. Include Lesson and Chapters views, credible records like Why prioritization fails, and a clear “Mark complete” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr