BikeControl (SwiftControl)
Use Zwift Click, Zwift Play, Shimano Di2, or any Bluetooth controller with MyWhoosh, Rouvy, Zwift, and more. Free to try on iOS, Android, Windows, and macOS.
목표·경험·장비 기반 운동 계획과 칼로리 목표, 클라우드 백업 안 하면 데이터는 휴대폰에만 저장
A workout plan and calorie target built from your goal, experience and equipment. Your fitness data stays on your phone unless you turn on cloud backup.
스포츠·피트니스TypeScript · SCSSGitHub @keshavkhatri온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
최근 완료된 8시간 회차 사이 GitHub 스타 증가량 순
Use Zwift Click, Zwift Play, Shimano Di2, or any Bluetooth controller with MyWhoosh, Rouvy, Zwift, and more. Free to try on iOS, Android, Windows, and macOS.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기fitness-app
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗StokeForm is a cross-platform (iOS / Android) fitness app (workout planning and logging, nutrition and calorie tracking, body-composition analysis, progress tracking) built with Ionic 9 + Angular 22 (standalone, zoneless, signals) + Capacitor 8.
All fitness and health data is stored on this device only. A StokeForm account (email or Google) is required to finish first-run setup, but nothing is synced to it yet.
Implemented so far:
/assessment: results, macro breakdown, Why these numbers? with each step of the fitness calculation engine's own calculation, and next steps into the app). The profile can be reviewed and edited later from the assessment or the You tab.fit-theme-dashboard, matching the approved mockup): the StokeForm wordmark, a notification bell (dot while reminders are unread) and the avatar (opens You); a greeting with the user's name and the active-day streak; "Your day, in motion" with a ring (the mean of today's goals) and Move (logged steps vs 10,000), Train (today's planned workout done) and Recover (today's check-in) tiles, which open the steps and recovery check-ins; the featured workout (start, resume, activity, rest or setup) over a generated placeholder image (home-media.ts takes a real photo); compact Nutrition (protein ring, calories vs target) and This week (finished vs planned workouts, bars as tall as the time trained; opens Progress) cards. Each part loads independently; pull to refresh.fit-theme-dashboard): a daily food log by meal and day with a Monday–Sunday day strip, a calorie ring and macro bars against the day's calculated targets (intake only when a target is withheld). Add food (dark) searches your Recent foods (distinct foods from the last 30 days): + logs one again to the chosen day and meal in one tap, or tap it to change it first; foods can also be entered manually. Edit food scales a logged food by serving size and number of servings (live totals from the domain) and updates the same entry; delete asks first. Week charts calories and a chosen macro by day against the targets, with averages over logged days only (a day without entries is never a zero). There's no food database or barcode scanning.fit-theme-dashboard): photo, name, age and height from your profile, your goal, tiles for Profile, Weight, Body measurements, Body composition, Fitness review and Quick add, plus Progress and the settings. The Profile editor is the dark grouped review of your saved answers (each row opens its question; Save profile re-runs the assessment). Weight, measurement and InBody entry, InBody detail and the Fitness Review use the dark immersive style; the history screens are light.domain/daily-check-in, core/daily-check-in)./offer): Free or Premium, shown once right after first-run setup and any time from You. No billing provider is integrated, so everyone is Free and Premium says it isn't available yet (no prices, trials or checkout). The feature matrix and entitlement boundary are in docs/access-model.md.InBody onboarding (AI-based): the welcome screen's Get started sets up by answering questions; when this build can read reports, Set up from an InBody report instead starts with the upload. The upload step says the image goes to an external AI service, checks the file (PNG/JPEG/WEBP, up to 8 MB) and posts it to the app's own extraction endpoint (core/inbody, POST /v1/inbody-extractions), which holds the OpenAI key (Responses API, Structured Outputs, store: false); the app never does. Every answer is re-validated (parseInBodyExtraction) and mapped (inBodyPrefill); a read report prefills sex (on the about-you screen, which also shows the report summary), height and weight (each ruler starts at the printed value, e.g. 172.4 cm, unrounded); each screen shows the printed value or flags it as uncertain, unreadable, absent or unusable for the user to correct, and a value counts as confirmed once its screen is continued. The profile is saved only from the review's "Create my profile", as before. Unsupported or unreadable reports, file, network, provider and invalid-response failures each have their own message, with retry and a switch to manual entry that keeps answers already given. The image and extraction stay in memory only; nothing is logged; weight history and assessments are untouched (the workout plan is made from the saved profile, as for manual set-up); age is never turned into a date of birth and Fat Free Mass is not used as lean body mass. The endpoint is a public URL set in src/environments (inbodyExtractionEndpoint; never a key): the local server in development builds (http://localhost:8787); production builds set null, which hides the upload option until hosting is chosen. No local OCR.
Exercise demonstrations: workout detail ("Show demonstration") and the active workout ("How to do it") offer a demonstration for exercises with a faithful match in free-exercise-db (public domain): its start and end position photos, played in turn like a GIF, with Pause/Play (paused by default under reduced motion) and a retry if loading fails. Nothing loads until asked. The mapping is domain/workout-programming/exercise-demonstrations.ts (58 of 77 exercises; the rest show no demonstration rather than a different movement); photos come from exerciseMediaBaseUrl in src/environments (jsDelivr, pinned to one commit; null hides demonstrations).
InBody assessments (You → Body composition, Progress, Quick Add → Add InBody): a history of saved assessments (key values, the latest value per metric and the difference since the previous report in the same unit; a single assessment shows no change), and a detail page per assessment with every recorded value grouped as on the sheet. A new assessment can be typed in or uploaded: the upload reuses the onboarding extraction (ReportImport) and fills in the form, which is the review step; nothing is saved until the user saves. Values saved unchanged are stored as read from the report (INBODY_AI_PROVENANCE); any correction saves them as a manual entry. The catalogue covers every scalar the extraction reads (skeletal muscle mass, fat-free mass, water, BMI, visceral fat level, …); lean body mass stays a separate, manual-only metric. From the detail page an assessment can be edited (the same form, prefilled; it keeps its import provenance only while its values are unchanged) or deleted after a confirmation (other assessments, weigh-ins and the profile are untouched). Saving never changes the profile or weight history; the profile weight is still updated only with "Use as profile weight" on a weigh-in.
Not implemented yet: sync of app data to the account, progress photos, push notifications, health-app integrations, AI coaching and payments/subscriptions (a provider-neutral boundary exists; no provider). Each will arrive as a separate, reviewed phase.
| Command | Purpose |
|---|---|
npm start | Dev server (ng serve) |
npm run build | Production build to www/ |
npm run lint | ESLint (TS + templates + template a11y) |
npm test | Vitest unit tests (--watch=false in CI) |
npm run server:start | InBody extraction server on 127.0.0.1:8787 (reads server/.env; see server/README.md) |
npm run server:install | Installs the server's own dependencies (once, and after its lockfile changes) |
npm run server:migrate / server:migrate:status | Applies / lists database migrations explicitly (needs MIGRATION_DATABASE_URL or DATABASE_URL; see server/DATABASE.md) |
npm run server:email:test -- --to <address> | Sends ONE test email to the address you name through the configured delivery (needs --to; see server/AUTH.md, "Setting up real email") |
npm run server:cleanup / server:cleanup:apply | Preview / delete old accounts whose email was never confirmed (preview is the default; reads DATABASE_URL; see server/AUTH.md) |
npm run server:test / server:typecheck | Server tests (no network, no key) / TypeScript check |
npm run android:debug:local / android:debug:cloud | Debug APK talking to the API on this PC (via adb reverse) / to Cloud Run. Windows; needs a JDK 21 and the Android SDK (JAVA_HOME, ANDROID_HOME, or the scoop installs). See server/AUTH.md, "Testing on an Android phone". |
The Android project is in android/ (app ID com.stokeformfitness.app). Debug builds are signed with the
local debug key; adb install -r android/app/build/outputs/apk/debug/app-debug.apk updates an installed
debug build and keeps its data. iOS has not been added yet (npx cap add ios).
website/ is the stokeform.com site (home, terms, privacy, contact): static files for Vercel, separate from the app. See website/README.md.
src/
theme/ Design tokens: the ONLY place colors/type/spacing are defined (contract: docs/design-system.md)
_palette.scss Color values (Sass maps): classic light + dark; redesign warm + charcoal (one key set)
_tokens.scss Emits CSS custom properties (--color-*, --space-*, --radius-*, --font-size-*, …)
and the opt-in screen themes (.fit-theme-dashboard, .fit-theme-immersive)
_ionic-bridge.scss Maps tokens onto Ionic's --ion-* variables
_mixins.scss Component helpers: text(), eyebrow, focus-ring, safe-area-padding, button-reset, pressable
theme.scss Global entry: base styles, utility classes, Ionic overrides
app/
app.config.ts Providers (Ionic platform mode, router, icon + theme init)
app.routes.ts Tabs shell; each feature mounted via its own <area>.routes.ts
domain/
fitness-profile/ Framework-free profile model, units, equipment catalog, goal-target policies,
plausibility ranges and runtime parsing (for storage/API data)
workout-programming/ Deterministic workout generator (v2): exercise catalog + progression chains,
objective-based session templates, weighted exercise selection, prescription
profiles, weekly volume balancing, sequencing, duration limits, profile adapter.
All programming numbers in workout-config.ts; golden fixtures in testing/
training-plan/ The user's plan lifecycle on top of the engine: plan from profile, freshness
(does a stored plan still fit the profile?) and a strict stored-plan parser
fitness-calculations/ Deterministic engine: profile → FitnessAssessment (BMR, TDEE, calorie and
macro targets, safeguards, explanation). All coefficients in calculation-config.ts
workout-session/ Performed workouts: log rules, stored-log parser, history and progress facts
nutrition/ Food entries, day totals and targets
inbody-extraction/ AI extraction contract for InBody reports: JSON schema for the model, strict response
validation, mapping to profile/assessment suggestions (no network, files or storage)
body-measurements/ Weight entries, history and trends; tape measurements, their history and changes;
the explicit profile-weight change
core/ App-wide singletons (no UI)
profile/ FitnessProfileRepository (local today), FitnessProfileService, OnboardingStatusService,
UnitPreferenceService, guards
calculations/ FITNESS_CALCULATION_CONFIG injection token for the domain engine
workout/ WorkoutPlanRepository (local snapshot today), WorkoutPlanService (create / keep /
regenerate the plan as the profile changes; saves a Premium custom plan, which is never
regenerated automatically), WORKOUT_PROGRAMMING_CONFIG token,
WorkoutLogRepository/Service (active workout + finished workouts), WorkoutHistoryService
nutrition/ NutritionRepository (local food log), NutritionService (day log + calculated targets)
body-measurements/ Weight and measurement history repositories/services; ProfileWeightService
(explicit "use as profile weight")
inbody/ InBodyExtractionClient: sends a report image to the extraction endpoint, re-validates
the answer; INBODY_EXTRACTION_ENDPOINT token (null = upload unavailable)
time/ CLOCK token + local calendar date helper (deterministic tests)
storage/ KeyValueStorage: async device-local preference store (localStorage today)
theme/ ThemeService: system/light/dark preference
icons/ Central ionicon registration (only listed icons are bundled)
shared/ui/ Design-system components (selector prefix `fit-`), import via `shared/ui`
shell/
tabs/ Bottom tab bar: Home, Train (workout), Fuel (nutrition), Progress, You
quick-add/ Quick Add sheet + action registry; QuickAddLauncher opens it (from You)
features/
home/ Dashboard: page, routes, view models, section cards (all real data: profile goal, plan,
workout history, nutrition, recorded weight)
workout/ Plan, Workout Detail, active workout (full screen), summary, history; progress/ is
mounted under You (/you/progress); custom-plan/ is the Premium plan editor and the exercise
library/picker (the library is Free; the editor is gated, see docs/access-model.md)
nutrition/ Daily food log, Add food (recent-food search), Edit food (portions), weekly view
body-weight/ Weight history (/you/weight-history) and weigh-in entry
body-measurements/ Measurement history (/you/measurements) and entry
you/ Profile review, links to progress and body tracking, appearance and units settings
assessment/ "Your starting point": profile → engine → view model (pure adapter) → thin page
onboarding/ Full-screen onboarding flow (no tab bar); /onboarding/review edits an existing profile
state/ OnboardingFlow (signals), draft model, step definitions, resumable progress store
validation/ Pure step/form validation with user-facing messages
steps/ Step components; generic single-choice step + config, form steps, summary
onboarding-content.ts Labels, descriptions and icons for every answer
docs/design-system.md is the contract for tokens, screen themes, components, accessibility and responsive rules; screen redesigns follow it.var(--color-*), var(--space-*), var(--radius-*), and @use 'mixins' as fx; @include fx.text(h3, semibold); (src/theme is on the Sass include path).<html> follows the OS; theme-light / theme-dark force a mode (managed by ThemeService). Redesigned screens opt into a screen theme with a class on the page host (fit-theme-dashboard follows light/dark, fit-theme-immersive is always dark); screens without one keep the classic look. Focus indicators use --color-focus and stand-alone graphics --color-primary-strong, never the brand fill (lime is invisible on light surfaces).OnPush, signal inputs/outputs. fit-* is presentational and has no business logic. Feature-specific components live in features/<area>/components.ios/md per platform for native behaviour (transitions, swipe-back). The look must be mode-independent: never rely on mode-only Ionic features (e.g. collapse="condense") or on Ionic's mode-specific sizing; check new UI in both modes (append ?ionic:mode=ios / ?ionic:mode=md to the dev URL).resource() (e.g. Home reads the profile, plan, history and nutrition services). If demo data is ever needed, it lives only in *.demo.ts files (enforced by lint, no-restricted-imports) and must be labelled in the UI.<area>.routes.ts. Full-screen flows that hide the tab bar go next to the shell route in app.routes.ts.OnboardingStatusService derives needs-onboarding (no profile) / needs-assessment (profile whose assessment wasn't reviewed; marker stores only the profile's ) / . guards the tab shell (setup complete, then the one-time offer for users who just finished setup: ), guards and the full-screen workout routes (never interrupted by the offer), guards , guards and . The profile is created only after the account step, so nothing personal is shown before sign-in; the questionnaire draft survives the sign-in trips (email screens with , Google's app link) and restarts. Editing the profile changes , so its assessment is shown again.Known items that must be resolved before a production release:
LocalFitnessProfileRepository and OnboardingProgressStore keep personal and body data (date of birth, sex, height, weight, goals) as plain JSON in device storage (localStorage via KeyValueStorage). Review profile persistence (platform secure storage / encrypted local store, server as source of truth once the API exists) before release. Marked with TODO(security, before production) in both files.LocalWorkoutPlanRepository keeps the plan (goal, experience, training setup; no body data) as plain JSON in device storage. Covered by the same persistence review.updatedAtcompleterequireAppReadyFirstRunOfferServicerequireOnboardingComplete/offerredirectIfOnboarded/onboardingrequireProfile/assessment/onboarding/reviewnext=/onboardingupdatedAtunitSystem is display-only. Height and weight are picked on rulers (fit-ruler, wrapped by the onboarding height/weight pickers): height in whole cm or whole inches, weight in 0.1 kg or 0.1 lb, over the profile's own ranges (HEIGHT_CM, WEIGHT_KG; imperial rounded inwards). The draft keeps one canonical value; switching units only changes what is shown, and every ruler tick round-trips to itself (tested for every tick), so switching back and forth never drifts. A value read from a report (or typed) may sit between ticks; it is shown exactly and only snapped once the ruler is moved. Body details are answered one screen at a time (basics is partial in the draft until all four are given); progress saved by the previous version still resumes. There is no nutrition-preference question: the profile has no field for it, so that screen of the design is left out rather than storing an answer nothing uses. The finish screen makes the workout plan (as Home would on first open) and says it is ready only once it was; it then continues to the assessment, since Home opens only after it. The profile stores dateOfBirth (ISO YYYY-MM-DD), never age; derive age with currentAge() from domain/fitness-profile/date-of-birth.ts, and display age rather than the birth date. The app is adults-only (18+, AGE_YEARS in profile-rules.ts). weight is the profile's current weight, not a history; recorded weigh-ins live in the separate weight history and change the profile only through the explicit "Use as profile weight" action. No fitness calculations happen here; engines consume UserFitnessProfile later.src/app/domain): framework-free TypeScript, enforced by lint (no Angular/Ionic/Capacitor/rxjs or app-layer imports). Calculations take an explicit asOfDate (no hidden clock) and return { ok, value | error }. Formula/coefficient changes require a new calculationVersion in calculation-config.ts. Results are estimates; UI copy must say "estimated maintenance", "starting calorie target", "initial protein target". Assessments separate estimates (BMR, TDEE) from targets; consumers must handle targets.calories.status (normal / floor-applied / review-required) and targets.macros.status (feasible / constrained / infeasible, which has no gram targets). The calorie threshold is a product safety guard, not medical guidance.UnitPreferenceService) only changes the profile's unitSystem: stored values stay metric and nothing is converted, the plan is kept, and an already reviewed assessment stays reviewed. A workout records its weight unit (kg/lb) when it starts.TabsPage) decides what happens. Pages open it with QuickAddLauncher.show(). Ship an action by flipping available and handling (actionSelected).--color-text-on-muted (AA), every progress bar has a label/value text, state never relies on color alone (filled icons for the active tab, text for trends and "Coming soon"), and reduced-motion is honoured via the motion tokens.