Case Study

Hara: A Calm Food and Gut Health Diary Built Around a Real Personal Need

A personal gut health diary app built to track meals, symptoms and daily context in one private place. Hara was created as a simple working MVP to help notice patterns in eating, record useful information and support future conversations with a healthcare professional.

8 June 2026

Hara: A Calm Food and Gut Health Diary Built Around a Real Personal Need

Notice what your body has been saying

Hara is a simple personal food and gut health diary, designed to help track what you eat, how you feel and what may be affecting your body over time.

The idea came from a practical need. I was having ongoing gut issues and wanted a straightforward way to record meals, symptoms and the smaller daily factors that might affect how I felt. Bloating, pain, irritation, stress, sleep, medication, mood and notes all felt relevant, but I did not want to use an app that added too much complexity or made me question where the data was going.

So I built my own.

Hara began as a private tool for personal use. It was never intended to be a medical product to diagnose conditions, and it does not replace advice from a GP or healthcare professional. Its role is much simpler. It helps create a clear record of food, symptoms and context, so patterns may become easier to notice later.

If I speak to a healthcare professional I can take a useful diary of what I ate, when I ate it and how I felt afterwards.

Why Hara?

The name Hara comes from the Japanese word 腹 / はら / hara, which can mean abdomen, belly or stomach.

That made it feel like a natural fit over other AI generated app names! The app is about the gut, but it is also about paying attention to the body in a calmer, more reflective way. It is not about over-tracking or turning health into another dashboard. It is about noticing what your body has been saying.

The problem

Food and symptom tracking can quickly become too complicated.

Many apps try to cover everything. Calories, macros, exercise plans, goals, recipes, weight loss, coaching, reminders, reports and community features can all be useful in the right context, but they can also get in the way when the need is simple.

I wanted to answer a more specific question: What have I eaten, how did I feel and are there any patterns I should pay attention to?

That question helped shaped the beta product which focuses on low-friction recording. It should be quick enough to use after breakfast, lunch, dinner or tea, without feeling like another admin task.

What Hara tracks

Hara is designed around the small pieces of information that may help build a clearer picture over time.

It can record:

  • Meals
  • Symptoms
  • Bloating, pain or irritation
  • Mood
  • Sleep
  • Stress
  • Medication or supplements
  • Notes

The aim is not to make every entry perfect, but to make tracking easy enough that I actually do it.

The product approach

Hara was built as a rapid MVP using Lovable, TanStack and Supabase.

It sits on a Made Grand subdomain and uses verified, authenticated login. The first version is private and personal, with no expectation of wider users at this stage.

The product is intentionally simple. There is no complex dashboard or timeline in the first version, because the early goal is to capture useful information quickly and review it later.

The app may grow as I use it, but that’s part of the point of building my own apps. It can grow with new features as and when I think they could be useful.

Rather than inventing a large product based on other apps or theory, Hara starts with one real need and lets the product direction emerge from actual behaviour.

The UX challenge

The main UX challenge was not technical, it was behavioural. If a food diary takes too long to complete, people stop using it. If it asks too many questions, it becomes irritating. If it feels clinical, it creates the wrong mood.

Hara needed to feel calm, light and useful, so the interaction needed to support quick logging, especially around meals.

Breakfast, lunch, dinner and tea are natural points for recording food, but symptoms do not always appear immediately, and that created an important product question.

  • Should symptoms be logged separately later in the day?
  • Should a meal entry be editable afterwards?
  • Should the user be able to link a later symptom back to a previous meal?

Those are still open design questions, but hey matter because gut symptoms can appear hours after eating, so the app needs to support delayed reflection without making the tracking process complicated.

Future AI features

Hara may later become a public product which could include AI-assisted pattern analysis, helping review food and symptom entries over time. It could highlight possible links, suggest what may be worth paying attention to and help the user reflect on their habits more clearly.

One possible long-term idea is that Hara could become closer to a personal food diary assistant or nutrition companion.

That positioning still needs some further thought. Hara should not claim to diagnose problems or give medical advice. A safer and more useful role is to support awareness, reflection and better decision-making.

The AI feature should help people ask better questions. It should not pretend to have all the answers.

What Hara does not claim

  • Hara is not a medical app.
  • It does not diagnose conditions.
  • It does not recommend treatment.
  • It does not replace a GP, nutritionist, dietitian or healthcare professional.

It is a personal diary that may help people record useful context, notice possible patterns and have better-informed conversations about their health.

The value of Hara is in making personal information easier to collect, organise and reflect on, to support healthcare conversations, not replace them.

What this shows about Made Grand

Hara is also a useful Made Grand project proof point.

It shows how a simple issue can become a focused working product quickly. Instead of searching for an app that does too much, stores sensitive data elsewhere or forces the user into someone else’s workflow, Hara takes a direct route.

  1. Define the problem.
  2. Build the smallest useful version.
  3. Use it in real life.
  4. Improve it from there.

That is the value of rapid MVP development when it is guided by clear thinking. AI-assisted build tools can speed up production, but the useful work still comes from understanding the problem, shaping the experience and deciding what not to include.

Hara is not impressive because it is technically complex. It is useful because it is focused.

If you're planning an MVP or early-stage product and want to make sure the foundations are right before you build, we're happy to talk it through.

Start a conversation