What's new

Gauge is now on Google Play, alongside the App Store.

It is the same app and the same subscription — Pro follows your account, not your handset — with Health Connect in place of Apple Health for workouts and weight, and Strava syncing on both.

Also today

Quality sessions are now graded against your maximum heart rate rather than a fixed number. A single threshold asks very different things of a 25-year-old and a 45-year-old, and asks more again of a woman than a man of the same age — so hard sessions were being logged as easy ones for anyone whose heart rate doesn't run high.

Gauge now estimates your ceiling from your age and sex, raises it if you've ever recorded higher, and judges the session against that. And when a session follows one you planned, the plan's own description wins: interval work averages deceptively low, and you already told Gauge what the workout was.

Tapering is not just training less. Your carbohydrate needs to go up while your mileage comes down, and that is exactly when most plans go quiet.

Race week now carries its own protocol: a carbohydrate load across the final days, race day fuelled as race day rather than as another long run, and a race plan you can read through — and share — before you start.

Two things that were read-only are now yours to work with.

Fuelling, with timing

A long-run day used to show a number of carbs to take during the session. It now shows a plan: how many grams, how many gels that is, when to take the first one, and roughly how often after that.

The timing isn't invented — the engine only ever fuelled the minutes after the first half hour, because you don't need carbs in the opening 30 minutes of a run. That was buried in the arithmetic and is now said out loud.

The number depends on how much your stomach handles per hour, which is a trained capacity, not a fitness score. Gauge now asks in the fuelling card itself, where the number it changes is on screen — rather than in a settings row nobody found. Answer for where you are today; come back and move it up as you practise.

Plans change

Sessions can now be added, edited, moved between days, and removed. Tap a session on the Training screen to change it, or "Add a session" on an empty day.

Moving a session is just editing its day — because "move it to Saturday" and "I put it on the wrong day" are the same thing. And because the plan is what grades a day before you've run it, correcting a 90-minute long run to 120 moves that day's carbohydrate too.

Gauge has always computed your day from your training, your weight, and your goal. It just never told you how. Two new surfaces fix that.

Why today

Tap the day type at the top of Home — "Rest day", "Long day", whatever today is — and Gauge opens its reasoning. Your target, your maintenance for the day, and the gap between them, followed by the actual notes the engine wrote while grading you: deficit capped, weekly deficit balanced, results-adjusted −150 kcal.

That text was always there. It was written every single day and shown to nobody.

This week

Tap the date and choose This week for a Monday-to-Sunday review: every day's target against what you actually ate, with a tick marking where the target sat, and the days you barely logged marked as partly logged rather than counted as a shortfall you didn't have.

Below it, your weight over the last fortnight, and how close Gauge is to having enough evidence to tune your targets — "7 of 10 days of targets" — so the adaptation stops being something that happens silently in the background.

Smaller things

• Your activity level from onboarding is now used directly instead of being re-derived, which was quietly grading the most active users as moderate.
• Your cut pace comes from the goal weight and target date you actually set, rather than one fixed rate for everybody. Ask for more than Gauge will run and it says so on the spot, instead of missing the date two months later.

The number you check most — calories left today — no longer requires opening the app. Gauge now ships three iPhone home-screen widgets, and they stay current with every meal you log.

The widgets

• Today's Calories (small) — your calories remaining over a tick-mark gauge, with a needle at exactly where your day stands.
• Today's Calories (medium) — the big number plus your goal, food logged, and a progress bar, with a Log button that drops you straight into the food input, keyboard ready.
• Today's Macros (medium) — labeled bars for carbs, fat, and protein against today's targets, just like the summary inside the app.

They show today's targets, not static ones — a rest day, a long-run day, and a race day all read differently on your home screen, exactly as the engine set them.

Adding one

Press and hold an empty spot on your home screen, tap Edit → Add Widget, and search for Gauge. Swipe to the design you want and tap Add Widget. The full walkthrough — and what to do if a widget looks stale — is in Home-screen widgets.

Widgets need iOS 17 or later and this update (1.0.2) from the App Store. Android widgets are on the roadmap.

Until today, Gauge computed your targets from a formula — a good formula, but a formula. Real metabolisms drift from formulas: cuts plateau, gain phases stall, and the honest answer has always been to adjust. Now Gauge does that adjusting for you.

How it works

Keep logging and weighing in like normal. Every day, Gauge compares two weeks of evidence: what it predicted your maintenance calories were, versus what your logged food and your weight trend say they actually were. When the two disagree, your maintenance estimate moves toward the evidence — a little at a time, never more than 300 calories in total — and every target built on it moves with it.

That means a plateau on a cut gets a genuinely deeper push, a stalled gain phase gets more food, and loss that's running too hot gets reined in. All at the pace you chose in Weight Goal — the adjustment changes what Gauge believes your body burns, not how aggressive your plan is.

Built-in honesty

• No adjustment happens from thin evidence. It takes about ten well-logged days and a few weigh-ins in each week — if the data is spotty, Gauge holds steady and your coach will suggest logging or weighing in instead.
• Your calorie floor is untouchable. No plateau can push your targets below it.
• Nothing is silent. Adjusted days say so right in the day's explanation ("results-adjusted −150 kcal"), and your morning digest can tell you why.

What you'll notice

For the first couple of weeks: nothing — Gauge is gathering its evidence. After that, if your results and the formula disagree, you'll see the adjustment appear in your day's rationale and your targets shift by small steps. If they agree, nothing changes, which is its own kind of answer.

Read the full story in How Gauge sets your targets.

A big day for getting answers — and for logging breakfast faster.

Help & Guides, in the app and on the web

Seventeen guides covering everything from your first day to troubleshooting sync, organized by topic. Find them in Settings → Help & Guides, or at ongauge.app/help. Articles update continuously — no app update needed.

Contact support, properly

The new contact form replaces the old email link. Send a message and you'll get an instant confirmation; a real person replies, usually within a day or two. Reaching out from inside the app automatically includes your app version, so we can help faster.

One-tap meals

Your usual breakfast is now one tap: long-press a meal's header on Home to save it as a meal group, then log the whole thing from your Library whenever you eat it again. Each item still logs individually, so everything stays editable.

Also in this update

• Your app version now shows at the bottom of Settings.
• Sharper social previews and better search visibility for the website.

Point your camera at the plate and Gauge does the rest.

Photo logging is live for Gauge Pro: snap a meal (or pick one from your library), optionally note anything the photo can't show — cooking oil, hidden ingredients, how many eggs — and Gauge identifies the foods and estimates portion-aware macros.

Photos are analyzed and immediately discarded; they're never stored. As always, every estimate stays editable — portions, multipliers, and the Ask Gauge correction path all work on photo-logged entries.