arch-atlas

Screens

UI · user-facing flows

presentation

Overview

Product surface documented from the app: every screen, the user flows that link them, and the API calls each screen fires — hover a screen card in any flow to see the request headers + body. Domain / data / DI nodes are pending the architecture-extraction pass.

Screens

Programswireframe
default

Paginated list of training programs with a current-program banner.

Programs — emptywireframe
empty

No programs yet → prompt to create the first one.

Program detailwireframe
default

Program overview with its day list; tap a day to see exercises.

Day detailwireframe
default

Exercises for a day; primary action starts the workout.

Exercise detailwireframe
default

Exercise instructions, muscles, and a report tab.

Create programwireframe
default

Name a new program, then add exercises to its days.

Add exercisewireframe
default

Search the exercise library and add to a program day.

Workout — startwireframe
default

Pre-workout overview; 'Begin' creates a session then opens the runner.

Workout — active setwireframe
default

Per-set logging (weight + reps). Each completed set logs an execution.

Workout — restwireframe
default

Rest timer between sets (rest_screen.dart). Static — no API.

Workout — completewireframe
success

Session finalized; shows summary and refreshes the training report.

Difficulty reportwireframe
default

Perceived-difficulty report (distribution, insights). Rating itself is saved on each set execution.

User Flow

Empty — fill this in later. Open the manifest and add content here.

Cases & Edge Cases

Empty — fill this in later. Open the manifest and add content here.

Code References

Empty — fill this in later. Open the manifest and add content here.

API Calls

Empty — fill this in later. Open the manifest and add content here.

Notes

Empty — fill this in later. Open the manifest and add content here.