u/Interesting_Lie_9231

I’m working on an iPhone app called MetricSync that lets you take a photo of your food and get an estimate for carbs, calories, protein, and fat.

The idea is to make low-carb tracking faster. Instead of manually searching every ingredient or building the whole meal from scratch, you can take a photo, get an estimate, and then edit anything that looks wrong.

I know photo estimates will never be perfect, especially with sauces, oils, homemade meals, and portion sizes. But I’m wondering if a fast editable estimate would still be useful as a starting point.

For people here who track carbs or macros:

Would you use photo-based carb estimates if you could edit them, or would you only trust manual logging?

I can share the app link if that is allowed here.

I built an iPhone app called MetricSync that lets you take a photo of your food and get an estimate for carbs, calories, protein, and fat.

The main thing I’m trying to make easier is meal logging. Instead of manually searching for every ingredient, you can take a photo, get an estimate, then edit it if anything looks off.

I know this may be useful for people who are trying to watch carbs, improve food awareness, or track meals more consistently after a prediabetes diagnosis.

This is not medical advice and it does not replace a doctor, dietitian, or any plan you already follow. The point is just faster food and carb logging.

I’m looking for feedback from people who already track carbs, meals, glucose, or A1C-related habits:

Would photo-based carb and macro tracking actually be useful to you, or would you not trust it enough to use it?

I can share the link if that is allowed here.

I made TokenBar, a small macOS menu bar app for people who use AI tools a lot while working.

The problem I kept noticing is that token usage and estimated spend are easy to ignore in the moment. You might be coding, debugging, generating text, testing prompts, or using an AI agent for a while, then only later realize the usage added up.

TokenBar keeps it simple. It sits in the menu bar and gives quick visibility into AI token usage and estimated spend while you work.

I wanted it to feel like a small utility, not a full dashboard or another productivity suite.

Main idea:

• quick AI usage visibility
• estimated spend while working
• lightweight menu bar app
• no subscription
• $5

I’m mainly looking for feedback on whether the value is clear and whether the landing page explains the problem well.

Link: tokenbar.site

I came across a small Mac menu bar app called TokenBar that tracks AI token usage and estimated spend while coding.

The idea is pretty simple. A lot of people are using AI coding tools all day, but the cost is usually invisible until later. You might be debugging, generating code, testing ideas, or running prompts for hours, then only check usage after the fact.

TokenBar basically puts that visibility in the menu bar.

It is not trying to be a huge analytics platform. It is more like a quick “am I spending more than I realize right now?” indicator for people who use AI tools heavily.

What stood out to me is that it is only $5, and apparently it has already grown to around $5k in value in about a month. Small utility apps still seem underrated when they solve a narrow problem clearly.

A few reasons I think it is interesting:

• AI usage costs are becoming harder to ignore
• developers do not want another dashboard to check
• menu bar apps are useful when the problem is constant
• one-time pricing feels better than another subscription
• tiny tools can still create real value if the timing is right

Curious what people think. Is AI spend tracking something you would actually want in your menu bar, or is this too niche?

Link: tokenbar.site