Back to Projects

From a closed PDF to a useful nutrition habit system

Many nutrition plans start the same way: one PDF with the monthly menu, a few recipes, and too many things the user still has to solve alone. It works as a document, but not as a product.

Saria comes directly from that friction. The idea is to move from a static menu to a live tool that helps people plan, execute, adapt, and sustain a real nutrition routine without recalculating everything every time.

Instead of delivering “the diet” as a closed file, Saria turns that content into a web experience where the user can:

  • see what to eat today,
  • plan the week,
  • edit meals,
  • manage recipes,
  • generate a shopping list,
  • log what they actually ate,
  • and track progress with more context.

    • What problem it solves

    The problem was not just “digitizing a menu.” The real problem is that the PDF leaves out almost all of the operational layer:

  • 1.It does not adapt well to daily life: if you swap a meal, eat out, or cannot find an ingredient, the document does not help.
  • 2.It does not connect planning with execution: having a menu is one thing; turning it into shopping, recipes, logging, and follow-through is another.
  • 3.It does not scale into a product: a PDF works for one or two people, but not for groups, roles, admin workflows, or serious personalization.

    • Saria takes a different direction: the nutrition plan should be an interactive system, not a dead file.

    What Saria is

    Saria is a nutrition planning and adherence system built to transform something as passive as a PDF diet into a much more useful, actionable, and real-life-friendly experience.

    It does not stop at “showing a menu.” The ambition is much bigger: bring planning, execution, tracking, and adaptation into one product that people can actually live with.

    You can view it here: saria.bitsentry.xyz

    Core features

    1. Weekly planning as the product core

    The center of the product is no longer the PDF. It is the week.

    Saria is evolving toward a dedicated Semana module designed to let a user leave with a usable weekly food plan in just a few minutes. That includes:

  • creating or continuing a week,
  • reviewing days and meals,
  • editing specific slots,
  • swapping dishes,
  • and making the plan operational without bouncing across too many screens.

    • This is an important product decision: reduce noise and make planning one fast, focused task.

    2. Today view and actual follow-through

    Planning alone is not enough. The user needs a practical daily execution surface.

    The Today page brings together:

  • the meals of the day,
  • nutrition targets,
  • daily check-ins,
  • water, steps, weight, and sleep,
  • meal logging,
  • extra foods and add-on ingredients,
  • and quick actions around the current day.

    • That turns the product into an adherence tool, not just a menu builder.

    3. Recipes in quick and detailed modes

    One common friction in this kind of app is that full recipe creation is too heavy. Saria addresses that with two modes:

  • quick mode, for saving useful recipes without filling every macro per ingredient;
  • detailed mode, for users who want full nutrition granularity.

    • The recipe flow already includes:

  • ingredient autocomplete,
  • suggestions from the existing catalog,
  • import flows,
  • favorites,
  • filtering,
  • and editing without destroying previous data.

    • 4. Shopping list generated from the plan

    This is one of the clearest expressions of the product thesis.

    Once you move from PDF to system, the next logical step is turning the plan into action. Saria already defines a shopping list that aggregates ingredients from weekly or monthly plans, with:

  • category grouping,
  • weekly, biweekly, or monthly periods,
  • aggregated quantities,
  • and manually added wildcard items.

    • In other words, the plan stops being only visual and becomes something you can actually shop from.

    5. Groups, roles, and a multi-user foundation

    Another important jump is moving beyond a product shaped around two specific people.

    Saria already includes a direction toward groups + roles + real auth, allowing it to evolve from a highly custom tracker into a more reusable product:

  • end users,
  • isolated groups,
  • global admin,
  • group settings,
  • and group-scoped ranking and data access.

    • This does not only improve architecture. It also opens more realistic use cases for couples, families, coaches, or small accountability groups.

    6. AI where it is actually useful

    Saria does not try to “put AI everywhere.” It uses it in one very concrete and useful place: meal analysis from a photo.

    The product direction here is straightforward:

  • describe the image,
  • infer what the person is eating,
  • structure that result,
  • and let the user act immediately afterward.

    • For example:

  • create a recipe,
  • swap a meal in the plan,
  • or log that meal as consumed.

    • Here AI does not replace the product. It accelerates a real-life task that often breaks adherence.

    Practical utilities

    Beyond the stack, Saria is interesting because of the utilities it brings together in one system:

  • a weekly food planner,
  • a custom recipe manager,
  • a shopping list derived from the plan,
  • a daily habits and intake tracker,
  • nutrition onboarding support,
  • PDF generation to preserve continuity with traditional delivery formats,
  • a light social/group layer with ranking,
  • and a visual assistant for logging meals from images.

    • That puts it in a strong middle ground: it is not just a macro tracker, not just a recipe app, and not just a progress dashboard.

    What makes it powerful as a product

    What makes Saria stand out is not only that it digitizes a diet. What makes it powerful is that it connects several utilities that are usually fragmented, loosely connected, or missing altogether.

    Here, the user does not just receive information. They get a tool that helps them decide, shop, cook, log, and sustain the habit.

    That completely changes how the product feels.

    Clear use cases

    Saria supports several use cases that justify the jump from PDF to product:

  • 1.Individual users who want to stop improvising meals and follow a weekly plan that is easier to execute.
  • 2.Couples or households that share part of the shopping and planning process.
  • 3.Nutrition professionals or coaches who need something more dynamic than a static document.
  • 4.Users with low adherence who benefit from a daily view, fast logging, and a shopping list connected to the plan.
  • 5.Mobile-first scenarios where taking a photo and logging a meal matters more than filling long forms.

    • Why the project is interesting

    What makes Saria interesting is not only that it “manages menus.” It tackles a very common but poorly solved transition: moving from a manual PDF-based service to a digital product that still preserves real utility.

    That kind of transition forces you to think across several layers at once:

  • user experience,
  • day-to-day operations,
  • data structure,
  • personalization,
  • multi-user scalability,
  • and which parts are actually worth automating.

    • That is exactly the territory Saria is exploring.

    Current state and direction

    The project already has a broad functional base and, at the same time, a very explicit direction for the next iterations:

  • simplify weekly planning,
  • improve recipe creation,
  • turn the plan into a shopping list,
  • expand the multi-user layer,
  • and use AI pragmatically in everyday execution.

    • In other words, Saria is not trying to be “the super nutrition app that does everything.” It is trying to solve the path from having a menu to living it through a dynamic, editable, and genuinely useful system.

    _Saria turns a static nutrition plan into a living system: week planning, recipes, shopping, tracking, and real iteration._