<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Feature Requests — Welcome To The Cronometer Community</title>
        <link>https://forums.cronometer.com/</link>
        <pubDate>Tue, 21 Jul 2026 04:49:14 +0000</pubDate>
        <language>en</language>
            <description>Feature Requests — Welcome To The Cronometer Community</description>
    <atom:link href="https://forums.cronometer.com/categories/feature-requests/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Scatter Plot Option</title>
        <link>https://forums.cronometer.com/discussion/7145/scatter-plot-option</link>
        <pubDate>Mon, 20 Jul 2026 11:25:32 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>ChrisKay</dc:creator>
        <guid isPermaLink="false">7145@/discussions</guid>
        <description><![CDATA[<p>Can we add the usage of scatter plots with or without lines? I would much rather a scatter plot with a trend line than auto connecting data points. </p><p>My example, I only use the days I complete for my calorie plots. If I take a week or two off for vacation, and I plot only completed days, it just shows a line connecting my 2 nearest completed days around that timeframe, which imo, just makes the data messy. </p><p>I know this can be done by exporting to excel, but it would be nice to have as a native feature.  </p><span data-embedjson="{&quot;url&quot;:&quot;https:\/\/us.v-cdn.net\/6030245\/uploads\/DX7JAXXJSZVA\/1000013027.png&quot;,&quot;name&quot;:&quot;1000013027.png&quot;,&quot;type&quot;:&quot;image\/png&quot;,&quot;size&quot;:168466,&quot;width&quot;:1080,&quot;height&quot;:1100,&quot;displaySize&quot;:&quot;large&quot;,&quot;float&quot;:&quot;none&quot;,&quot;downloadUrl&quot;:&quot;https:\/\/forums.cronometer.com\/api\/v2\/media\/download-by-url?url=https%3A%2F%2Fus.v-cdn.net%2F6030245%2Fuploads%2FDX7JAXXJSZVA%2F1000013027.png&quot;,&quot;active&quot;:true,&quot;mediaID&quot;:2904,&quot;dateInserted&quot;:&quot;2026-07-20T11:24:25+00:00&quot;,&quot;insertUserID&quot;:4767,&quot;foreignType&quot;:&quot;embed&quot;,&quot;foreignID&quot;:&quot;4767&quot;,&quot;embedType&quot;:&quot;image&quot;,&quot;embedStyle&quot;:&quot;rich_embed_card&quot;}">
    <span>
        <a href="https://forums.cronometer.com/home/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fus.v-cdn.net%2F6030245%2Fuploads%2FDX7JAXXJSZVA%2F1000013027.png" rel="nofollow noopener ugc" target="_blank">
            <img src="https://us.v-cdn.net/6030245/uploads/DX7JAXXJSZVA/1000013027.png" alt="1000013027.png" height="1100" width="1080" data-display-size="large" data-float="none" data-type="image/png" data-embed-type="image" srcset="https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=300, width=300/6030245/uploads/DX7JAXXJSZVA/1000013027.png 300w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=600, width=600/6030245/uploads/DX7JAXXJSZVA/1000013027.png 600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=800, width=800/6030245/uploads/DX7JAXXJSZVA/1000013027.png 800w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1200, width=1200/6030245/uploads/DX7JAXXJSZVA/1000013027.png 1200w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1600, width=1600/6030245/uploads/DX7JAXXJSZVA/1000013027.png 1600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=2000, width=2000/6030245/uploads/DX7JAXXJSZVA/1000013027.png 2000w, https://us.v-cdn.net/6030245/uploads/DX7JAXXJSZVA/1000013027.png" sizes="100vw" /></a>
    </span>
</span>
]]>
        </description>
    </item>
    <item>
        <title>Adding Ketone &amp; Glucose Readings - entering time of day possible</title>
        <link>https://forums.cronometer.com/discussion/947/adding-ketone-glucose-readings-entering-time-of-day-possible</link>
        <pubDate>Tue, 22 May 2018 12:40:32 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>PJB</dc:creator>
        <guid isPermaLink="false">947@/discussions</guid>
        <description><![CDATA[<p>I'm now taking several Glucose readings durning the day.  It's very easy to record these Biomarkers in CronOmeter but I don't see the time of day I recorded them.  Time of entry would be very helpful for multiple entries on the same day.</p>
]]>
        </description>
    </item>
    <item>
        <title>Dark Mode for web</title>
        <link>https://forums.cronometer.com/discussion/7130/dark-mode-for-web</link>
        <pubDate>Thu, 16 Jul 2026 12:52:37 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>ChuckClaunch</dc:creator>
        <guid isPermaLink="false">7130@/discussions</guid>
        <description><![CDATA[<p>Hi, long time gold user- this is one of the few remaining web based applications that still blinds me with white each time I use it  <img src="https://forums.cronometer.com/resources/emoji/lol.png" title=":D" alt=":D" height="20" /> .  Seems like a super simple ask, could this be bumped up on the priority list?</p>
]]>
        </description>
    </item>
    <item>
        <title>Quick Add Nutrients</title>
        <link>https://forums.cronometer.com/discussion/6149/quick-add-nutrients</link>
        <pubDate>Sat, 03 Feb 2024 23:28:19 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>logicalparadox</dc:creator>
        <guid isPermaLink="false">6149@/discussions</guid>
        <description><![CDATA[<p>This is a real must-have feature. A lot of times, I find myself staring at a nutrition label or nutrition info, with no barcode. Whether it’s in a restaurant, or in a cookbook, or in a recipe/meal planning app. I don’t want to create a custom food… that’s too tedious; I might not have time in the moment. And maybe these will be one-offs that I won’t use again.</p>

<p>Why not have an option to just QUICK ADD a food. I select the option and its opens up a form for me to punch in the info. This would have a “title” field that by default could be “Quick Add” or something. I could edit that, if I want, to give it a name that I remember what it is, but if not there’s no required fields missing.  If all I want is to quickly add calories or macros, I can just add those and be done with it. Like a couple taps and a single screen just to record calories or carbs or something.  At least it’s better than a note telling myself to add it as a full blown later (spoiler alert: I probably won’t do that).</p>

<p>The form for quick adding nutrients could also leverage the same tool you guys already have for adding custom foods, so I could just snap a photo of the nutrition label and BAM - data is tracked. Maybe put that botton as a major option under ADD, right next to scan barcode. Or else have both the barcode and label scanners separate under a SCAN option. Currently, users can’t access the label scanner import feature at all. Only from scanning a barcode that isn’t recognized. Why??? Why isn’t this option available when making a custom food? That way I can quickly add any recipe or food that gives me a nutrition label (but doesn’t have a barcode). Rather than manually inputting all of that stuff. Imagine hitting ADD, then SCAN, then LABEL, and there’s all the nutrition and serving size data. You then have the option to quick add (just dump the info into your diary and skip having to name it, save it, go through several screens) or to save the info as a custom food if it’s something you’re going to potentially use again.</p>

<p>This would be a life saver… because most of the time, I’m not eating things with barcodes. But I’m also not just eating whole foods out of hand that are easy to add. Sure, if I’m having an avocado, that’s easy to track. Tap, tap, done. But… not when I sit down for dinner and am looking at a bowl of some curry I made. That’s 75% of my eating - things I made or were made for me that are difficult to track. Adding recipes for everything I make is SO time consuming. And it’s next to impossible when my partner does the cooking/meal prep. I tried asking my partner to create recipes in Cronometer for everything she makes… that didn’t work out well. I can get her to share a link to whatever recipe she used, but using the recipe importer and/or manually importing everything is a huge chore. It’s not practical or sustainable. So, I often give up and backslide into blind eating. It’s not like I’m eating the same meals over and over again. We often make recipes once and move on.</p>

<p>But… A surprising amount of the time, the recipes have nutrition info listed. Instead of creating a custom recipe and worry about every single ingredient, it would be nice to have an option of just snapping a pic of the nutrition info/label or if all else fails just punch in at least the macros. That would be a game changer. If I could just snap a photo of the info to create the food (if I’m going to use it more than once) or snap a photo to just import those details into a single entry without “Next”ing my way through multiple screens, it would be so much easier. It would take away any excuse for not recording something (or worse yet having to feel like “do I even want to eat this, because then I’ll have to add it into Chronometer later”.</p>

<p>This seems like you guys have all the stuff to make this happen. Just allow a quick add feature to manually add nutrients for a one-time situation and add an option to import the details by photo when/if a label is available. Then simply add an option to do the same when importing custom foods, rather than only having this feature hidden behind the scan a barcode option.</p>
]]>
        </description>
    </item>
    <item>
        <title>Progress against goals view in Android Widget</title>
        <link>https://forums.cronometer.com/discussion/7111/progress-against-goals-view-in-android-widget</link>
        <pubDate>Thu, 09 Jul 2026 15:08:12 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>EX4Paul</dc:creator>
        <guid isPermaLink="false">7111@/discussions</guid>
        <description><![CDATA[<p>Rather than just kcals consumed or remaining, can we see how we are progressing against specific goals.</p>

<p>e.g. my target for protein is 140g per day. That doesn't map to kcals in any meaningful way. Can the chart at the top of the 'Diary' tab page be shown as a widget so I don't have to open the app and go hunting?</p>

<p>Perhaps a single view of progress against a single macro target for folk that are focused on one thing?</p>
]]>
        </description>
    </item>
    <item>
        <title>Option to hide progress circles while keeping text numbers visible in long scrollable list on diary</title>
        <link>https://forums.cronometer.com/discussion/7096/option-to-hide-progress-circles-while-keeping-text-numbers-visible-in-long-scrollable-list-on-diary</link>
        <pubDate>Fri, 26 Jun 2026 22:48:17 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>featurefeedback</dc:creator>
        <guid isPermaLink="false">7096@/discussions</guid>
        <description><![CDATA[<p>A recent update has changed the appearance of the N/T items on the diary page for desktop. Please note this makes for a very BAD user experience. Previously, users complained that they couldn't tell the difference between a nutrient they hadn't eaten yet and a nutrient that simply didn't have a target. The developers added the dots to act as a visual separator:</p>

<ul><li>Light grey dots mean 0mg/0g has been logged.</li>
<li>Dark grey dots change to show you have logged an amount, but the app has no target to compare it against.</li>
</ul><p>While intended to provide clarity, the execution resulted in a busy, high-contrast grid that distracts from your primary macronutrients. Now the most highlighted items on the Diary page are the nutrients that you DO NOT WANT to track. I just want to see the numeric amount of these N/T items in my diet for items like soluble fiber, DHA, EPA, saturated fat, and other items with no RDA. But now these are highlighted with large dark gray circles making it very difficult to quickly view the other items I am tracking.</p>

<p>Can we get this changed back to the previous less obtrusive look or at least provide an option to turn off the annoying large dark gray circles that mean nothing.</p>

<p>Anyone else with similar issues with this new visual?</p>

<p>A VERY BAD USER EXPERIENCE.</p>
]]>
        </description>
    </item>
    <item>
        <title>Polyphenols</title>
        <link>https://forums.cronometer.com/discussion/6387/polyphenols</link>
        <pubDate>Sun, 21 Jul 2024 14:50:25 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>CD333</dc:creator>
        <guid isPermaLink="false">6387@/discussions</guid>
        <description><![CDATA[<p>Very keen to have polyphenols included in the data, with current knowledge increasingly showing us how vital it is to get a good range in daily.</p>
]]>
        </description>
    </item>
    <item>
        <title>Upload a recipe from a picture</title>
        <link>https://forums.cronometer.com/discussion/7101/upload-a-recipe-from-a-picture</link>
        <pubDate>Tue, 30 Jun 2026 23:48:19 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>KeepCalmAndCarrieOn</dc:creator>
        <guid isPermaLink="false">7101@/discussions</guid>
        <description><![CDATA[<p>Would it be possible to add a way to upload a recipe from an image?  Sometimes I have something that is in PDF or other format, and it would be nice if I could create a recipe in the app by uploading a picture of a recipe. Thanks</p>]]>
        </description>
    </item>
    <item>
        <title>Should we have the option to revert back to the old color scheme?</title>
        <link>https://forums.cronometer.com/discussion/7090/should-we-have-the-option-to-revert-back-to-the-old-color-scheme</link>
        <pubDate>Wed, 24 Jun 2026 20:31:56 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>crossm19</dc:creator>
        <guid isPermaLink="false">7090@/discussions</guid>
        <description><![CDATA[<p>The new color scheme is fine but also has some drawbacks. There is plenty of discussion taking place on the Reddit thread, so I won't list those hear. I am just curious to gauge if other people would also like the option to revert back to the old colors.</p>
]]>
        </description>
    </item>
    <item>
        <title>Macro targets as min/max ranges</title>
        <link>https://forums.cronometer.com/discussion/7099/macro-targets-as-min-max-ranges</link>
        <pubDate>Tue, 30 Jun 2026 09:38:01 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>burperinred</dc:creator>
        <guid isPermaLink="false">7099@/discussions</guid>
        <description><![CDATA[<p><strong>Feature request: Macro targets as min/max ranges</strong></p>

<p>It would be useful if macro targets could optionally be set as minimums, maximums, or ranges, rather than only fixed targets.</p>

<p>Right now, if I set a fixed target for carbs, protein or fat, the app shows how close I am to that exact number. That’s useful in some cases, but often I don’t actually care about hitting an exact value.</p>

<p>Examples:</p>

<ul><li>For carbs, I may only care about staying below a maximum, especially for glucose control.</li>
<li>For protein, I usually care about reaching a minimum for diet/training, rather than hitting one exact number.</li>
<li>For fat, a range makes more sense: enough for physiological needs, but not so much that it pushes calories too high.</li>
</ul><p>So instead of only “target: 140 g”, it would be great to have options like:</p>

<ul><li>minimum: at least 140 g</li>
<li>maximum: no more than 150 g</li>
<li>range: 60-90 g</li>
<li>fixed target, as it works now</li>
</ul><p>The diary could then show whether I’m below, within, or above the target range, rather than treating everything as a fixed number to hit exactly.</p>
]]>
        </description>
    </item>
    <item>
        <title>Adaptive TDEE calculation, Why don&#39;t we have it?</title>
        <link>https://forums.cronometer.com/discussion/5468/adaptive-tdee-calculation-why-dont-we-have-it</link>
        <pubDate>Sun, 27 Nov 2022 19:22:34 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>snatale42</dc:creator>
        <guid isPermaLink="false">5468@/discussions</guid>
        <description><![CDATA[<p>I've seen this asked on 2 other posts going back a while with no official answer, what's the deal? Seems like a no brainer to me.</p>

<p>We can have all the fancy integrations with fitness trackers and scales that make assumptions and then add or subtract numbers, but when our macros themselves are a guess, and the calories burned is also a guess, what's the point?</p>

<p>More and more competition has this now, MacroFactor is doing it very successfully, Carbon does it, MM+ has done it for a while, and it's a priceless feature. So much goes into the in/out equation and the gray area is huge, but since most people's goals are either to gain, lose, or maintain, the scale doesn't lie.</p>

<p>I still feel Cronometer is the most feature rich by a lot, but missing that one is a crime. I won't lie, I've been cheating with MF, having the ability to set a weight gain/loss goal and just track and having it auto adjust to keep me on track in real time can no longer be lived without. I workout more and raise TDEE, I get more cals, or maybe an adjustment to the macros otherwise, I start slacking off like around the holidays now, it'll back be off if the scale is showing i'm regressing, it just keeps going and it's almost impossible to screw up. This HAS to be added!</p>

<p>Would love an official word on this.</p>

<p>Assuming you guys are smart enough to have moles using your competitors products, the overwhelming majority of their users coming in daily are MFP people that smartened up, and Cronometer people that came and paid more specifically for the AI TDEE adjustments. It's a pretty regular conversation one that side. Worst part, is all of us agree this is the better overall tracker, but that one issue sells people.</p>
]]>
        </description>
    </item>
    <item>
        <title>Feature Request: Reorder Diary Groups</title>
        <link>https://forums.cronometer.com/discussion/7089/feature-request-reorder-diary-groups</link>
        <pubDate>Wed, 24 Jun 2026 20:31:16 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>rhd314</dc:creator>
        <guid isPermaLink="false">7089@/discussions</guid>
        <description><![CDATA[<p>It would be great to be able to reorder the diary groups, perhaps via a drag-and-drop mechanism.</p>

<p>For example, I currently have a "Snack" group, which is currently slotted as Group 5. I would like to rename the Snack group to "Pre-Workout Snack", and move that diary group to the top of my diary, before Breakfast, into the slot for Group 1. Similarly, I would like to move my "Biometrics" group, which is currently at the top of the diary in the group 1 slot, lower in the diary, to group 8.</p>

<p>I could rename the group slots one by one, but then past diary entries would be affected (breakfast foods might appear as lunch, etc.)</p>

<p>This is admittedly a minor tweak. But it would be nice to reorder the diary groups without affecting the categorization of past entries.</p>
]]>
        </description>
    </item>
    <item>
        <title>Web calendar: week start on Monday</title>
        <link>https://forums.cronometer.com/discussion/4052/web-calendar-week-start-on-monday</link>
        <pubDate>Wed, 27 Jan 2021 11:40:26 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>Mattias</dc:creator>
        <guid isPermaLink="false">4052@/discussions</guid>
        <description><![CDATA[<p>I'm from Europe. Workdays start on Mondays, is it possible with a setting to change the calendar in the web app, so not Sundays starts the weeks?</p>
]]>
        </description>
    </item>
    <item>
        <title>Protein target calculated by body mass.</title>
        <link>https://forums.cronometer.com/discussion/7047/protein-target-calculated-by-body-mass</link>
        <pubDate>Sun, 17 May 2026 12:31:35 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>w3woody</dc:creator>
        <guid isPermaLink="false">7047@/discussions</guid>
        <description><![CDATA[<p>I have Apple Health integration turned on, and I weigh myself daily, so my current weight flows into Cronometer in the morning.</p>

<p>What I'd like is to be able to set my protein target as a multiple of my weight in kilograms--say, setting it to "1.6 g/kg/day" or "2 g/kg/day"--and have it calculate that day's protein target. Then for fat and carbs, set a percentage to apportion the rest of the calories between those two remaining macronutrients.</p>

<p>I sort of do this in my head now; I've set my percentages so that protein works out <em>about</em> 1.8 g/kg/day. But it'd be helpful if the software could do it instead.</p>
]]>
        </description>
    </item>
    <item>
        <title>Meal plan builder</title>
        <link>https://forums.cronometer.com/discussion/2815/meal-plan-builder</link>
        <pubDate>Wed, 20 Nov 2019 00:54:47 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>Bear</dc:creator>
        <guid isPermaLink="false">2815@/discussions</guid>
        <description><![CDATA[<p>Hi, I like to plan 7 days worth of food for the week which also helps me knowing what to buy at the grocery store. I have to use previous days to build what I'm eating for that day and often my calories are increase or decreasing depending on my activity level. So the feature request would be to make some kind of meal building where I can add in all my food for a day and know all the amino's and nutrients that I am receiving, so a weekly overview of this data would help.</p>
]]>
        </description>
    </item>
    <item>
        <title>Weigh the Data Confidence Score by Food Mass, Not Entry Count</title>
        <link>https://forums.cronometer.com/discussion/7095/weigh-the-data-confidence-score-by-food-mass-not-entry-count</link>
        <pubDate>Thu, 25 Jun 2026 19:37:26 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>Relhak</dc:creator>
        <guid isPermaLink="false">7095@/discussions</guid>
        <description><![CDATA[<p>Hi everyone,</p>

<p>I would like to suggest an improvement to the <strong>Data Confidence Score</strong> shown for micronutrients.</p>

<p>As I understand it, the current Data Confidence Score is calculated in a fairly rough way: it looks at the number of food entries that contain data for a given nutrient and divides that by the total number of food entries.</p>

<p>For example, if I log 13 food items, and 12 of them contain Selenium data, the Data Confidence Score for Selenium would be:</p>

<p><strong>12 / 13 = 92.3%</strong></p>

<p>That makes sense as a simple first pass, but I think it can be misleading in real-world food logs.</p>

<p>The issue is that each food entry appears to be treated equally, regardless of how much of that food was actually consumed.</p>

<p>For example, suppose the 1 item missing Selenium data is a spice or seasoning logged at <strong>0.1 g</strong>. Should that really reduce the confidence score by <strong>7.7 percentage points</strong>? That tiny amount is unlikely to have a meaningful impact on the total Selenium intake.</p>

<p>On the other hand, imagine the opposite case. Suppose the 12 foods with Selenium data are all tiny entries, like salt, pepper, spices, or small garnishes, while the 1 food missing Selenium data is the main meal of the day and accounts for <strong>99% of the total food mass consumed</strong>. In that case, a confidence score of <strong>92.3%</strong> would feel overly optimistic, because the missing data is attached to the food item that matters most.</p>

<p>My suggestion is to calculate the Data Confidence Score using the <strong>mass weight of each food item</strong>, rather than simply counting food entries.</p>

<p>So instead of:</p>

<p><strong>(Items with nutrient data / total items) * 100</strong></p>

<p>It could be:</p>

<p><strong>(Total grams from foods with nutrient data / total grams logged) * 100</strong></p>

<p>For example:</p>

<p>If I eat <strong>910 g</strong> of food in total, and the foods that contain Magnesium data account for <strong>900 g</strong>, while the missing item accounts for only <strong>10 g</strong>, then the confidence score would be:</p>

<p><strong>(900 / 910) * 100 = 98.9%</strong></p>

<p>That seems much more representative than simply counting the number of food entries.</p>

<p>Likewise, if I eat <strong>512 g</strong> of food, but only <strong>12 g</strong> comes from foods with the nutrient data, while the remaining <strong>500 g</strong> is missing that nutrient data, then the confidence score would be:</p>

<p><strong>(12 / 512) * 100 = 2.3%</strong></p>

<p>That would give a much more realistic warning that the nutrient value is probably unreliable.</p>

<p>The fundamental argument is that many food log entries are not equal in nutritional importance. A 0.1 g spice entry cannot contain more than 0.1 g of total substance across all nutrients, while a 500 g meal can obviously have a major impact on micronutrient totals. Treating both entries as having equal impact on the Data Confidence Score can either artificially inflate or artificially deflate the score.</p>

<p>I think a mass-weighted confidence score would better reflect the actual reliability of the nutrient totals and would make the label much more useful, especially for users who log many small ingredients, spices, supplements, or custom recipes.</p>

<p>Curious what others think.</p>
]]>
        </description>
    </item>
    <item>
        <title>Make Reports account for nutrient storage / active nutrient windows</title>
        <link>https://forums.cronometer.com/discussion/7094/make-reports-account-for-nutrient-storage-active-nutrient-windows</link>
        <pubDate>Thu, 25 Jun 2026 19:36:03 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>Relhak</dc:creator>
        <guid isPermaLink="false">7094@/discussions</guid>
        <description><![CDATA[<p>Hi everyone,</p>

<p>I really like using Cronometer for tracking calories, macros, and micronutrients, especially the Nutrition Report feature. However, I think there is one area where the current report view can be a bit misleading: nutrient averages over longer date ranges.</p>

<p>Right now, the report is very useful for showing average daily intake across a selected period, such as the last 7 days, or custom ranges for Gold users. That works well for many things, but not all nutrients behave the same way in the body.</p>

<p>For example, some nutrients are relatively short-lived and need more regular intake. Vitamin C and many B vitamins are water-soluble, so excess intake is generally not stored in the same way as fat-soluble nutrients. On the other hand, vitamins A, D, E, and K are fat-soluble and can be stored for much longer. Minerals and fatty acids also vary a lot depending on the specific nutrient.</p>

<p>Because of this, a longer report average can sometimes create the impression that I am consistently meeting a target, even if the actual intake pattern is very uneven.</p>

<p>Example:</p>

<ul><li>I eat a lot of vitamin C-rich foods on Monday</li>
<li>Then I barely get any vitamin C for the rest of the week</li>
<li>The 7-day average might still look acceptable</li>
<li>But from a practical nutrition perspective, that Monday spike may not be equally relevant by Sunday</li>
</ul><p>This becomes even more important with longer reporting windows. If I look at a monthly report and had very high intake of a short-lived nutrient at the beginning of the month, the average may still look good near the end of the month, even though that intake may no longer be very relevant.</p>

<p><strong>Main idea: active nutrient window shading in reports</strong></p>

<p>My main suggestion would be to add a visual overlay or shaded stacked bar to the Nutrition Report.</p>

<p>The report could still show the normal average intake for the selected date range, but part of the bar could be shaded differently to indicate how much of that intake is likely still relevant based on the nutrient's expected storage or active window.</p>

<p>For example:</p>

<ul><li>Short-lived nutrients could fade quickly</li>
<li>Fat-soluble vitamins could remain visually "active" for longer</li>
<li>The user would then see both the selected date range average and a more biologically relevant recent-intake estimate</li>
</ul><p>So instead of only seeing:</p>

<p>"Vitamin C: 100% average over 7 days"</p>

<p>You might see something like:</p>

<p>"Vitamin C: The full bar represents the 7-day average, while 70% of that bar has a stronger shaded portion to show how much of that intake is estimated to still be recently relevant."</p>

<p>Or visually, the current report bar could stay mostly the same, but with a shaded overlay. The total bar would still represent the selected report average, while the stronger shaded portion would represent the nutrient's estimated active/relevant window based on when it was consumed.</p>

<p>I think this would make the report much more informative, especially for users who rely on longer averages. It would help show the difference between "I averaged enough over this date range" and "I have had enough of this nutrient recently."</p>

<p>This does not need to be treated as a precise medical calculation. Even a rough heuristic or educational visual indicator would be useful.</p>

<p><strong>Alternative / simpler versions</strong></p>

<p>If a full dynamic overlay is too complex, there could be simpler implementations:</p>

<p><strong>1: Label nutrient-specific averaging guidance</strong></p>

<p>Cronometer could label nutrients by recommended tracking style, for example:</p>

<ul><li>Best tracked daily</li>
<li>Best tracked weekly</li>
<li>Long-term average is acceptable</li>
<li>Storage varies / context dependent</li>
</ul><p><strong>2: Small disclaimer next to affected nutrients:</strong></p>

<p>For example:</p>

<p>"Vitamin C is water-soluble and is best interpreted with recent daily intake rather than long-range averages."</p>

<p><strong>3: Report warnings for uneven intake:</strong></p>

<p>If a nutrient target is technically met by the average, but most of the intake came from one or two days early in the range, Cronometer could flag it with something like:</p>

<p>"Average met, but recent intake has been low."</p>

<p><strong>4: User Toggle in Report</strong></p>

<p>Another possible implementation could be to avoid the visual shading entirely and instead make the report average itself nutrient-aware.</p>

<p>For example, Cronometer could offer a toggle between:</p>

<ul><li><strong>Pure average</strong>: the current mathematical average over the selected report period</li>
<li><strong>Active estimate</strong>: an adjusted view where nutrients "decay" differently depending on how they are stored or used by the body</li>
</ul><p>So if I eat a fat-soluble vitamin near the beginning of a 7-day period, it could still have a stronger impact on the active estimate later in the week. But if I eat a large amount of a short-lived water-soluble vitamin at the beginning of the period, its impact would decay faster.</p>

<p>In other words, the report could still use the same date range, but the nutrient calculation would be weighted based on the expected storage/active window of each nutrient.</p>

<p>That might be simpler visually than adding shaded bars, while still solving the same issue: showing the difference between "I averaged enough over this period" and "my recent intake is likely still relevant."</p>

<p>The key thing would be making it optional, because the pure average is still useful. A toggle would let users choose whether they want the standard report or a more biologically contextual "active nutrients" view.</p>

<p><strong>Why this would be useful</strong></p>

<p>I think this would help users avoid misinterpreting long-range averages. Averages are helpful, but for nutrients with shorter storage windows, they do not always tell the full story.</p>

<p>This would also make Cronometer's reports feel more nutrition-aware, not just mathematically correct. The app already tracks a lot of detailed micronutrient data, so adding more context around how to interpret that data could be really valuable.</p>

<p>Curious what others think. Would something like this help you interpret your nutrient averages more accurately?</p>

<p><strong>Concept Ideas:</strong></p>

<p>Current Nutrition Targets:<br /><img src="https://us.v-cdn.net/6030245/uploads/editor/6o/ffazotuk07cf.jpg" alt="" title="" srcset="https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=300, width=300/6030245/uploads/editor/6o/ffazotuk07cf.jpg 300w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=600, width=600/6030245/uploads/editor/6o/ffazotuk07cf.jpg 600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=800, width=800/6030245/uploads/editor/6o/ffazotuk07cf.jpg 800w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1200, width=1200/6030245/uploads/editor/6o/ffazotuk07cf.jpg 1200w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1600, width=1600/6030245/uploads/editor/6o/ffazotuk07cf.jpg 1600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=2000, width=2000/6030245/uploads/editor/6o/ffazotuk07cf.jpg 2000w, https://us.v-cdn.net/6030245/uploads/editor/6o/ffazotuk07cf.jpg" sizes="100vw" /></p>

<p>Shading Idea based on "Active" nutrition:<br /><img src="https://us.v-cdn.net/6030245/uploads/editor/qj/n03rah7rllew.jpg" alt="" title="" srcset="https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=300, width=300/6030245/uploads/editor/qj/n03rah7rllew.jpg 300w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=600, width=600/6030245/uploads/editor/qj/n03rah7rllew.jpg 600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=800, width=800/6030245/uploads/editor/qj/n03rah7rllew.jpg 800w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1200, width=1200/6030245/uploads/editor/qj/n03rah7rllew.jpg 1200w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1600, width=1600/6030245/uploads/editor/qj/n03rah7rllew.jpg 1600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=2000, width=2000/6030245/uploads/editor/qj/n03rah7rllew.jpg 2000w, https://us.v-cdn.net/6030245/uploads/editor/qj/n03rah7rllew.jpg" sizes="100vw" /><br /><img src="https://us.v-cdn.net/6030245/uploads/editor/vd/sd40r4vnfcbn.jpg" alt="" title="" srcset="https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=300, width=300/6030245/uploads/editor/vd/sd40r4vnfcbn.jpg 300w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=600, width=600/6030245/uploads/editor/vd/sd40r4vnfcbn.jpg 600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=800, width=800/6030245/uploads/editor/vd/sd40r4vnfcbn.jpg 800w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1200, width=1200/6030245/uploads/editor/vd/sd40r4vnfcbn.jpg 1200w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1600, width=1600/6030245/uploads/editor/vd/sd40r4vnfcbn.jpg 1600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=2000, width=2000/6030245/uploads/editor/vd/sd40r4vnfcbn.jpg 2000w, https://us.v-cdn.net/6030245/uploads/editor/vd/sd40r4vnfcbn.jpg" sizes="100vw" /></p>
]]>
        </description>
    </item>
    <item>
        <title>Optional food category icons in Diary instead of only 🍎</title>
        <link>https://forums.cronometer.com/discussion/7093/optional-food-category-icons-in-diary-instead-of-only</link>
        <pubDate>Thu, 25 Jun 2026 19:28:54 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>Relhak</dc:creator>
        <guid isPermaLink="false">7093@/discussions</guid>
        <description><![CDATA[<p>Hi Cronometer team,</p>

<p>Small visual feature request: could we get an optional setting to show food category icons in the Diary instead of using the same 🍎 icon for every food item?</p>

<p>For example:</p>

<ul><li>🥛 Dairy and Egg Products</li>
<li>🥩 Beef Products</li>
<li>🐟 Finfish and Shellfish Products</li>
<li>🥜 Nut and Seed Products</li>
<li>🍞 Cereal Grains and Pasta</li>
<li>🍓 Fruits and Fruit Juices</li>
<li>🥦 Vegetables and Vegetable Products</li>
<li>🍬 Sweets</li>
<li>🧄 Spices and Herbs</li>
<li>🍝 Restaurant Foods</li>
</ul><p>The diary currently uses the same 🍎 icon for every food item, except supplements, biometrics, etc. It works, but visually everything blends together. For entries like milk, almonds, oats, sugar, juice, berries, and salt, the apple icon does not really add much information.</p>

<p>To illustrate my point, here's a screenshot of where the repeated 🍎 icon becomes superflous instead of adding meaningful information.<br /><img src="https://us.v-cdn.net/6030245/uploads/editor/kf/qahnl8fkafck.jpeg" alt="" title="" srcset="https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=300, width=300/6030245/uploads/editor/kf/qahnl8fkafck.jpeg 300w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=600, width=600/6030245/uploads/editor/kf/qahnl8fkafck.jpeg 600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=800, width=800/6030245/uploads/editor/kf/qahnl8fkafck.jpeg 800w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1200, width=1200/6030245/uploads/editor/kf/qahnl8fkafck.jpeg 1200w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1600, width=1600/6030245/uploads/editor/kf/qahnl8fkafck.jpeg 1600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=2000, width=2000/6030245/uploads/editor/kf/qahnl8fkafck.jpeg 2000w, https://us.v-cdn.net/6030245/uploads/editor/kf/qahnl8fkafck.jpeg" sizes="100vw" /></p>

<p>A few reasons I think category icons would be helpful:</p>

<ol><li><strong>Faster visual scanning</strong>: When reviewing a meal, category icons would make it much easier to quickly understand what the meal is made of without reading every item line by line.</li>
<li><strong>Better meal composition awareness</strong>: Seeing icons for dairy, grains, nuts, fruit, drinks, and added sugar could help users notice patterns more easily, such as "this breakfast is mostly grains and juice" or "I could add more protein or vegetables."</li>
<li><strong>More intuitive and polished</strong>: Diary UI Cronometer already provides very detailed nutrition data, so category icons would add a nice visual layer that makes the Diary feel more informative and friendly without changing the underlying data.</li>
</ol><p>I think this should definitely be optional, maybe under Diary settings:</p>

<pre spellcheck="false" tabindex="0">Food item icons: 
[ ] Generic food icon 
[x] Category icons
[ ] No icons
</pre>

<p>That way users who prefer the current clean look can keep it, while users who like visual cues can enable category icons.</p>

<p>Thanks for considering it. Cronometer is already great, and I think this would make the Diary even easier to use at a glance.</p>
]]>
        </description>
    </item>
    <item>
        <title>A dedicated product updates newsletter and public roadmap</title>
        <link>https://forums.cronometer.com/discussion/7092/a-dedicated-product-updates-newsletter-and-public-roadmap</link>
        <pubDate>Thu, 25 Jun 2026 19:23:40 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>Relhak</dc:creator>
        <guid isPermaLink="false">7092@/discussions</guid>
        <description><![CDATA[<p>Hi,</p>

<p>I noticed Cronometer already has a "New &amp; Improved" updates page, app update notes are available through the Play Store under "What's New", and there is also a newsletter option in account settings. That's useful, but the newsletter seems more focused on general nutrition content, like how to eat healthy, rather than dedicated product updates, app changes, and development progress.</p>

<p>Would Cronometer consider offering a separate newsletter focused purely on new features, app updates, database improvements, and development progress?</p>

<p>Something like a monthly "what's new, what's improved, and what's coming next" update could be really valuable. Not everyone checks the blog regularly, and app store release notes are easy to miss, especially when they are split across platforms.</p>

<p>A dedicated newsletter could highlight things like:</p>

<ul><li>Newly released features</li>
<li>Improvements to existing features</li>
<li>App changes that might otherwise go unnoticed</li>
<li>Features currently being worked on</li>
<li>Upcoming priorities</li>
<li>Database improvements and quality work</li>
</ul><p>This would not need to be a huge production either. Even a simple monthly format with "shipped, improved, in progress, and database updates" would already make a big difference. For example:</p>

<ul><li>Shipped: New features or app improvements released this month</li>
<li>Improved: Existing features, usability changes, or bug fixes</li>
<li>Database: New foods added, verified entries, or data quality improvements</li>
<li>In progress: Features or fixes currently being worked on</li>
<li>Next: Upcoming priorities or areas of focus</li>
</ul><p>Ideally, this could be available as an email newsletter, an in-app update feed, or both. The important part is making the updates easy to see for people who are interested, instead of relying on users to stumble across them.</p>

<p>To support this, a public roadmap page would also be great. It would give users a clearer sense of where the app is heading and what kinds of improvements are planned. It doesn't have to be a binding promise carved into stone tablets, guarded by lawyers and/or dragons. Even a lightweight "planned / in progress / recently shipped" roadmap would be enough. Check out <a rel="nofollow" href="https://forums.cronometer.com/home/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fimmich.app%2Froadmap">https://immich.app/roadmap</a> for a nice roadmap.</p>

<p>Finally, I think a statistics or database insights page could be really interesting, especially for the nutrition nerds among us. Things like database growth, number of verified foods, recently added foods, data quality improvements, or other behind-the-scenes metrics would help show that the database is actively maintained and improving.</p>

<p>I think the biggest benefit would be transparency. People are more willing to pay for Gold when they can clearly see that the product is improving and that they are getting new value for their money. Some users may also see Gold as a way to support a good product and active development, but that only really works if the work being done is visible.</p>

<p>For existing Gold users, this would also make the subscription feel better. New features, database improvements, and smaller quality-of-life changes are easier to appreciate when they are communicated clearly and regularly.</p>

<p>Basically: the work may already be happening, but making it more visible could make a big difference. It would improve trust, make Gold feel more valuable, and reach users where they actually are instead of hoping they stumble across the updates themselves.</p>

<p>Edit: I know there's an option to subscribe to a Newletter in the Account settings; what I'm looking for is more app updates &amp; feature related and not a "nutrition blog sent to my inbox" stuff.</p>
]]>
        </description>
    </item>
    <item>
        <title>&quot;What-If?&quot; style planning feature</title>
        <link>https://forums.cronometer.com/discussion/6604/what-if-style-planning-feature</link>
        <pubDate>Tue, 11 Feb 2025 18:57:21 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>joenegen</dc:creator>
        <guid isPermaLink="false">6604@/discussions</guid>
        <description><![CDATA[<p>hey all,</p>

<p>I've been working with tracking in Cronometer for a few weeks now and have been absolutely loving it. The tracking and meal creation tools are especially useful and robust, however, I think that there is a big opportunity for an awesome feature that would be VERY useful for a lot of people (myself included). I'm imagining some sort of daily "what-if?" style planning feature that would allow you to build sample meal plans for a day. So you could see, what happens if I don't eat breakfast, what happens if I have a beer after work, etc.</p>

<p>(A little bit of context here, I'm 26M and very active. My primary use for Cronometer is making sure that I'm getting enough calories and a mostly balanced macro split in my diet, but I think that this feature would be equally useful for people in a weight loss context.)</p>

<p>What inspired this post is that I've gotten a few of my go-to recipes imported into cronometer, and have been doing some math in a separate spreadsheet to try to figure out the best combination of these meals and snacks to hit my macro and calorie goals.</p>

<p>So, in my context, I would be able to put together a daily meal plan, and see how far I am away from my daily calorie goals, or if I've hit them. In a weight loss context, the opposite could of course also be true, you could make a daily meal plan, see where you might be over your numbers, see where you can make changes, etc.</p>

<p>I add meals into my diary as i eat them so I get a retroactive look at how I'm doing to hit my calorie and macro goals, and the "ask the oracle" tool seems to fill a similar need, but i think that a true planning tool would be an enormous value add to all kinds of users. I would be more than happy to expand on any of these ideas, and if any other folks have a good system for planning that I'm missing, or if this feature is somewhere that I can't find please let me know!</p>
]]>
        </description>
    </item>
    <item>
        <title>Any chance a public API for Cronometer will be available?</title>
        <link>https://forums.cronometer.com/discussion/3365/any-chance-a-public-api-for-cronometer-will-be-available</link>
        <pubDate>Sat, 30 May 2020 10:30:47 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>LarsNyborgPedersen</dc:creator>
        <guid isPermaLink="false">3365@/discussions</guid>
        <description><![CDATA[<p>I'm trying to do correlational analysis with my data from Cronometer and my data from other trackers, but it's just a pain to have to manually export the CSV each time.</p>
]]>
        </description>
    </item>
    <item>
        <title>Ability to reorder ingredients in recipes</title>
        <link>https://forums.cronometer.com/discussion/2811/ability-to-reorder-ingredients-in-recipes</link>
        <pubDate>Tue, 19 Nov 2019 04:28:44 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>drzoid</dc:creator>
        <guid isPermaLink="false">2811@/discussions</guid>
        <description><![CDATA[<p>It would be really nice to be able to drag ingredients up and down to reorder them. This comes up a lot for me as I make changes to prior recipes, new ingredients are always added at the bottom of the list even though it makes sense for them to be at the top or grouped with other items.</p>
]]>
        </description>
    </item>
    <item>
        <title>Adaptive TDEE would make Cronometer Perfect</title>
        <link>https://forums.cronometer.com/discussion/5132/adaptive-tdee-would-make-cronometer-perfect</link>
        <pubDate>Sun, 01 May 2022 15:56:57 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>jrharte</dc:creator>
        <guid isPermaLink="false">5132@/discussions</guid>
        <description><![CDATA[<p>Hi team,</p>

<p>If you guys added an option for adaptive TDEE calculation this would be Cronometer perfect in my eyes.</p>

<p>For the Adaptive TDEE to work accurately users would need to be consistent with food logging, and daily bodyweight entries. The calculation works by using the consumed calories and the change in weight.</p>

<p>It takes a few weeks of logging for it to produce accurate results, but it's much better than TDEE multipliers and smart watch calories etc.</p>

<p>Obviously it should be an option for users to select or deselect as they please, or the maybe allow it to be shown alongside the other calculation.</p>

<p>I've been entering data manually into this app: <a rel="nofollow" href="https://forums.cronometer.com/home/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.shumate.tdeeCalculator">https://play.google.com/store/apps/details?id=com.shumate.tdeeCalculator</a>  (but got lazy and haven't entered since Dec 2021!)</p>

<p>If you need help with the calculation / formulas, I believe this spreadsheet is one of the best resources: <a rel="nofollow" href="https://forums.cronometer.com/home/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F0B7gGXXQIy4R4ejRRNkZHZHFDOW8%2Fview%3Fresourcekey%3D0-6D2ColRi_grLWCiE63F0MA">https://drive.google.com/file/d/0B7gGXXQIy4R4ejRRNkZHZHFDOW8/view?resourcekey=0-6D2ColRi_grLWCiE63F0MA</a></p>

<p>Thanks.</p>
]]>
        </description>
    </item>
    <item>
        <title>Allow a percentage next to the &quot;Add Expenditure Above Baseline to Energy Target&quot;</title>
        <link>https://forums.cronometer.com/discussion/7076/allow-a-percentage-next-to-the-add-expenditure-above-baseline-to-energy-target</link>
        <pubDate>Tue, 09 Jun 2026 22:05:55 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>StormFireKitty</dc:creator>
        <guid isPermaLink="false">7076@/discussions</guid>
        <description><![CDATA[<p>I have noticed that the fitness tracker app seems to give me too much credit for a fair amount of my activity.</p>

<p>I'd like to be able to set a percentage under Add Energy Expenditure Above Baseline to Target.</p>

<p>That way I could tell it "My Energy target is 1800 calories, but I want you to add 50% of the additional expenditure to my target for the day". That would keep me from overdoing the calories on yardwork day, for example, when the app thinks I worked 800 extra calories by mowing the grass... My yard is <em>not</em> that big.</p>
]]>
        </description>
    </item>
    <item>
        <title>Toggle feature to zero out fibre</title>
        <link>https://forums.cronometer.com/discussion/7014/toggle-feature-to-zero-out-fibre</link>
        <pubDate>Tue, 21 Apr 2026 15:18:02 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>Methos5k</dc:creator>
        <guid isPermaLink="false">7014@/discussions</guid>
        <description><![CDATA[<p>As I mentioned in this post: <a href="https://forums.cronometer.com/discussion/7010/fibre-count-towards-calories#latest" rel="nofollow">https://forums.cronometer.com/discussion/7010/fibre-count-towards-calories#latest</a></p>

<p>Fibre seems to be accounting for more calories than the body can actually utilize. This could be problematic for people reducing their calorie intake near a lower threshold, as they would be under consuming. It can also be an issue for those look to maintain or gain weight. In these situations, the issue is more acute when the diet is high(er) in fibre.</p>

<p>Ideally, I think it would be great to see a change in the calculation to include more appropriate values for soluble and insoluble fibre; this would in turn reflect properly in the pie chart for consumed kcals and their percentages, plus the kcal value of the food item, as well as the meal's calorie value.</p>

<p>However, if that doesn't happen, it could be equally handy to have a toggle button that voids all of the fibre in a meal/item/day. Purpose of this could be to switch being seeing the values in the food/daily report, but also if it's toggled off, then the pie chart and caloric values would adjust downwards.</p>
]]>
        </description>
    </item>
    <item>
        <title>Logging daily vitamins and supplements I take</title>
        <link>https://forums.cronometer.com/discussion/7073/logging-daily-vitamins-and-supplements-i-take</link>
        <pubDate>Mon, 08 Jun 2026 11:45:53 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>Chas</dc:creator>
        <guid isPermaLink="false">7073@/discussions</guid>
        <description><![CDATA[<p>I don't see a way to log these items.  It would be good to have them reflected in the nutritional intake.  It says I'm deficient in Vit D for example and yet a take a supplement for that.</p>
]]>
        </description>
    </item>
    <item>
        <title>What visibility do friends have into my account?</title>
        <link>https://forums.cronometer.com/discussion/7074/what-visibility-do-friends-have-into-my-account</link>
        <pubDate>Mon, 08 Jun 2026 16:01:13 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>ATLBuckeyeGirl</dc:creator>
        <guid isPermaLink="false">7074@/discussions</guid>
        <description><![CDATA[<p>Just trying to figure out if I invite someone to be a friend, what can they see in my profile?</p>
]]>
        </description>
    </item>
    <item>
        <title>Custom Local Barcode Directory</title>
        <link>https://forums.cronometer.com/discussion/7069/custom-local-barcode-directory</link>
        <pubDate>Fri, 05 Jun 2026 07:44:27 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>adnan2997</dc:creator>
        <guid isPermaLink="false">7069@/discussions</guid>
        <description><![CDATA[<p>We know that if i scan a barcode and if it isnt in cronometer's database, it asks us to create a new custom food. <br />
and then if it gets added to their system, we might get notified.</p>

<p>But for example I live in europe. and many food are not in their database. and also most of the food never i scan doesnt go to the database. But either ways, if i have to eat the same food again (sometimes after a gap of many days). I have to either create a new custom food, or go back and search the food that i created 2-3 days ago, which is a huge hassle.</p>

<p>From the user's perspective, I think we can add a button which i can check. Called "include in your local directory" or something. Which would mean that in my mobile phone's storage, and in my account, this barcode shall be stored for the custom food that i make. So that next time when i'm having the same food and i barcode scan it, I can just use the custom food i created last time, rather than manually scrolling and scanning through the custom food's list to choose it from.</p>

<p>from the developer's pov, this wont take cloud storage. even if you intend to make it sync to an account, it would just be a bunch of string of numbers for each account. Which can be extremely small in size.</p>
]]>
        </description>
    </item>
    <item>
        <title>AI Integration [Feature Request]</title>
        <link>https://forums.cronometer.com/discussion/7068/ai-integration-feature-request</link>
        <pubDate>Fri, 05 Jun 2026 07:37:40 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>adnan2997</dc:creator>
        <guid isPermaLink="false">7068@/discussions</guid>
        <description><![CDATA[<p>I would like to propose an idea of AI integration. There are many AI integration in other apps already and AI at this point sounds like slop and stuff. But i think the idea i'm thinking is helpful.</p>

<p>Voice to text to auto-input. <br />
For example, i say to the chat "i had 300grams of yogurt". the ai gives me a few options for clarification. i choose one, it inputs automatically into the system. This can also be a less hassle than creating a new custom food everytime i make a new dish. I can just say the ingredients and amounts i used in a dish with its weight. the ai can then make a custom dish for me rather than me going out of the way to calculate everything.</p>
]]>
        </description>
    </item>
    <item>
        <title>Sharing links for food items or meals</title>
        <link>https://forums.cronometer.com/discussion/7065/sharing-links-for-food-items-or-meals</link>
        <pubDate>Tue, 02 Jun 2026 20:20:16 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>kenziegarcia</dc:creator>
        <guid isPermaLink="false">7065@/discussions</guid>
        <description><![CDATA[<p>Would be awesome if there were a way to send a meal to a user through a link or at least a food listing. My husband and I eat the same dinner and it would be so helpful to have just one of us log and the other share the meal or items easily!</p>
]]>
        </description>
    </item>
   </channel>
</rss>
