What changed in Leptir

One clearer public Leptir

Landing, Manual, Privacy, and Evolution now share a responsive public-page system and describe the product in the same direct language.

• The Manual now covers web logging, optional Telegram capture, editing, Account, and exports.
• Landing previews no longer imply adherence scoring, personal targets, or 14-day intelligence that is not shipped.
• Privacy copy distinguishes current controls from details that still require explicit confirmation.

What changedThe promise before signup is closer to the product people actually use.

Leptir 2.0 became the daily experience

The redesigned Day experience became the default, followed by a shared application shell for Logs, Workouts, Account, Connect, and Export.

• Day keeps meals, workouts, and weight in one timeline with a calmer information hierarchy.
• Account became the home for identity, timezone, food context, Telegram, appearance, and exports.
• Navigation, spacing, and controls were tightened for iPhone-sized screens.

What changedSigning in now feels like entering one application instead of a collection of separate tools.

Edits became trustworthy history

Meal and workout corrections now preserve a clearer record of what changed instead of quietly replacing the previous interpretation.

• Meal revisions can be reviewed as version history.
• Reanalysis follows the revised meal while preserving user-authored content.
• Workout editing and removal reached the same daily timeline workflow.

What changedPeople can correct Leptir without losing the history behind the correction.

Telegram became quieter and more accountable

Telegram logging gained clearer estimate disclosure, restored day commands, broader undo, and safer behavior in group conversations.

• Meal receipts distinguish estimates and user-provided nutrition more clearly.
• Undo can remove the latest eligible meal from across the logged day.
• In group chats, Leptir stays silent unless it is directly invoked.

What changedChat capture is easier to trust and less likely to interrupt the wrong conversation.

Account access and production boundaries hardened

Timezone handling, password recovery, internal documentation access, and the public domain were tightened around the production experience.

• Profile timezone controls keep day grouping accurate without changing stored event instants.
• Password forms now show the real requirements and support clear visibility controls.
• leptir.io is enforced as the canonical public origin, and internal admin documentation is admin-only.

What changedAccount and deployment behavior is more predictable at the edges where trust is easiest to lose.

One timeline, with verifiable releases

The Day backend gained a unified timeline for meals, workouts, and weight while production build identity made the running release easier to verify.

• A shared timeline service orders different event types on the same day.
• Health and build metadata can identify the version running in production.
• GitHub Actions became the repeatable test gate for changes headed to main.

What changedThe daily record became more coherent, and releases became easier to confirm after deployment.

Same-day readouts across web and Telegram

Telegram /next and the web Today status now use the same deterministic snapshot of logged meals, workouts, macros, and meal timing.

• Logged workout count, duration, and coarse activity heuristics can change the wording.
• Higher-output days avoid generic calorie-restriction language.
• The readout does not use wearable recovery data.

What changedThe same logged day produces a consistent status in both surfaces.

LP2 public-page foundation

The landing page established the slate color tokens, restrained typography, and shared marketing navigation now used by Leptir’s public pages.

• Manual, Privacy, and Evolution share the public navigation and design tokens.
• The signed-in dashboard remains a separate application surface that is still evolving.

What changedPublic information now has a clearer visual relationship to the landing page.

LP2 landing & themes

The marketing surface gained a token-driven design system with dark, slate, and soft-light presentation options.

• Theme tokens centralize color, shadow, and surface language.
• Command-center mock and narrative emphasize interpretation over raw scores.

What changedThe public introduction became calmer, clearer, and more distinctive.

Profile editing & local time integrity

Meal editing, re-analysis, and dashboard feeds tightened around the user’s timezone and honest timestamps—reducing “wrong day” drift between Telegram and web.

• PATCH-style edits and optional reanalysis keep the log aligned with intent.
• Feed and summaries respect profile-local dates for the same truths everywhere.

What changedThe timeline reads as a believable day, not a server-default artifact.

Telegram trust layer

Meal receipts and follow-ups were simplified: minimal receipts, neutral /next copy, and fewer mixed signals between channels.

• Telegram offers fast chat capture; the web supports logging, review, and editing.
• Nutrition scores align with final macro truth after reconciliation.

PrincipleIf the bot sounds robotic, people stop logging—clarity > verbosity.

What changedHigher confidence that what you see in chat matches what the dashboard remembers.

Workouts as structured memory

Workouts gained a durable mirror layer—optional duration and structured metadata—so training could inform exports and downstream interpretation without losing raw logs.

• Workout rows attach to facts with additive metadata.
• JSON export can include workout context where present.

What changedMovement stops being free-text-only when you need structure downstream.

One “today” everywhere

Daily nutrition totals for “next move,” dashboard cards, and summaries were unified around the same day boundary and timezone rules.

PrincipleSplit sources of truth quietly erode trust—one pipeline won this fight.

What changedTelegram and web no longer disagree on the same calendar day’s numbers.

Data portability

Exports matured: domain-shaped CSV and JSON, clearer signed-in ZIP flows, and workout-aware joins where applicable—so ownership is practical, not theoretical.

• Meals, workouts, and weight could leave the system in useful shapes.

What changedUsers can audit and reuse their history outside Leptir.

Product doctrine & transparency

Leptir documented its stance: user ownership of data, visible assumptions in interpretation, and copy on landing and early dashboard aligned with that doctrine.

PrincipleTransparency isn’t a feature flag—it’s the default posture.

Macro truth & food lineage

Macro overrides, food DB linkage, and source propagation hardened the chain from ingestion → stored row → score—so numbers don’t float away from what was reviewed.

What changedInterpretation could be challenged without breaking the audit trail.

Unified nutrition chart

The dashboard gained a coherent week-scale view of protein, carbs, fat, and calories—making pattern visible before narrative.

What changedMacro structure became glanceable across days, not only meal by meal.

Manual as onboarding

The user manual moved from placeholder to a real first-run guide—Telegram prefixes, pairing, and where to look on the web.

What changedNew accounts had a single linkable answer to “how does this work?”

Production-shaped runtime

The app split into explicit process types (web, bot, migrate), added health checks, stricter configuration, and rate limiting suited to a small but real deployment.

• Failures become visible early; migrations stop surprising app boot.

PrincipleReliability is part of trust—the service has to stay up to be honest.

More consistent receipts across Telegram and web

Formatting and copy paths moved closer together so the same saved log is described more consistently in Telegram and on the web.

What changedUsers get fewer conflicting messages about the same entry.

MVP foundations: edit, weight, score

Meal editing landed, weight history and graphing stabilized, nutrition scoring integrated end-to-end, and export/help paths reached “shippable daily driver” quality.

What changedLeptir crossed from demo to something people could run as a primary logger.

Web surface & accountable pairing

Public landing, user manual, password reset, Telegram re-pairing, and migrations aligned so signup → connect → log was a coherent journey.

• /connect and profile navigation converged on /me as home base.

What changedIdentity and device linking stopped feeling improvised.