gymii 🏋️

Type in your plan. Log your sets. Watch the numbers climb. Your gym draws itself along the way.

Everything lives in your browser — no account, no tracking, not even a cookie banner. No backend unless you turn on sync, and even then it only ever sees ciphertext.

→ bmmmm.github.io/gymii — installable, works offline.

• 🗺️ Gym — a real floor-plan editor: walls, zones, doors, mirrors, lockers, and machines you can tap. Everything starts locked so nothing gets nudged by accident — double-tap an item to unlock it for moving and resizing, double-tap again to lock it. Zones and walls sit on three layers, so a small area inside a big one stays visible. The gym carries its brand once (a machine only says so when it differs), its full address with a link straight to OpenStreetMap, and a list editor that fixes every machine's type, brand and muscles in one pass without a tap on the plan per machine. Undo/redo included, and typing a machine number lights it up on the plan. One tap away from the Train hub. Optional: draw it once your gym is in there and gymii can point you at the next machine.
• 💪 Train — repeat a past workout in order, or roam by number, map tap or muscle. Last workout's numbers prefill every set. Cardio machines log distance + time, bodyweight machines reps + extra weight, and free-weight areas keep separate histories per named exercise. 📍 shows where the next machine stands, a busy one gets the closest open alternative, and a coverage row tracks which muscles you've hit today. Your locker number has a home too — noted at the start, out of the way once you're logging. 🏁 in the machine header finishes the workout right where you logged the last set, and removing a set takes two taps — it has no undo.
• 📋 Plans — start with the plan you already have: type it in the way it's written (Leg press 3x10 80, #7 Chest press 3x8-12 40kg, Treadmill 20min) and gymii reads it — no gym needed yet. At the machine it asks once which one this is, creates it under that name, and remembers. Edit as a list of steppers or as plain text, whichever is faster. Then just tick it off: today's plan is one tap on the start screen, every set is one tap ("✓ Log set 2/3 — 50 kg × 10"), and the workout keeps pulling you back to unfinished targets. Your LLM can draft one too; paste it in for review.
• 📅 Weekdays, without the nagging — tag a plan with the days you train and the start screen says what today is about: what's on, what you already did, or that it's a rest day and when the next one comes. A day that went by is stated once, never tallied, and "skip this week" settles it. gymii also notices when you keep training something on Tuesdays and offers to write that down.
• ⏱️ Rest timer — starts itself and remembers per machine. Tap outside the rest screen and it keeps running above the log button, so putting the screen away never costs you the rest; the screen itself says what's coming ("Next: set 2/3 — 50 kg × 10"). A rest you change mid-workout belongs to that workout — one link makes it the machine's for good. The screen stays awake (just the break, or the whole workout — your call) and dims itself so a dark gym stays dark: the countdown ticks one brighter beat per second, any touch brings it back, and the last seconds are bright again. Four tones to pick from, each one audible before you commit — and they play like music, so an iPhone's silent switch doesn't swallow them.
• 📈 History — opens on a weekly dashboard: this week's workouts, sets, volume and time against last week, twelve weeks of bars to tap, a progress chart per machine you can drag along, the route you walked through the gym drawn on your floor map, and a muscle card that shows how many sets each group got — tap a row and the view narrows to that muscle. A second screen holds every workout (one tap repeats it), the training heatmap and the editor: add or remove sets and machines, fix the date, or type in a workout you did without your phone. After each strength set, one tap rates it by reps left in the tank (0, 1, 2, 3+) — gymii also remembers the order you visited the machines in. Name a workout (gymii suggests one from the muscles you trained) and one tap filters everything down to it. Hints — "try 60 kg", "train it this week", each with a ↗ to the study behind it — sit where you act on them: under "Last:" at the machine, under a muscle, under the chart, in the plan; they always read all of your training.
• 🏨 Gyms & units — home gym, hotel gym, whatever. kg or lbs, switched in one go.
• 📦 Templates — export your gym as JSON, import someone else's. Want to poke around first? Settings → "Load test data" fills a separate Demo gym with eight weeks of history and three plans — your own gyms stay untouched.
• 🤖 AI, on your terms — copy a prompt plus your data into any LLM you trust, paste the answer back. gymii never talks to an AI service itself.

python3 serve.py   # → http://localhost:8437

Any static file server does the job; serve.py just turns caching off so edits show up on plain reload. No build step, and nothing from node_modules ever reaches the browser — the app that ships has no dependencies at all. Its browser tests do: pnpm install && pnpm exec playwright install chromium, then pnpm run smoke.

localStorage, under gymii.* keys. Nothing leaves the browser unless you turn on sync, and sync is end-to-end encrypted wherever the browser allows it. The one exception is explicit: served over plain http (your own server in your own network), the browser refuses crypto entirely — gymii then offers sync only as a clearly-labeled unencrypted mode, never silently. Until you turn anything on, export a backup before you switch devices or browsers.

With sync on, the device list shows when each paired device was last seen. A backup device is expected to check in on its own — when one has gone quiet for more than three days, the Sync card tells you which one.

Settings shows how much of the browser's storage gymii occupies and whether the browser has promised to keep it. Browsers do clear sites nobody has opened in a while — on iPhone after seven days, unless the app was added to the Home Screen — so gymii asks for persistent storage the first time you finish a workout, when there is finally something that cannot be reconstructed. And if a write is ever refused, it says so at the top of the screen rather than pretending the set was saved.

Vanilla HTML/CSS/JS (ES modules), zero dependencies. Tests are plain node, no runner — for f in test/*.test.mjs; do node "$f"; done. Notes for contributors and agents live in AGENTS.md.

Got a floor plan of your gym? Templates are meant to be shared — export it (Settings → Export gym template) and either open a Submit a gym template issue (no git needed, paste the JSON) or send a two-file PR against templates/. Details in CONTRIBUTING.md; CI validates every template against the app's real import path.

Homepage · GPL-3.0 · ko-fi