“Review flashcards every weekday” and “remind me every two hours to check the experiment” both repeat. However, the first sentence creates work that can be finished, while the second creates a message that needs to appear again. Treating both as the same object makes the system harder to understand.
A recurring task creates new work
Every occurrence of a recurring task should be completable. A student can finish it, remove it, or leave it outstanding. Daily reading, a weekly discussion post, and a monthly reimbursement form all fit this model because each occurrence represents an actual obligation.
The recurrence rule decides when the next obligation belongs on the list. TextTodo supports calendar-based rules for daily, weekday, selected-weekday, and monthly tasks. Completing one occurrence creates one future occurrence. Missing several days does not create a pile of old copies.
A recurring reminder creates another interruption
A recurring reminder does not need a completion state. Its purpose is to bring back a message after an interval, such as checking an experiment, changing laundry, standing up during a long session, or looking at a status page.
Research on cognitive offloading shows that external reminders can increase the chance of remembering a future intention. That benefit still has a cost because a reminder has to be created, checked, and allowed to interrupt something else. Repetition should therefore come from a real need rather than the assumption that more alerts will always help.
If finishing the repeated item matters, it should be a recurring task. If only the return of the message matters, it should be a recurring reminder.
A reminder cannot pretend that work was completed
A daily reminder that says “do vocabulary” does not know whether yesterday’s vocabulary was finished. When completion matters, a recurring task keeps the current obligation visible and advances the series only after that occurrence is done.
The opposite mistake creates its own problem. Turning every repeating cue into a task fills the list with obligations that were never meant to be tracked. Checking an experiment every two hours during a short process may need repeated interruptions without needing a permanent task each time.
Match the rule to the schedule
- Work that repeats every weekday belongs in a calendar-relative recurring task.
- Work that repeats on Monday and Thursday belongs in a selected-weekday task.
- Work due on the first of each month belongs in a monthly task.
- A cue needed every two hours belongs in a fixed-interval reminder.
- An alert ten minutes before one deadline is a deadline reminder, not a recurring object.
An outage should not create a flood
If a server returns after being offline, replaying every missed cue would make the reminders less useful. Twelve messages arriving together do not create twelve new chances to act. TextTodo skips missed fixed-interval deliveries and schedules the next one. Recurring tasks follow the same basic principle by creating one future occurrence instead of producing a historical backlog.
This approach gives up the appearance of perfect recovery in order to preserve the meaning of the current list and the current moment. A reminder from six hours ago cannot become timely again simply because the server came back online.