Short explanations of the principles and trade-offs built into Calk.
How Calk counts food#
Why you assemble a dish instead of photographing it#
Calk asks you to assemble a dish from its parts rather than photograph it. The first entry takes more input, but it makes the calculation explicit.
An image may not reveal how much oil went into a salad or whether a sauce contains sugar. A model has to infer those details, and the resulting estimate cannot show which hidden assumption was wrong.
With a meal template, you choose the base, protein, sauce and other parts. Calk calculates from those choices. Save a dish you repeat and its usual setup is ready next time.
The controls are deliberately practical rather than laboratory-precise. A template may ask about portion size, the relative amount of a filling, or whether an ingredient was present. Ingredients that can move the total substantially get more detailed choices. Others are kept simple so that a normal meal does not turn into a weighing exercise.
Templates also separate the structure of a meal from its name. Search may take you from the name of a particular dish to a broader soup, sandwich or bowl template. You then describe the version you actually ate. If no single template fits, you can assemble the main part in one and record an addition separately; the daily total still contains both.
This matters beyond the current meal. Reusing the same saved composition applies the same assumptions each time, which makes comparisons across days more consistent.
You can always inspect and change a saved setup. The heart stores your usual selections; it does not turn them into a recommendation. Today’s dish can still use a different sauce, portion or side without altering the favorite unless you save the new state.
The result is a diary whose numbers have a visible source. When a daily total looks surprising, Day analysis can trace a selected nutrient back to the ingredients that contributed it. That connection would be much weaker if the meal started as an image and its hidden details were inferred for you.
Why there is no giant food database and no barcode scanner#
Very large food databases usually combine manufacturer records with user submissions. That creates duplicates, regional variants and entries whose source or serving size is hard to verify.
Calk starts with a smaller, verified ingredient set. You assemble the dish and can see which choices produced its nutrition total.
A barcode identifies a packaged product, provided that the database has the right regional version and current label. It does not describe an assembled plate at home, in a canteen or in a café. Calk’s templates are built for those meals as well as packaged components.
The trade-off is real: finding one exact packaged product may take longer. A saved meal, however, opens with your usual composition and can be recorded consistently over time.
If your exact product is missing, choose the closest match by composition and use it consistently.
Why you do not need to weigh every gram#
Calk is designed to work without weighing every ingredient. Templates provide portion, size and amount controls for the choices that matter to the dish.
Any food record contains uncertainty. A scale reduces uncertainty about weight, while ingredient variation and cooking still affect composition. The question that matters is whether extra precision would actually change the result.
Templates therefore use more detailed controls for calorie-dense ingredients such as oil, sugar and nuts, and simpler choices where a small portion difference has less effect.
Composition matters alongside weight. Knowing which ingredients were present often adds more useful information than recording a highly precise total weight for an unspecified dish.
If estimating portions feels unfamiliar, use a scale occasionally to calibrate your eye. Save meals you repeat so that the same assumptions are applied consistently.
Why only the edible part counts#
Every food in Calk is described by its edible part. Cherry, plum and peach stones, the bone in a chicken wing or a T-bone steak, a banana peel — none of that is food, and none of it is in the numbers.
The portion buttons follow the same rule. “One egg” means the egg you ate, not the egg you weighed with the shell still on.
So if you ever check a portion against a scale, weigh what will actually be eaten. Shopping weight inflates the result, and the thicker the peel or the heavier the bone, the further off it goes.
Thin skin you eat stays: an apple with its skin is an apple. The rule is only about what you set aside — the stone, the bone, the shell, the thick peel.
Why an amount button sometimes leaves the total unchanged#
You tap “a lot”, but the calorie total does not move. This can happen when that option is the only selected item in its group.
Amount buttons describe a share within the group, not a weight in grams. If a wrap contains only one selected filling, that filling already takes the whole share. There is nothing else for the button to rebalance.
Select a second filling and the same buttons can change the result. “More meat” now means a larger share of meat relative to the vegetables.
Shares let the same template work across different serving sizes. The overall portion controls the size of the dish; amount buttons describe how its components divide that portion.
The same rule applies to any group with exactly one selected option.
Time and rhythm#
Why it helps to log before eating#
You can log a meal before or after eating, as long as the day is still open. Logging it first has one extra benefit: the totals can still inform the meal in front of you.
You can see how much of each target or limit remains and adjust the composition or portion if you want to. You get the numbers while you can still act on them.
Logging afterwards still creates a valid record, but then you are recording a decision you have already made.
Recording the meal while it is in front of you can also make its ingredients and portions easier to remember accurately.
Use whichever timing fits the situation. Before eating gives Calk a chance to help with the current decision; afterwards still preserves the day for later analysis.
Why conclusions come by the week, not by the day#
One day can be shaped by travel, a celebration, unusual activity or a noisy scale reading. It may be accurately recorded and still be unrepresentative of your routine.
Calk uses daily numbers to help with today’s choices. Broader conclusions rely on repeated days, because a pattern becomes easier to distinguish from an isolated event.
One large meal or one carefully planned day remains part of the record, but neither is enough on its own to establish a trend.
Use the weekly and longer-term views when you want to understand direction. The expenditure estimate likewise depends on a weight trend and recorded intake over time, not on one day.
Why the day ends at midnight and past days cannot be edited#
Calk uses local calendar days. At midnight, a new day begins, so food recorded afterwards belongs to the new date. Keeping that boundary fixed makes daily and weekly comparisons consistent.
Past days are read-only. You can review them, but you cannot add yesterday’s lunch today.
Memory becomes less reliable with time: it is easy to reconstruct ingredients, portions and timing with more confidence than accuracy.
Back-dated entries would also quietly change what the weekly views were built on. Daily totals, weekly windows and patterns in meal timing all depend on entries staying attached to the time they were recorded.
A gap is honest: it shows up as missing data. An estimated entry looks precise even when its composition and time are uncertain.
Log before eating or soon afterwards. If you miss a day, resume with the next meal rather than trying to rebuild the past.
A missed day and two silent weeks are different things#
Missing an occasional day does not invalidate the diary. Smoothing can handle gaps, and weekly views use the days that contain data.
After a longer break, your routine, activity or weight may have changed. Extending the old trend across that period would assume that the earlier conditions still apply.
Calk therefore closes the earlier run, widens its uncertainty and begins measuring the current trend from fresh entries.
Your earlier history remains available. The reset applies to the conclusions that require current, continuous evidence, not to the records themselves.
Screens and what they show#
Why templates are not in alphabetical order#
The template list is ordered by expected use rather than alphabetically.
The same dish begins with different letters across Calk’s languages. An alphabetical list would give each language a different order without making frequently used templates easier to reach.
The default order puts commonly used templates near the top. Before Calk knows your habits, that is a better starting point than spelling.
Once you place your own templates on tabs, their personal order matters more than the catalog’s default order. You can arrange those tabs around the meals you use most.
Why the home screen does not show everything#
Calk’s home screen is designed for the things you need several times a day: logging food, checking today’s targets and limits, and seeing the latest weight and status.
It also links to the places that explain today’s numbers: detailed analysis, your goal and the report. Those sections provide a quick signal on the home screen and leave their full detail to the next screen.
This keeps the frequent action — adding a meal — easy to reach without turning the home screen into a complete archive.
Meal photos are absent for the same reason. Calk records the composition you selected and keeps the home screen focused on information that affects the calculation.
Why water has three numbers#
Calk records water from two sources, which produces three related numbers on the screen.
Drinks covers poured beverages such as water, tea, coffee and juice.
Water from food includes moisture in ingredients and water incorporated into a dish during cooking. It contributes to the total Water value without appearing on the Drinks line.
The three numbers are:
- the target — the reference range for total water intake;
- Drinks — how much you drank;
- Water — total intake, food plus drinks.
Compare the target with Water, not with Drinks alone. This keeps the same reference whether most of the recorded water came from beverages or food.
There is no separate plain-water total. Water in tea or coffee still contributes to total water; caffeine, sugar and calories are recorded in their own nutrients where applicable.
Only recorded food and drinks contribute to these figures. They describe the diary and are not an assessment of your hydration.
Why variety is counted in cells, not in products#
The variety count can move less than the number of individual foods you logged.
Calk counts cells: groups of foods that are closely related in its variety taxonomy. Several beef dishes, for example, can map to the same beef cell even when they have different names or preparation.
A food from an unfilled cell expands the count; another item from a cell already represented does not. The metric therefore measures breadth across the taxonomy rather than the number of entries.
Calories and macronutrients describe quantities. The variety view adds a different signal: how widely your recorded foods are spread across the catalog’s nutritional groups.
To broaden the map, add a food from a group that is not already represented rather than another variation of the same group.
Why the report needs a month of data#
The 30-day report unlocks only after the diary contains enough food and weight data to support it.
Its conclusions cover sustained patterns: expenditure, weight direction, repeated foods and the range of what you eat. A handful of days may describe an unusual week rather than your routine.
Readiness is therefore counted in data, not elapsed time: at least 20 qualifying food days and 10 days with weight entries inside the window. You may meet the threshold before 30 calendar days, while 30 days with sparse records will not unlock the report.
Once it is ready, you choose when to open it. The window rolls over the latest 30 days and is recalculated whenever the report opens.
The threshold reduces the influence of a few unusual days. It cannot make every conclusion certain, but it gives the report enough coverage to describe a pattern rather than an isolated event.
Your data#
Why the food diary works offline#
The food catalog is bundled with the app. Searching, assembling a dish and calculating its nutrition all work offline.
That matters because meals are often recorded away from reliable Wi-Fi or mobile coverage. The core diary remains available in those situations.
Your food logs, weights, targets and reports stay on the device and are not uploaded. Calk does transmit limited pseudonymous usage analytics, crash diagnostics and the data required to manage your account and subscription, as described in the privacy policy.
Keeping the food catalog local also means a search query does not need to be sent to an online food database before you can log a meal.
Your target and how it is found#
Why the target is a range, not a single number#
Calk shows a target range rather than one exact calorie number.
Energy expenditure varies from day to day with movement, routine and other ordinary factors. It is also estimated with uncertainty, especially while your personal history is short. A range can show both realities without pretending that the midpoint is exact.
A range also avoids turning a small difference from one number into a pass or fail. The useful signal is whether the day sits within, near or beyond the range.
Targets and limits have different meanings. Protein is something to aim for; added sugar and salt are quantities to stay within. The labels and indicators reflect that distinction.
Why the target changes on its own#
The first target comes from a formula: sex, age, height, weight, usual activity. A formula describes an average person with those numbers — a useful place to start, not a portrait of your body.
After that Calk compares two of your own series: how much energy you logged and how your weight moved over the same period. With a complete log, steady weight anchors the estimated maintenance calories at the recorded intake. If the trend moves down on similar intake, the estimate moves up; if it moves up, the estimate moves down.
A single day cannot show this. Weight swings with water, salt and the hour you step on the scales, and one day of food says nothing about a week. So Calk compares a smoothed weight trend with a set of days that have complete food logs, not just yesterday’s two numbers. More data narrows the uncertainty in the estimate.
That is why the number can change on a day when you changed nothing in Settings: a few more logged days or another weigh-in gave the estimate new evidence.
After a long break, Calk stops treating an estimate from months ago as current. It gathers fresh food and weight data before relying on that estimate again.
A day with recorded intake below half the formula-based expenditure estimate is excluded from this calculation. Under-logging that stays above this cutoff biases the adaptive estimate downward. In either case, incomplete records make the estimate less reliable; they do not change actual energy expenditure.
What a yellow number means#
A number turns yellow when the percentage on screen passes 100: 100.0% is still green; 100.1% is yellow. That is all the color says: this value is above its target.
Going over a target is not a grade. Calk does not know whether the value came from a celebration, a long walk, a late dinner or an ordinary day. Yellow only makes the over-target value easy to spot.
The color does not tell you what to do. If the value repeats or surprises you, open the composition to see which foods contributed most and decide from there.
Values whose target is a minimum — fiber, for one — never turn yellow: passing a floor is not going over anything.
In the limits block the warm color is simply that group’s color: those are the values best kept low, and their bars are drawn that way from the start, not because something was exceeded.
Why some answers take a few weeks#
In the first days, some figures are missing and others come with a wide range. They are waiting for evidence, not still loading.
Calk does have a starting point: a height-and-weight formula provides a theoretical expenditure estimate from day one. If you import eligible Health data, that can improve the starting estimate. Either way, the uncertainty is deliberately wide until your food and weight history can support a personal estimate.
Daily targets are available immediately. Weekly views follow from the days you record. A personal expenditure estimate and forecasts take longer because they depend on how your weight responds over time.
The formula is useful as a starting estimate, but it describes a typical person with similar characteristics. Calk labels the early estimate cautiously and replaces it with your own evidence as that evidence becomes strong enough.
In the meantime, keep logging and weigh regularly. The uncertainty narrows as ordinary days accumulate; opening the app more often will not speed it up.
Why you are asked to weigh more often than seems necessary#
Scale weight can move substantially from one reading to the next. Hydration, salt and carbohydrate intake, the menstrual cycle, time of day and digestion can all affect a single measurement. The app cannot tell from one reading which of those factors was responsible.
With only one reading a week, any one of those fluctuations has a large influence. More frequent readings give the app enough points to smooth the series and estimate its direction.
Weigh regularly under reasonably similar conditions and avoid drawing a conclusion from one number. Look at the trend over several weeks instead.
Missing an occasional day does not break the series. After a long pause, Calk becomes more cautious because the earlier trend may no longer describe your current routine.
How Calk talks to you#
Why advice is limited and rarely repeated#
Calk could comment on every day, but frequent prompts quickly become background noise.
Instead, advice appears when the entries show a repeated pattern worth acting on. A single unusual day is not enough.
Each message names the pattern and suggests a specific action without grading you. It also stays out of the way until the underlying situation changes, rather than repeating the same message.
No advice may simply mean that Calk has not found a sufficiently stable or useful pattern in the available data.
Why positive feedback stays factual#
A food diary that reports only shortfalls and limits gives a one-sided account.
Calk also names positive patterns. The wording stays factual: “Vegetables on four of the last seven days” describes the diary. “Well done” judges the person, so Calk avoids it.
A fact can show what changed without deciding whether you were good or bad. That is also why Calk shows where a number sits instead of assigning it a grade.
Positive feedback appears only when the data supports something specific. A day without a message is not a bad grade; there is simply nothing new to point out.
Why the app sends almost no notifications#
Calk does not send meal reminders, streak prompts or generic encouragement.
Notifications are kept for two concrete events: a report that is ready to read and, if you enable trend monitoring, a meaningful change in your weight trend. Both lead to something you can inspect in the app.
There are no “you haven’t opened the app” messages or scheduled congratulations. Opening Calk should follow your routine, not a retention schedule.
Trend monitoring is optional in Settings. Report reminders are offered when the report becomes available, if notifications are allowed on your device.
What Calk does not do#
Why there is no ready-made meal plan#
Calk does not provide a ready-made meal plan.
A useful plan would need detailed knowledge of your preferences, cooking skills, available food, allergies and schedule. Calk does not collect enough of that context to prescribe a realistic menu.
Calk starts with the food you actually eat. It shows the resulting targets, limits and repeated patterns, then offers specific suggestions where the data supports them.
Those suggestions all work on the meals you already eat:
- add — vegetables to a familiar dish, beans to the soup, protein at breakfast;
- replace — the sauce, the cooking method or the proportion of parts;
- keep — meals that already work need no change.
The idea behind it is simple: fewer calories per gram, more protein and fiber. A dish like that keeps you full longer for the same calories, and repeating it is easier than holding a temporary rule. Change what the dish is made of rather than adding on top of it: an addition brings its own calories.
A suggestion is grounded in your own entries and remains optional. It can help you adjust an existing meal without replacing your routine with somebody else’s menu.
Why there is no friend feed and no competition#
Calk has no friend feed, leaderboards or challenges.
Other people’s targets are poor reference points. Energy expenditure and routines differ even among people with similar height and weight, and a public number rarely carries that context.
A public diary can also change what gets recorded. If entries are chosen for an audience, the record may stop reflecting ordinary eating and become less useful for personal analysis.
Calk compares your own periods instead: this week with an earlier week, or the current report with your own history. Both sides then come from the same person and method.
You can still share a single dish card when you choose. That does not expose the diary behind it.
Why there are so few settings#
Calk has fewer settings than most apps in this category. You can change the things that affect how it works for you: language and theme, measurement and portion units, nutrient display, button size, haptics, analytics and trend notifications.
What you cannot change are the rules behind the diary: when a calendar day ends, how a weekly view is built, or which measurements feed a calculation. Those rules need to stay the same from one week to the next. Otherwise a chart can move because a hidden setting changed rather than because your food or weight changed.
The dividing line is simple: preferences change the way you use or view the app. Calculation rules change what the result means. Calk exposes the first and keeps the second consistent.
Your goal is adjustable too, but it lives with your profile rather than among display preferences. Changing it updates future targets without rewriting past days.
Why Calk does not use AI to calculate your food#
Calk does not ask a model to guess a meal or recalculate it from a description. The nutrition total comes from the ingredients and proportions you select.
That approach is fast. The result updates as soon as you tap a button, including when the device is offline.
It is also inspectable. You can open the dish and see which selections produced the total instead of having to trust a plausible-looking estimate.
Most importantly, it is repeatable. The same saved composition gives the same result. That consistency matters when Calk compares one week with another.
AI can run on a device, and models can be made more deterministic. Neither changes the product requirement: a diary calculation must be traceable to the food recorded. Calk therefore uses explicit composition for the number rather than a model’s guess.
Why Calk gives no medical advice#
Calk does one thing: it builds a dish from its parts and tells you honestly what is in it. That is a calculation about food, not a conclusion about your health.
The targets here are a reference point, not a prescription. They come from general formulas over height, weight, age and activity, and they describe a notional healthy adult. The app cannot see your blood work, your diagnosis or the medication you take.
This is why Calk is careful with its words. It does not say “you are iron deficient”. It says the food you logged carries few sources of iron. The difference matters: the first is a statement about a person, and only someone with test results and an examination may make it. The second is a statement about a list of foods, and that is the part the app genuinely knows.
If there is a medical condition, a pregnancy, a prescribed diet or a history of disordered eating, the numbers are set by a professional. The app has neither the knowledge of your case nor the standing to apply it.
The most useful thing Calk can do for a conversation with a clinician is bring data to it. Thirty days of recorded meals describe your eating better than a recollection of it does.