Settings flows as the scheduler

Android only. The settings store is the source of truth; the work queue is a projection of it. One long-lived collector watches the preferences and (re)enqueues or cancels.

That is the shape to aim for, and it is worth knowing that the reference does not have it everywhere: alongside the scheduler below, the launcher activity enqueues two more periodic works of its own, one of them from a second settings collector on the activity's own lifecycle scope. That second one is exactly the anti-pattern named just below the sample — a live example rather than a hypothetical, and the first thing to look for in a codebase that already has a scheduler.