Overview
Argilzar Workouts did not begin as a blank-slate app idea. It came from an already useful Usable chat workflow for logging workouts, then turned that workflow into a dedicated interface with programs, workout execution screens, summary/history views, and a cleaner product memory trail.
Why this project exists
The project exists because chat was good enough to prove the habit but not good enough to be the final interface. The most valuable part of the earlier workflow was that Usable chat created real logged sessions that later became product evidence, PRD material, and implementation priorities.
What was built
- A local-first workout app backed by IndexedDB/Dexie
- Program library, workout logger, summary, and history views
- Dedicated support for skip flows, substitutions, and supersets
Project scope
The project keeps a clear product stance: use the app UI for fast execution and keep intelligence in the surrounding workflow. That is why the current app stays local-first and why the longer-term direction includes keeping Usable chat in the loop for planning while a dedicated UI handles actual workout execution.