Forky AI for Apple Watch.
Forky AI reads your Apple Watch active and basal calorie burn from HealthKit, no manual entry, no second wearable. Every meal you log in Forky writes back to the Apple Health app under Nutrition, so the iOS health graph stays unified. The daily target on the Track tab moves with your real burn — finish a 90-minute run and the macros lift before you finish stretching. Shipping with Forky v1.2, after the v1.0 launch and HealthKit entitlement land.
- 01
- Active energyCalories burned via movement and workouts, read directly from HealthKit. Replaces the BMR static estimate Forky uses for users with no wearable.
- 02
- Basal energyYour resting metabolic rate as the Watch measures it, not a TDEE formula. This catches the day-to-day BMR drift that fixed targets miss.
- 03
- WorkoutsType, duration, intensity. Forky uses the workout window to time its meal-timing nudges and to bias post-workout meals toward protein and carbs.
- 04
- Body massWhenever you weigh in to the Health app, Forky updates your daily target so the macro plan tracks your actual scale curve instead of the number you typed at onboarding.
Open Forky after v1.2, grant HealthKit permission for the four data types above, and the Track tab gains a top banner: Active 421 · Basal 1,580 · Eaten 1,720 → Deficit 281. Forky also writes every meal you log to the Nutrition section of Apple Health so the rest of the iOS ecosystem — sleep apps, fitness Forkyes, your doctor — sees the same numbers Forky sees.
v1.2 reads but doesn't ride the Workouts UI inside Apple Health. We don't post Forky meals as Workout entries (they belong in Nutrition, not Workouts). We also don't pull heart-rate variability or sleep — both are useful, neither shifts the calorie target enough to justify the entitlement surface in v1.2.
- 01“Active 312 kcal at 11 a.m. on a Tuesday — you've burned a third of your usual daily active by lunch. Adding 180 kcal to today's target.”
- 02“You logged a 1,400 kcal lunch on a 720-active day. Dinner suggestion: a 480 kcal bowl, not the 750 the meal plan defaulted to.”
- 03“Your weight dropped 1.2 kg over four weeks faster than the deficit math says. Rebuilding your target up to 2,140 — you're under-eating, not magically melting fat.”
- 04“Run finished at 6:14 p.m. — your dinner suggestion just shifted to a 35g-protein meal instead of the salad it had queued.”
Yes. The Track tab uses a BMR estimate plus your logged meals to compute deficit or surplus. The Apple Watch integration just makes the kcal_out side measured instead of estimated. The app is usable end-to-end with zero wearables.
No. v1.0 ships with manual macro logging, fridge and meal scanning, and recipe import. The HealthKit READ + WRITE integration arrives in v1.2 once the App Review entitlement lands. Whoop direct OAuth comes earlier in v1.1 — see forkyai.com/whoop.
Yes — when v1.2 ships, every meal logged in Forky writes back to Apple Health under Nutrition (Dietary Energy, Protein, Carbohydrates, Fat). You can revoke this at any time from Settings → Privacy → Health → Forky AI.
Any Apple Watch that writes Active Energy and Workout to Apple Health works — that's every model since Series 1 on watchOS 4+. Older watches won't have continuous heart-rate, but that doesn't matter for calorie tracking.
No standalone Watch app at v1.2. Forky is iPhone-only at launch — the Watch is a data source via HealthKit, not a destination. A first-party Watch complication is on the roadmap for v1.3.
Install Forky AI and pair your Apple Watch from Settings → Connected Apps.