Why an ad on every save breaks the weigh-in habit

A twenty-second penalty on a five-second task

Daily behaviours are extremely sensitive to friction, and a weigh-in is a behaviour with no immediate reward at all — the payoff arrives weeks later, as a line on a chart. When typing the number takes three seconds and saving takes one, people slot it between the shower and the coffee without thinking. Put an interstitial with a delayed close button in the middle and the whole thing costs five times as much, all of it time that buys the user nothing.

That's why the complaints are rarely phrased as "it's slow". They're phrased as "I deleted it the moment the ad appeared". The objection isn't the twenty seconds; it's that the app started charging a toll on the one action it exists to encourage.

The worst case is the day you come back

An ad-per-save design has a cruel property: it charges the most at the exact moment the user needs the least resistance. Miss two days, come back, and you owe three saves — which means three ads. Miss a week and it's seven.

In practice people make one of two choices there. They abandon the missed days, or they abandon the app. Either way the line breaks, and a broken line is much easier to walk away from than a continuous one. The value of a weight log was never a single morning's number; it's the trend. An interstitial on save is placed precisely where it does the most damage to that trend.

Where ads are fine, and where they aren't

There's nothing wrong with a free app being funded by advertising. What matters is placement. A workable rule: an ad belongs where the user has already finished what they came to do and is pausing anyway — never in the middle of the action they repeat every single day.

Concretely, that splits like this.

• Acceptable: a fixed banner at the bottom of the screen, a stats or settings page people open once a week, or behind an occasional action like a backup or an export.
• Bad: immediately after the save button, on every app launch, on every date change — anywhere inside the daily loop.
• Worst: inside a multi-day catch-up flow, which taxes the user hardest at the moment they were trying to rescue their own data.

What to check before you commit to an app

Store listings won't tell you. These four checks usually settle it within five minutes of installing.

• Save three entries in a row. If a full-screen ad appears each time, you already know how this ends a few weeks from now.
• Sort the reviews by most recent and search them for the word "ads". This is far more informative than the star average.
• Try logging a past date. If backdating is blocked — or triggers its own ad — the app has no recovery path for the week you inevitably miss.
• See whether removing ads requires a subscription. If "remove ads" is the only cure, the interruption isn't an accident, it's the business model.

How Scalendar handles it

Scalendar doesn't interrupt the save. Typing a weight and saving it, or filling in a whole missed week from the catch-up screen, are treated as flows that have to finish cleanly. Backfilling three days never costs you three ad breaks.

The log itself stays on your phone: no account, no sign-in, nothing uploaded, and a CSV export whenever you want a copy. For an app you open every morning, not being in the way every morning matters more than any feature list.