Low-power mode should degrade nonessential visuals and sensor sampling

What it is

When charge has fallen to a few hours still needed outdoors, the watch should turn off what is not needed now: always-on and per-second motion, expensive face drawing, high-rate optical heart rate, GNSS that is not in use. What remains is time, alarms, the one expensive sensor already running in a workout, and a button that still confirms. Degrade is the product changing behavior on purpose, not the UI shattering after the battery manager kills processes. This entry is about how that low-power band pulls back visuals and sensors. It is not about whether always-on should be on in ordinary use, and not about how chatty background sync should be in ordinary use.

Why it happens

At low charge the marginal value of each milliamp-hour rises: the same heart-rate flash is a rounding error on a full-day budget, and at ten percent it may be the difference between getting home still alive. Visual effects (translucency, a frame every second, a full-color face) and sensor sampling (continuous optical, dual-frequency location) are two kinds of spend that can be cut as blocks, after which the main path (read time, dismiss an alarm, finish logging this run) still exists. If the system does not cut, apps keep running at full-charge refresh and sample rates, charge hits zero with no warning, and the watch becomes black glass with not even the time—worse than “rings pause for a while, heart rate becomes a spot check.” Degrade must be readable. People need to see “saving power now,” or a slower ring and sparser heart-rate dots will be read as a fault.

Where it stops holding

A navigation or outdoor activity already underway may have GNSS as its primary sensor. Low power should warn “continuing will empty this soon” and let the person choose, not silently kill the track halfway. Continuous clinical monitoring that the wearer is actively using has a clinical meaning when downsampled; do not treat that as ordinary saving. Low charge while on a charger is only a number that has not yet climbed; do not enter degrade, or a plugged-in watch will drop into a sparse mode for no reason. Haptics or high luminance that accessibility depends on should not be swept away with low power; cut decoration first, assistive channels later.

Applying it

• Define one explicit low-power band: always-on off, per-second drawing off, face down to a high-contrast sparse time, optical heart rate on sparse checks, unused GNSS off.
• Entering the band gets one screen that says what was turned off and what remains, plus a one-tap exit (the wearer accepts a shorter remainder).
• Exempt a sensor that the in-progress activity depends on from automatic degrade; warn remaining time instead.
• Verify by entering the band at ten percent and walking read-time, dismiss-alarm, and finish-an-already-started walk. Those three must still complete. Then check that the power curve sits clearly below the same scene at full-charge policy. If the main path breaks, or the curve barely moves, degrade has not yet cut the visuals and sampling that actually spend.

Related

• Within the group: K4.08.1 Always-on display and frequent interaction drain a small watch battery · K4.08.2 Background sync frequency trades freshness against battery · K4.08.4 Expected watch battery life shapes tolerance for interaction delay
• Adjacent: K4.06 Watch Faces and Complications · K1.09 Power, Data, and Weak Networks · F7.12 Performance Cost of Motion
• Search terms: low power mode · sensor downsampling · watch battery degrade