Currently, the nutrition log uses a flat structure where every food item is shown as a separate entry. This is useful for precise tracking, but it can make the timeline feel fragmented and makes it harder to see what was actually eaten as a meal.

I’m proposing "Contextual Meal Grouping": keeping individual food entries, but automatically grouping items that were logged within a similar time window into a single meal.

Individual food items would remain separate records with their exact timestamps, but entries consumed around the same time could be grouped into a single meal.

For example:

12:30 - Chicken - 300 kcal

12:35 - Rice - 350 kcal

12:40 - Broccoli - 80 kcal

Could be shown in the Timeline as:

Lunch - 730 kcal

The grouping could be based mainly on the time between entries, with an option to manually adjust, split, or merge a group when needed.

Each meal group could show an aggregated nutritional summary, such as:

This would make it easier to see the total nutritional value of a meal without having to manually add up several individual entries.

It could also provide more useful context when looking at meal timing and composition alongside other health or performance metrics.

Grouped meals could appear as a single collapsible block on the Timeline.

Users could:

This would make the Timeline cleaner without losing the detail of individual food logs.

Recipes already provide a way to combine multiple foods into one entry, but they don't always fit how people log their meals.

Not every meal is a predefined or repeatable recipe. For example, a user might simply log chicken, rice, vegetables, and a drink within a few minutes without wanting to create a recipe for that combination.

Meal Groups could therefore complement Recipes:

Recipes - predefined or frequently repeated combinations of foods

Meal Groups -> automatically grouped individual entries based on when they were consumed

This would let users keep logging food naturally while still having their entries grouped into meaningful meals.

Having a meal-level structure could also give Bevel Intelligence better context. Instead of having to infer that several individual entries were part of the same meal, it could work with an explicit meal group.

This could make it easier to generate insights around meal composition and timing in relation to other metrics, while still keeping the individual food data available.

Overall, the idea is to keep the current detailed food logging, but add a higher-level meal structure on top of it. This would make the nutrition timeline easier to understand and allow meals to be analyzed as a whole rather than only as individual food entries.