Onboarding wireframes · CalorieCount planning artifact

Minimum setup, with reasons.

Account creation and body inputs are kept compact. Sensitive fields explain their purpose at the moment they are requested; units stay visible and editable.

1 · Welcome and account

Promise, expected effort, and familiar account actions. No tour of the full product.

9:41● ◒ ▰

Optional neutral illustration area

Remember what works.

Set up your starting target, then go to Today. About 3 minutes.

CONFIRMED Continue with Apple is account authentication only. It never grants Apple Health permission.

OPEN Can an experienced user defer account creation until after the first meal, or is identity required for health permissions and data ownership?

2 · Body data and units

Collect only the inputs needed for eligibility and the energy estimate.

9:41● ◒ ▰

Set up

About you

These details help check whether an automated target is appropriate and estimate energy needs.

Age

years

Height

Current weight

123 456 789 ⌫0.

Decimal separator follows locale. Validate range and precision after entry.

Sex used for this energy estimate

Why does the estimate need this?

Optional. You choose what to share and confirm every available value.

CONFIRMED Current weight uses one direct numeric field with decimal keypad and visible kg/lb control. No picker alternatives appear in the flow.

RULE Explain the sex-specific coefficient, keep it private, and separate it from gender identity.

STATE Impossible values error inline; unusual plausible values require confirmation.

2A · Apple Health permission

A distinct, contextual step explains the requested categories before the iOS system permission.

9:41● ◒ ▰

Apple Health

Fill available details from Apple Health?

This is optional. We request read access only after you continue, and only the data you allow can be used.

Height and weight for editable body fields
Recent steps and activity for activity context
Recent workouts and duration for training context

Separate permission: signing in with Apple did not grant this access.

ILLUSTRATIVE IOS SYSTEM STEP Allow Health data access?

The system shows the available categories and your current sharing choices.

RULE Permission is optional, category-specific, and never described as automatic or complete.

FALLBACK Denied access returns to editable manual body fields and the manual activity path.

2B · Confirm available health data

Available values are attributed, editable, and mixed safely with required manual inputs.

9:41● ◒ ▰

Check your details

Confirm what was available.

Apple Health filled two fields. Review them and enter anything that is missing.

AgeEntered manually

years

HeightApple Health · editable

Current weightApple Health · updated today · editable

Sex used for this energy estimate Private input · never filled from Apple Health

Why does the estimate need this?

Limited data: unavailable fields stay blank and editable. Existing manual values are never overwritten without confirmation.

RULE Imported values remain drafts until confirmed. Show source and recency when available.

PRIVACY Equation sex keeps its contextual explanation and must be entered manually.

One gate, two honest outcomes.

The safety questions themselves require clinical copy review. These screens focus on the resulting product behaviour: eligible users may review an estimate; automation-ineligible users never see an automated target—not even a neutral maintenance estimate.

3A · Eligible outcome

Continue toward an estimate without overstating certainty.

9:41● ◒ ▰

Safety check

We can prepare a starting estimate.

Your answers are within the current boundary for automated guidance. The result will still be an estimate that you review.

Nothing changes your target without your approval.
You can choose a manual target instead.
We will show the estimate’s basis and confidence.

No number yet

Goal and activity context still need to be collected before an estimate can be calculated.

RULE Eligibility is permission to calculate, not a claim of clinical certainty.

3B · Manual-only safety outcome

Confirmed policy branch. No automated maintenance estimate appears anywhere in this path.

9:41● ◒ ▰

Safety check

Use a target you set yourself.

Based on your answers, we will not calculate or recommend a calorie target. You can still use the food log with a manual target.

Manual target only

No suggested number, maintenance estimate, deficit, surplus, or automatic weekly calorie change will be shown.

For personalised nutrition guidance, talk with a qualified clinician who understands your circumstances.

CONFIRMED This path stays manual-only for Lose, Maintain, Gain, and Recomposition.

OPEN Can a person continue with calorie visibility disabled and no target, or must a manual target be entered to finish setup?

Four goals, equal standing.

