Hi, HN
I kept giving up on calorie tracking because trying in every meal was too much work. So I tried building something where I just take a photo and it estimates what’s on the plate. It’s honestly not perfect - it does well with simple meals and gets confused by messy or mixed plates, so you can always correct it. But for me it lowered the friction enough that I actually kept logging.
Under the hood it’s a vision model for the food recognition, wrapped in Kotlin Multiplatform (iOS and Android) with a small Ktor backed.
I’d love feedback - especially where the recognition fails for you, so I can see the real edge cases. Thanks for checking it out.
What do you do about portion size, and the calories a photo can't see like oil or dressing? Those are the parts that have always made me distrust the number these apps spit out. Curious how you're handling it. Only looked at the landing page so far.
Some other similar apps do the same thing but it's hard to provdie right and accruate inforation just based on photos by using LLM & OCR. any special design you did in this app?
the app looks same or similar to fitness apps. As myself I found the apps difficult in managing while doing exercises because you have to constantly do this in phone. I prefer not to .So build something where it would not require manual efforts or minimum manual effort.
Fair - I hate touching the phone between sets too. Right now the app keeps it minimal: photo for meals, quick-tap for workouts. But "zero effort while exercising" is the direction. What would work best for you - logging the whole workout once at the end, or voice/watch input mid-session? Asking because this decides what I build next.
11 comments
[ 6.0 ms ] story [ 40.8 ms ] threadUnder the hood it’s a vision model for the food recognition, wrapped in Kotlin Multiplatform (iOS and Android) with a small Ktor backed.
I’d love feedback - especially where the recognition fails for you, so I can see the real edge cases. Thanks for checking it out.