← The collectionDigital products / 2026

BigBack

In development

A clearer picture of progress.

A mobile fitness experience connecting food logging, physique insights, a personal plan, and coaching.

Self-initiated mobile product
BigBack development interface with a dark theme, orange progress ring, and daily food summary

The project

Built a connected mobile app and backend spanning onboarding, food logging, scan explanations, progress, and coaching.

Our contribution

  • Product design
  • Mobile development
  • AI integration
  • Data visualization

Context

Self-initiated mobile product

In development / 2026
01

Inside the project

Connect the daily actions.

BigBack brings a longer-term fitness goal into the decisions made each day. The experience connects onboarding, a physique blueprint, food logging, progress, and a coach, rather than asking each screen to tell a separate story.

A dark interface, strong orange accents, and a clear hierarchy give the information a consistent home on a small screen.

02

Inside the project

Useful AI needs a careful data layer.

Food logging separates language understanding from nutrition data. The model identifies the food and quantity; nutrition lookups supply the associated macros. Photo analysis and coaching run behind authenticated backend functions.

The engineering work also covers the less visible moments: interrupted requests, camera permission, account recovery, quantity corrections, and limits on expensive operations.

03

Inside the project

One number, with its meaning intact.

An important refinement aligned how the app describes physique estimates. Measured estimates, goals, and projections became distinct values, with consistent wording across the dashboard, scan result, and coach.

Aligning that language made the data model part of the interface design. The same value needed to carry the same meaning wherever someone encountered it.

Project notes & credits

Product direction and development: Everest Egenhofer, with AI-assisted implementation.

Development interface with demonstration data. Physique estimates are not clinical measurements.

From the process

BigBack
Product thinking

One number, with its meaning intact.

A September 1 BigBack development record describes aligning the dashboard, scan result, and coach around the same physique estimate. Measured values, goals, and projections became distinct types with consistent wording. The lesson was a design one as much as an engineering one: a useful number needs a clear meaning everywhere it appears.

Something here sparked an idea?Let’s explore it.