The chooser describes intent rather than promising an outcome. Safety status changes the target path later; it does not remove or disguise a goal.

4 · Goal chooser

Lose, Maintain, Gain, and Recomposition are all first-class options.

9:41● ◒ ▰

Your goal

What are you working toward?

This sets the direction of your target and what progress means. You can change it later.

RULE Maintain is not a fallback or “no goal.” Recomposition does not promise simultaneous fat loss and muscle gain.

OPEN When a goal changes later, which onboarding questions repeat and does the 21-day outcome window reset?

Ask where this plan should land.

Every goal asks for a destination after the goal choice. Where bounds are approved, the coarse slider and exact numeric field update one value. Recomposition can explicitly defer when no credible sourced baseline exists. A destination is intent, not a promised outcome.

5L · Lose destination

Landing weight sits below current confirmed weight and above the safety-limited minimum.

9:41● ◒ ▰

Lose

Where would you like to land?

This helps frame progress. It does not make the calorie target more aggressive.

Landing weight

Safety-limited minimumCurrent · 82.1 kg

Illustrative value. Locale, units, target BMI, and approved safety rules determine the real range.

RULE Landing weight never increases the selected pace or bypasses deficit caps, intake floors, or target-BMI safety.

5M · Maintain destination

Maintain defaults near current weight. A materially different destination prompts a goal change.

9:41● ◒ ▰

Maintain

What weight do you want to maintain?

Choose a landing point close to your current confirmed weight.

Landing weight

Lower intentHigher intent

Goal check: Maintain stays at the current confirmed weight until the approved stability band exists. A lower or higher intent routes to Lose or Gain.

OPEN The exact Maintain destination band remains tied to the unresolved stability model.

5G · Gain destination

Landing weight sits above current confirmed weight without increasing the conservative starting surplus.

9:41● ◒ ▰

Gain

Where would you like to land?

This sets a progress destination. Training experience still controls the starting surplus.

Landing weight

Current · 82.1 kgPersonalized upper bound

Illustrative value. The destination does not promise that all added weight will be muscle.

RULE A farther destination never exceeds the experience-based surplus and 500 kcal/day cap.

5R · Recomposition destination

Body fat is a progress reference only and requires a comparable measurement source.

9:41● ◒ ▰

Recomposition

Confirm the body-fat observation first.

A value, source, and date stay together. Changing the method creates a new observation; it never relabels an older one.

Measurement source

Observation date

Now choose the destination. Future comparisons use a compatible measurement method. This value does not calculate calories.

Landing body fat

Direction only · bounds pendingBelow current · 22.8%

Clinical bounds must be approved before this value can be confirmed.

RULE Never infer body fat, diagnose a selected value, or compare incompatible measurement methods.

OPEN Clinical review must define slider bounds before product implementation.

DEFERRED COPY If Recomposition was set later, either acknowledgement says: “Your goal and starting point are set. You can add a body-fat destination later.” The CTA remains Go to Today.

Ask only what changes the target.

Each goal branches into the minimum inputs currently supported by the recommendation proposal. Maintain’s detailed adjustment rules remain explicitly unresolved.

6L · Lose questions

Selected pace, with safety caps applied later.

9:41● ◒ ▰

Lose

Choose a starting pace.

Slower rates may better support performance and recovery. The final target still respects the safety boundary.

System rule: cap the initial deficit at 20% of maintenance or 750 kcal/day, and never cross the approved intake floor.

OPEN Should the UI ask a performance-priority question, or infer the slower recommendation from existing training context?

6M · Maintain questions

No extra input is required for the starting estimate.

9:41● ◒ ▰

Maintain

Keep weight broadly stable.

For eligible users, the starting target is the estimated maintenance value with no deficit or surplus.

No extra question proposed

Continue to activity context. The stability band and weekly adjustment cadence are still under product and clinical review.

Unresolved behaviour: do not ask for a “tight” or “relaxed” maintenance band until the adjustment model is confirmed.

PENDING Stability band, persistence threshold, review cadence, and automatic weekly adjustment.

