I have to agree with all the things said here in the comments. In fact, as much as I love Bevel I find myself going back to MacroFactor over and over. They’ve just nailed this and it’s easily 3-4x faster. For me the primary issue is search speed and accuracy. For some reason, it doesn’t seem to match the brand name as well as the common name. Results don’t seem to take my historical choices into account. If I’ve eaten something before, or it’s one of my saved foods, it should definitely come to the top of the list before a random brand I’ve never heard of. Plus all the other features mentioned by others (swipe to duplicate, delete, edit time, group by meal, bulk edit, etc).

If it’s easier I’d be just as happy if you integrated with MacroFactor, but I’m guessing that’s less aligned with your product strategy.

As others have detailed, the number of steps to add a food is taxing to say the least and the searching takes an inordinate amount of time for each entry. While the UI is visually polished, the actual food logging workflow is currently too cumbersome for daily use. The high friction in adding items makes it difficult to maintain a consistent logging habit.

Critical Issues:

Search Latency: Search queries take 3-5 seconds to return results. The cumulative time spent logging a single meal is prohibitive and this is more cumbersome if the initial search result is incorrect for a given food item.

Data Integrity: I've seen examples where the data for a food item had zero values (e.g., Nancy's Low Fat Cottage Cheese), which necessitates manual correction.

Unit Support: Many food items only offer volume as an option. Since I weigh my food, the lack of mass-based options (grams/ounces) creates significant friction and requires manual conversion.

Logging Friction: The number of "taps" required to move through the entire flow of adding an individual item (from search to a confirmed entry) is significantly higher than industry competitors.

Retrospective Logging: Most people log food retrospectively, not in real time. The experience currently feels too fragmented and needs a more cohesive batch-entry flow.

Requested Improvements:

Efficiency Shortcuts: Implement "Slide to Delete" for individual entries, "Copy Previous Meal," and the ability to set "Recurring Meals" for daily staples to reduce repetitive data entry.

Meal Groupings: Group entries by Breakfast, Lunch, Dinner, and Snacks with macro summaries (Calories, Fat, Carbs, Protein) displayed for each meal.

Bulk Editing: Add multi-select capabilities to the timeline to allow for batch-changing meal times or categories.

Optimized Search: Aim for sub-second search results and improved keyword matching to reduce repeat searches.

Intuitive Display: Update the timeline to show calorie counts for each individual food item at a glance.

II havI have to agree. I have been using Noom for sometime now and in the past I have also used my fitness pal. This is by far the clunky nutrition I have ever worked with and likely won’t continue to use it.

Take a look at Loose it! They support EU food and bigger part of the nordic

This it the manual flow I use now to record eating a saved recipe (8 steps!)

Launch Bevel

Tap +

Tap Search Food

Tap My Foods

Tap Recipes

Tap the recipe I want

Tap Next

Tap Log

Using the Shortcuts app, I can collapse the first three steps into one but this is still cumbersome.

I'd love support in Shortcuts that allowed a single action to log the default portion of a preset recipe without any other taps. This would then allow even more cool integrations like reading an NFC tag to trigger logging.

Maybe a integration with Yazio

Agree! I think MacroFactor is the best when it comes to food logging. Super fast. Great interface, too. I love the food log timeline MacroFactor has. Would love to see similar designs in Bevel!

Note to the team: lots of these features are already available in the Lifesum app which would be a good rodelmodel to look at 🙏🏻

Agree. Or something like copy from yesterday for ease when meal prepping, making it easier to find previous/historical items

100% I agree in this. When you have other apps like lose it, or MYP that do this so easily, and bevel doesn’t read the nutrition information they put into apple health, that could also fix this issue.