READ THE EVIDENCESource-confirmedSynthetic reproductionUser anecdotesProposed / not shipped
01
Preserve the foundation
A clearer promise. Not another app.
VoiceFit already has multimodal capture, ingredient correction, previous-session sets and data-aware coaching. Improve their continuity inside Today / Train / You, rather than replacing that structure. [1]
Existing surfaceKeepMake dependable
TodayFood & daily context
Meal capture Ingredient edits Pending estimates
Faithful repeats Explicit local day Unknown ≠ zero
Proposed segment: busy recreational strength trainees who also want practical nutrition tracking. This is a focus hypothesis, not validated market sizing. Templates, timers, export, unit settings and accessible controls are useful baseline utilities; competitors already document many of them. [4][5]
02
Where the work really happens
Capture is only the beginning.
A quick input is not a completed task. Follow a familiar meal or a final gym set through repair and saving; the lower lane is a proposed future, not shipped behavior.
Missing nutrition in quick repeat is reproduced with synthetic fixtures; the extra repair burden is a workflow inference, not a measured user task time.
Finish risk is source-traced, not a native event-order reproduction. Exact unit and set-count failures were synthetically reproduced. [1]
03
Trust before reach
Eight places to protect the record.
Priority reflects potential impact, not measured incidence. Open a finding for the proposed fix and the evidence needed to call it closed.
Contain firstPrivacy + recorded truth
AOwnership & privacy safeguardsSource-confirmedP0
Strengthen account boundaries and remove raw health-related content from ordinary server telemetry. The audit does not establish production exploitation or observed customer harm. [2]
Proposed fix
Enforce ownership throughout record access; retain redacted stage and request telemetry instead of sensitive content.
Acceptance gate
Negative multi-account tests pass; retention and logging review finds no raw health payloads.
BUnits, set counts & exercise identitySynthetic reproductionP0
Injected fixtures reproduce incorrect unit handling and lost set counts. Multi-exercise review also needs distinct identities. [1]
Proposed fix
Keep original units, normalize once and represent exercise groups explicitly.
Acceptance gate
Mixed-unit, multi-set and multi-exercise fixtures retain the confirmed values and identities.
CFinish without losing draftsSource-confirmed riskP0
Finish does not check or flush edited draft rows before completion disables editing. Native event-order behavior was not tested. [1]
Proposed fix
Validate and await dirty-row saves before completion; allow completed-session corrections.
Acceptance gate
Finish during pending edits either preserves confirmed fields or clearly blocks completion; reopen and verify.
DTruthful offline persistenceSource-confirmedP0
Persisted read caches exist. The advertised offline write queue is not durable in the inspected implementation. [1]
Proposed fix
Correct the copy now; add durable user-scoped drafts and explicit local, syncing and acknowledged states.
Acceptance gate
Force-stop, reconnect, expired-auth and account-switch tests preserve the right user's logical records.
EOne local day across viewsSource-confirmedP0
Calendar-day boundaries are inconsistent across dashboard and coaching paths; meal history has a compensating mobile path. [1][2]
Proposed fix
Use one validated timezone-aware day-range rule and show the entry date on its receipt.
Acceptance gate
DST, midnight and travel fixtures agree across history, Today and Coach.
A synthetic delayed interpretation overwrote a reviewed correction. Retry safeguards are stronger for workout batches than other creates. This is not a real-database concurrency result. [2]
Proposed fix
Extend operation receipts; make edits conditional on revision; retry estimates on the same record.
Acceptance gate
Response-loss and stale-job fault fixtures yield no duplicate logical records and preserve reviewed corrections.
Account verification/reset needs continuation. Asking can be mistaken for recording; failed estimates and selected dates need recovery. Sparse trends and accessibility also need clearer semantics. [1][2]
Proposed fix
Resume auth flows, clarify uncertain intent, retry the same entry, preserve unknowns and offer labelled accessible actions.
Acceptance gate
Native auth/resume, ambiguous-input and sparse-data fixtures pass; real VoiceOver/TalkBack and large-text checks pass.
8 findings · priority is impact-based, not an incidence estimate.
04
The comparison that matters
Voice and AI are already here.
The defensible hypothesis is less work per correct task. These are vendor-documented capabilities at the research snapshot, not installed-app benchmarks or a ranking.
Capability documented in reviewed sources · “?” means unknown here, not absent.
Documentation establishes availability claims, not speed, accuracy, reliability or installed October 2026 behavior. MacroFactor's “no shared coaching at launch” wording does not establish a continuing gap. Unknown cells reflect this audit's coverage, not a claim that the app lacks a feature.
Jobs → candidate features
Less work through repetition and repair.
Selected posts and reviews are anecdotal and nonrepresentative. The connections are an audit synthesis, not demand shares.
Choose typing or speaking [17]→Optional voice, same record
Return without logging debt [27][22]→Pause, resume, optional streaks
05
Focused differentiation experiments
Start with two. Keep six testable.
The first two bets build on existing strengths. Every screen below is a local concept illustration, not a shipped feature; controls never access your microphone or save real health data.
Proposed concept / local demo01
“My usual, but…”
Reuse confirmed ingredients, then change just the portion. Saved meals already exist; the test is faithful reuse with less repair. [1][7][23]
TodayConcept
PERSONAL RECIPE · CONFIRMED BASE
My breakfast bowl
Oats
1 familiar portion
Yogurt
Unchanged
Banana
Unchanged
Same named recipe; confirmed base retained.
Illustrative portions · no nutrition estimate
Change a field, not the recipe.
Ingredients and confirmed nutrition must survive the clone. The demo only changes an illustrative portion.
Scope & decision gate
Smallest scope
Faithful clone, personal name, portion change, provenance, reset.
Success signal
Faster correct repeat logs; fewer repeated edits versus saved-meal baselines.
Reject / reshape
Setup costs exceed savings or remembered defaults corrupt novel meals.
Proposed concept / local demo02
A quiet gym copilot
Previous comparable sets, silent confirmation and optional voice share one draft. Hevy already copies previous values; continuity and correct context must add the value. [1][12][18]
TrainConcept
ILLUSTRATIVE SESSION
Back squat
Previous comparable working set 80 kg × 8 reps
One tap uses the displayed set.
SAME DRAFT → SAME RECORD
Not confirmed yet · local illustration
No audio capture. Local demo state is not a durable app record.
The mode changes. The record does not.
A real implementation needs local durability, sync receipts and a Finish gate.
Scope & decision gate
Smallest scope
Durable rows, reliable Finish, unit-safe structured input and one-tap next set.
Success signal
Less interruption per correct durable set; no lost writes in fault tests.
Reject / reshape
Reject voice-first positioning if optimized silent entry wins.
Proposed concept / local demo03
A repairable capture receipt
Show what was understood, for which day and where it is saved. A correction patches the same record and invalidates dependent summaries. [1][2]
Today / lunchEstimated
Dal & rotis
3 rotisDal unchanged
EstimatedSavedCorrected
Estimated only. Saving here changes local demo state, not a server.
One illustrative record throughout · no nutrition precision implied.
Scope & decision gate
Smallest scope
Date/scalar corrections, same-record estimate retry, conditional atomic edits and undo.
Success signal
Fewer recaptures and duplicates; understandable estimate and save states.
Reject / reshape
The receipt becomes a mandatory complex review form for every entry.
Proposed concept04
One evidence-linked weekly decision
Offer one feasible action, with coverage and inspectable evidence. Sparse data should trigger abstention, not an automatic calorie cut. [9][11]
ILLUSTRATIVE COVERAGE
✓M?T✓W?T✓F?S?S
Partial food record ≠ low intake.
ONE POSSIBLE ACTION
Keep targets unchanged.
Ask whether the missing days were unlogged before interpreting intake.
Actual finish time, less replanning and expert-rated preservation of intent.
Reject / reshape
Real constraints reduce it to a generic workout generator.
Proposed concept / local demo06
A reversible coach contract
Show affected fields and supporting observations before applying a scoped change. Start with program logistics, never autonomous medical or calorie decisions.
Reason: use available equipment while preserving the main work. This is illustrative, not a real recommendation.
Awaiting approval; your program has not changed.
Scope & decision gate
Smallest scope
Proposal, diff, approval, saved receipt and undo linked to record revisions.
Success signal
Users detect stale advice and can reject or reverse incorrect changes.
Reject / reshape
Scope is unclear, reversal fails, or stale evidence keeps driving advice.
06
Dependencies, not dates
Earn the next layer.
Use exit gates instead of sprint promises. Durability enables the two focused slices; bounded coaching depends on corrected records and honest coverage.
A / EXIT GATE
Contain before expanding.
Ownership/privacy tests pass; units and set fixtures retain confirmed truth; Finish preserves edits; native signup/reset completes.
B / REQUIRES A
Survive interruption.
Offline force-stop, reconnect, account-switch and response-loss tests preserve one logical record. Stale edits cannot overwrite corrections. DST views agree.
C / REQUIRES B
Compare real completed tasks.
Within-person comparisons include repair time and optimized manual baselines. A consented pilot shows useful voluntary repeat use.
D / REQUIRES B + C
Prove a useful, bounded decision.
Shadow-mode coaching beats a rules baseline, invents no facts or actions in acceptance fixtures, shows coverage and allows rejection/reversal.
A thin reliability layer / proposed architecture
Correct once. Every dependent view catches up.
Preserve account-cache isolation and workout-batch safeguards. This is an architectural recommendation, not a claim that a durable outbox already exists. [1][2]
01CaptureVoice / photo / tap Intent + original context
02Durable local recordUser-scoped draft Survives interruption
04InterpretationEstimate with revision Actionable failure
05CorrectionPatch same record Reject stale updates
06Derived summariesTotals + history + Coach Invalidate stale advice
ONE LOCAL ILLUSTRATION
Meal receipt: 3 rotis · initial revision
→
Today summary: 3 rotis
Coach evidence: initial revision
No nutrition arithmetic or network save; the demo illustrates propagation.
What should wait?
Defer broad social feeds, always-listening voice, camera form assessment and generalized autonomous programming until the core workflow wins. Add baseline utilities as needed; do not pitch timers, exports or accessible controls as inventions. Avoid a rewrite and a generalized multi-agent system.
07
Measure the whole task
The clock stops when the record is usable.
The primary metric is time to a correct, durable, usable record. Include repairs and saving, not just speech recognition or capture latency.
Incomplete lensCaptureRepair + save are left out
Whole-task lensCaptureRepair if neededSave + verifyUsable record
Stage decomposition, not a performance chart. Widths do not encode time. No task timings have been measured.
How to make the comparison fair
Randomize task order; compare participants' current tools and optimized silent entry. Include repeat and novel meals, changed recipes, mixed units, wrong dates, weak signal and mistaken estimates. Define denominators for duplicate/lost writes, faithful repeats, context errors and useful chosen actions before a pilot. Test guidance in shadow mode; do not infer clinical efficacy or causal nutrition/training effects.
08
What was actually verified
Tests are evidence. Not a quality score.
The audit exercised local source snapshots and injected fixtures. These counts describe that execution only, not native-device behavior or live-service reliability. [1][2]
Mobile83 tests passed
Required placeholder API-base configuration; fetches were mocked.
Backend4 + 41 tests passed
4 mocked batch unit tests; 41 injected synthetic handler tests.
Build checksTypechecks + contracts passed
Mobile/backend TypeScript and shared contracts build passed.
Still failing3 backend lint errors
A known unresolved check, not hidden by the passing test counts.
Not tested in this audit
Native Android/iOS devices; real microphone, camera or health-provider integration; live AI or production requests; real-database concurrency; customer interviews or product analytics.
Vendor pages document capabilities. Public anecdotes indicate possible jobs, not representative demand. Proposed screens and architecture are not shipped functionality. Recheck findings after changes.
Sources & provenance Private audit + public evidence
Source numbers match the underlying audit. External evidence was reviewed for the October 2, 2026 snapshot; pages may change. Only cited sources are listed. Private evidence is deliberately not linked.
[1]
VoiceFit mobile
Private source audit, 2 Oct 2026; detailed evidence shared privately.
[2]
VoiceFit backend
Private source audit, 2 Oct 2026; detailed evidence shared privately.