6G · Gain questions

Training experience controls the conservative starting surplus.

9:41● ◒ ▰

Gain

How long have you trained consistently?

This helps avoid recommending a larger surplus than your current training stage supports.

System rule: begin at 10%, 7.5%, or 5% above maintenance by experience; cap the initial surplus at 500 kcal/day.

6R · Recomposition questions

Training behaviour and explicit priority determine whether a small deficit can be offered.

9:41● ◒ ▰

Recomposition

What supports this goal?

Calories alone cannot credibly recommend recomposition.

Progressive resistance training

System rule: never offer a surplus under Recomposition. Muscle-first intent routes to Gain.

OPEN If progressive resistance training is “No,” route to Maintain or preserve Recomposition with an explicit no-prescription explanation?

Activity source, not wearable calories.

Apple Health improves activity classification when enough representative history exists. It does not add exercise calories to an activity-adjusted target. A clear manual route remains equally available.

7A · Confirm activity from Apple Health

Available recent activity and workouts prefill a reviewable category, not a calorie answer.

9:41● ◒ ▰

Activity

Does this match a typical week?

Available Apple Health data from the last 14 days suggests an activity category. Confirm it or choose another.

Suggested: Active

Based on 10 days with usable coverage. This is a category for the estimate, not exercise calories added to your target.

StepsAvailable · 10 days

Workouts4 sessions

Training duration212 min

RULE Show coverage and let the person correct an unrepresentative period, illness, travel, or device gap.

7B · Activity without health data

Connect through the distinct permission step or use the short manual assessment.

9:41● ◒ ▰

Activity

How active is a typical week?

We use activity to classify your starting estimate—not to add exercise calories twice.

Apple Health confirmation: ask the person to review the resulting category when history is sparse, implausible, conflicting, or unrepresentative.

Manual assessment: ask about work, transport, steps if known, and structured training; start at low confidence.

RULE Use wearable data for activity classification, not as the target itself.

Review what the system knows—or enter your own.

Eligible users see a transparent estimate and can switch to manual. Automation-ineligible users see only the manual entry state, with no anchoring estimate or implied recommendation.

8A · Recommended target review

Illustrative eligible-state values. The range and evidence remain visible.

9:41● ◒ ▰

Starting target

Review your starting estimate.

2,250 kcal/day · illustrative Maintain example

Plausible range2,025–2,475

GoalMaintain

Landing weight82.0 kg

Activity sourceManual

Starting confidenceLow

Method2023 EER

See how this was estimated

Maintain pending: the starting maintenance estimate is supported; detailed weekly Maintain adjustment is not yet confirmed.

RULE A recommendation exposes basis, range, evidence, confidence, and manual override before acceptance.

8B · Eligible manual override

Manual entry remains available without hiding the estimate the user declined.

9:41● ◒ ▰

Starting target

Set your own target.

Your calculated estimate was 2,250 kcal/day. It will not replace the number you choose.

Daily calorie target

kcal/day

Control: the app records that this is a user-entered target and does not silently replace it later. The landing destination remains intent, not a calorie calculation.

8C · Manual-only target entry

The safety path contains no calculated value, range, confidence, or recommendation anchor.

9:41● ◒ ▰

Manual target

Enter your calorie target.

Use a number you have chosen yourself or agreed with a qualified clinician. We will not suggest a number in this path.

Daily calorie target

kcal/day

No automated changes

Weekly reviews may show your own validated record, but they will not calculate or propose a calorie-target change.

Destination retained: your landing destination can frame progress, but it does not create an automated target or timeline.

CONFIRMED Do not display an automated neutral maintenance estimate in this path.

OPEN Define validation and recovery copy for an implausible manually entered target without converting the experience into a recommendation.

Acknowledge setup, then continue to Today.

This beat follows target confirmation in both paths. It marks the person’s first meaningful step and provides one unconditional next action: enter the home screen.

9A · Eligible setup acknowledgement

The eligible path acknowledges the confirmed starting estimate without repeating the preceding review screen.

