Log what you ate,not what was served.

Yes, bidirectionally. BiteDeck reads five metrics — steps, active energy, workouts, weight, body fat % — and writes ten: calories, protein, carbs, fat, fiber, sugar, sodium, water, weight, and body fat. Every single metric has its own toggle, on top of the iOS permission. Turn any one off without disconnecting everything.

Your logs live in SwiftData on your device. If you have iCloud device backup on at the iOS level, BiteDeck's data is included automatically — no separate cloud sync to a BiteDeck server. Export your full meal and weight history as CSV, or today's plan and intake as a one-page PDF, anytime.

You snap a photo. It goes through BiteDeck's own proxy to Google Gemini Vision for recognition, then the item list comes straight back to your phone. BiteDeck doesn't retain your images or train on them. If you'd rather not scan, every meal can be logged by search, barcode, nutrition-label OCR, or freeform entry.

BiteDeck requires a subscription — $69.99/year or $4.99/week. What stays the same either way: no ads, no account, and no analytics on what you eat.

Any iPhone on iOS 17 or later, in portrait. That includes iPhone Duo: since version 1.0.26 BiteDeck fits the closed outer display and keeps a phone-sized deck on the open inner display, held either way. No iPad layout, no watchOS app, no Android. The entire design leans on iOS-specific primitives (HealthKit, SwiftUI, SwiftData) — a port would be a different product.

Four ways: manual entry, the US Navy method (neck/waist/hip measurements with cm↔in toggle), the Deurenberg formula from BMI + age + sex, or imported from Apple Health. Every saved entry feeds both the Home Composition page and the Katch-McArdle BMR calculation that drives your calorie target.

A five-state forecast engine (locked / unlocked / goal-reached / maintaining / reversed) runs on your phone. It uses a 14-day lookback and a 7-day rolling average, adjusting for your actual deficit against maintenance TDEE. It never talks to a server — the whole thing is on-device math.

Yes. Fasts of 20 hours or longer protect their end-day as a logged day automatically — you can do a fast-only day and keep your streak. Milestones fire at 12, 16, 18, and 24 hours. Protocols: 16:8, 18:6, 20:4, OMAD, or custom 1–72 hours.

Type a brand name — "In-N-Out," "Chick-fil-A," "Chipotle" — and a dedicated menu card surfaces with every item sorted by section (burgers, shakes, fries, sides). Scoped search inside the menu, sort by section/name/calories, filter by section, multi-add. 281 chains in the database.

Because the whole design leans on iOS-specific primitives — HealthKit, SwiftUI, SwiftData, the on-device Gemini pipeline, Doto at fixed sizes, skeuomorphic modifiers that only exist in Apple frameworks. A port would be a different product. Not planned.