Saylog

Overview

Most calorie trackers ask you to search a food database, weigh your plate, and log every meal by hand. That friction is why people quit within a week. Saylog starts from a different premise: just say what you ate, and let the app do the rest.

Role: Designer and mobile engineer. Started: 2026, still actively building.

The Problem

Logging food is the boring part of eating well, and boring things get abandoned. Every calorie app I'd used made tracking feel like data entry, not something that fit into an actual meal.

The real value isn't the log itself, it's what you learn from it: which days you're actually hitting your protein target, what triggers a bad eating week, whether "eating healthy" is even true or just a feeling.

Approach

Saylog leans on voice as the primary input. Say "two eggs and toast for breakfast" and it's parsed, estimated, and logged in seconds, no search, no scale.

The dashboard is built around trends, not single entries: weekly macro averages, eating-pattern streaks, and a nutritional-gap report that flags what's consistently missing rather than judging any one day.

Tech Stack

Flutter Supabase Next.js Resend

The app itself is Flutter, for one codebase across iOS and Android. Supabase handles auth, data, and the parsing pipeline. The marketing site runs on Next.js, and weekly report emails go out through Resend.

What's Next

The core logging loop works. Next up is expanding the weekly health report and tightening the voice-parsing accuracy for less common foods and multi-item meals.