Most fitness apps can collect more data than I want to enter. I want to know what to do next.
Lean & Steady starts there. Onboarding collects enough information to make a first cut, recomp, or maintenance cycle. Before a payment decision, the user sees daily calories, protein, steps, meal allotments, a first milestone, and a review date.
The targets come from deterministic rules. An AI model does not make up calorie or protein numbers.
Today shows what is left. A meal changes the calorie and protein balance. Steps update one movement target. A short recommendation points at the next action. Meal photos can help estimate food, but the result stays editable and marked as an estimate before it changes the plan.
One weigh-in is noisy, so the app uses trends, consistency, weekly reviews, and a Day 29 decision loop. The cycle can continue, change, or enter a Quick Reset. Day 30 is a review point.
I built it in SwiftUI for camera work, Apple sign-in, private progress photos, Health access, widgets, and later App Intents. Health access stays narrow. The plan needs steps, not a copy of every health record.
No face scoring, attractiveness rating, public body leaderboard, or shame-based reminders. A daily coach should make one decision easier.
Lean & Steady is still in development. I will share the release here when it is ready.