A bad day is the moment a screen time app either keeps you or loses you. Munen handles it with three rules: your zone can fall at most one step per day, it never falls in the middle of a day, and if you have put in real effort by 8 pm from a low zone, you get a zone back that evening and keep it the next morning.
None of that is softness. It is what the engine has to do to avoid the two failure modes that make people delete this category of app: being punished on the day you most needed slack, and being rewarded and then demoted the next morning anyway.
Rule one: at most one zone per day
Your zone is capped to one step from the zone you actually saw yesterday, up or down. It does not matter how bad the day was.
This matters because a bad day hits the engine twice. It raises the load through the weighted signals, and it can also trip one of the two explicit rules that subtract a zone outright, for heavy night use or for pushing past the pause repeatedly. Without the cap, a single Thursday could drop you from 4 to 2.
The cap also sets the recovery speed, and it is symmetric. Three good days in a row take you from 2 to 5.
| Question | Answer |
|---|---|
| Maximum fall in a day | 1 zone |
| Maximum rise in a day | 1 zone |
| Anchor for the cap | The zone you actually saw yesterday, not the raw computed trend |
| Trend window | Yesterday only |
That last row is worth pausing on. Munen used to average the last seven days with exponential decay. Under that window, yesterday carried a weight of 0.41 and could be outvoted by the six days before it. A user who put in real effort saw nothing move. That is the shape of learned helplessness, and it is the opposite of what a habit app needs to produce. The smoothing now comes from the one step per day cap, which demands the same sustained evidence and can be explained in a sentence.
Rule two: nothing tightens mid day
All downward movement happens at the nightly recalculation. There is no moment during your day where the phone gets harder because of what you just did.
This is a deliberate refusal of the obvious design. It would be technically easy to lengthen the pause after the fourth open in an hour. It would also mean that the worse your afternoon went, the more the app pressed on you, which is precisely when people uninstall.
So Munen reads the day, waits, and changes the settings tomorrow morning.
Rule three: the 8 pm checkpoint
The one same day change Munen allows is upward.
At 8 pm, if you are in zone 1 or 2 and you have had a genuine effort day, Munen raises your zone by one and sets that as a floor.
| Condition | Threshold |
|---|---|
| Checkpoint time | 20:00 local |
| Starting zone | 1 or 2 |
| Time spent inside access windows today | Under 15 minutes |
| Times you pushed past the pause today | 8 or fewer |
| Result | Zone plus one, kept as a sticky floor |
The 15 minute figure is anchored twice. It is one third of the 45 minutes of distractor exposure that defines the severe resistance pattern, so a threefold reduction reads as real effort. It is also half of the roughly 30 minutes a day that Hunt and colleagues identified as a healthy target in their 2018 trial at the University of Pennsylvania, which means it sits comfortably below "barely acceptable" rather than at it.
The bypass count of 8 is only a backstop. It catches someone hammering the shield all day in very short bursts, without punishing a person who opens an app often but briefly. Total exposure already governs that case.
8 pm is chosen because school and work are done, it is inside the real usage window, and it is before sleep. A checkpoint at midnight would arrive after the evening you were trying to influence.
Why the boost is sticky
The floor persists across days. Your zone will not fall below it the next morning just because the underlying trend has not caught up yet.
The alternative was tried and it felt punitive. Earning a zone at 8 pm and losing it at 6 am is reward then removal, which is worse than never having given it. So the floor comes down only at the daily recalculation, and only by one step at a time, exactly like every other downward move.
The floor lifts on its own when the trend catches up to it, which is what graduation looks like.
What this does not do
It does not hide the real number. The stored trend is untouched. Your streak runs on the zone you actually see, which includes the boost, but the underlying trend is still what it is.
It does not override your own choice. If you manually set your zone that day, the boost does not fire. Your decision wins.
It does not fire from zone 3 or higher. The boost exists for the two lowest zones. If you are already in the middle of the range, an effort day simply shows up in tomorrow's recalculation.
Common questions
Does a bad day break my streak? The streak runs on the zone you actually saw, boost included. So an effort day that earned a boost does not break it.
Can I just set my zone myself when I know it is a bad day? Yes. Once a day on the free plan, roughly every four hours on Premium.
What if I want a wall on a bad day? That exists, and it is opt-in. The hard day contract lets you choose, ahead of time, what zone 1 does: a longer pause with a small window, a light nudge, or no entry at all. The default is the middle one.
Why not just let me turn everything off on a bad day? You can uninstall in ten seconds, and the free plan does not lock you in. The point is to make the honest option cheaper than the drastic one.
The short version
One zone per day, down or up. No tightening while the day is still happening. A zone handed back at 8 pm for a genuine effort day, and kept the next morning. For how this compares to apps with no cross-day memory at all, see Munen vs ScreenZen.