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

Profilewireframe
default

Loads the customer profile + follow counts + latest measurements.

Edit profilewireframe
default

Update name/bio/avatar; save posts back to the Medusa customer.

Body measurementswireframe
default

Log measurements (chest, waist, arms…) via a sheet.

Connectionswireframe
default

Followers/following tabs; follow toggle.

Settingswireframe
default

Hub: account, preferences (theme/language/units), security, support. Loads + saves user settings.

Notification settingswireframe
default

Per-category push toggles; registers the FCM token.

Securitywireframe
default

Change password, 2FA, delete account entry points.

Change passwordwireframe
default

Current + new password; validates against compromised/weak.

Delete accountwireframe
default

PLANNED — code calls POST /delete-user but the route is annotated 'not exist just prepared impl'. Marked planned per code.

Support & FAQwireframe
default

FAQ categories + questions; contact form tab.

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.