9:41● ◒ ▰

Setup complete

✓ Your starting plan is ready. You’ve taken the first step: your goal, destination, and starting point are set.

Confirmed estimate: the starting target reviewed on the previous screen is now set. Today owns the next action.

9B · Manual-only setup acknowledgement

The same acknowledgement, with the user-entered source preserved and no implied recommendation.

9:41● ◒ ▰

Setup complete

✓ Your starting plan is ready. You’ve taken the first step: your goal, destination, and starting point are set.

Manual-only remains manual: the target entered on the previous screen remains user-provided, with no automated recommendation or weekly adjustment. Today owns the next action.

RULE Celebration does not convert a user-entered target into advice or imply automated changes.

Today owns food logging.

This destination reference is outside onboarding. Both acknowledgement paths arrive here directly, where food logging is available as the primary home-screen action.

10 · Today destination

Setup is complete. The real home screen presents today’s state and food logging without an onboarding fork.

9:41● ◒ ▰

Today

Today

Your starting point is set. Track food here when you are ready.

Calories0 logged

Protein0 logged

Meals and reusable entries appear here after logging. No first meal is fabricated during onboarding.

BOUNDARY Today is the destination, not another onboarding step. Food logging begins from the home screen.

CONTINUES IN HOME Review the full neutral Today, logging-entry, and weekly-layer storyboard in Home / Today wireframes.

Decision register

Confirmed constraints are built into the storyboard. Open items are labelled where they affect screen count, routing, or copy; they should be resolved before medium-fidelity interaction design.

Status	Decision	Current wireframe treatment	Why it matters
Confirmed	Four first-class goals	Lose, Maintain, Gain, Recomposition receive equal chooser weight.	Prevents Maintain from reading as a fallback.
Confirmed	Every goal asks for a destination	Lose, Maintain, and Gain use landing weight; Recomposition uses an optional body-fat value/source/date observation and can store an explicit deferred state. Approved sliders synchronize with direct entry; unresolved Maintain and Recomposition sliders stay disabled.	Frames intent without promising an outcome or changing calorie logic.
Confirmed	Manual weight entry uses direct numeric input	Screen 2 shows one decimal-keypad field with a clear kg/lb control, locale-aware formatting, and commit-time validation. Wheel and hybrid concepts were rejected and are absent from the storyboard.	Keeps a short, known value fast to enter without presenting false product choices.
Confirmed	Apple authentication and Health access are separate	Continue with Apple signs in only. Apple Health uses an optional contextual permission, attributed editable values, and manual fallback.	Prevents implied consent and hidden data sourcing.
Confirmed	Safety-sensitive path is manual-only	No automated target or neutral maintenance estimate; no weekly auto-change.	Avoids an unsafe recommendation disguised as “neutral.”
Confirmed	Setup acknowledgement leads directly to Today	Both target paths retain distinct acknowledgement content and expose exactly one CTA: Go to Today. Food logging is a primary home-screen action, not an onboarding decision.	Celebrates progress without repeating the target review or introducing a false log-now/log-later fork.
Open	Maintain adjustment model	Initial estimate is shown only for eligible users; weekly adjustment remains off.	Stability band, persistence, and cadence are not approved.
Open	No-training Recomposition branch	Flagged at the goal-specific question.	Changes whether the flow reroutes to Maintain or preserves the label with no prescription.
Open	Manual target without calorie visibility	Manual entry is shown; targetless continuation is not assumed.	Affects accessibility, safety, and completion requirements.
Open	Account timing and skip behaviour	Account remains first; acknowledgement proceeds directly to Today.	Determines time to value and what can be stored before identity exists.
Open	Imported/repeat suggestion on first use	Deferred to Today’s food-logging surface; it is not part of onboarding.	A new account cannot honestly have a likely repeated meal.
Open	Mid-plan goal switching	Starting a new plan repeats goal, destination, baseline, safety, and target confirmation. Editing the goal inside an active plan is not demonstrated.	Determine whether any mid-plan goal change must create a new plan.