When a student remembers a form that needs to be sent tomorrow, opening a task app is rarely the actual goal. The goal is to avoid forgetting the form. However, a typical task system may require the student to open the app, find the right list, enter a title, set a date, choose a reminder, and remember to return later. A message-based system can begin with the original thought: “remind me to send the form tomorrow at 4.”
This is the reasoning behind TextTodo. Messages are not guaranteed to receive attention, and placing a reminder there does not make it automatically useful. The advantage is more practical: the same conversation can become both the place where the task is captured and the place where it returns.
What notification research actually found
A 2014 CHI study analyzed nearly 200 million Android notifications from more than 40,000 people. Among the notifications that people eventually clicked, 50% were clicked within 30 seconds and 83% within five minutes. Participants also rated notifications from messaging apps as the most important category, while notifications connected to people and real-world events tended to be valued more highly.
A separate one-week field study of 15 smartphone users found that notifications were typically viewed within minutes, even when phones were silent. Personal communication and the social expectation around it helped explain why some messages received attention.
It would be easy to use these results as an excuse to send more notifications, but that conclusion is not supported. Both studies are old, Android-focused, and unrelated to TextTodo or iMessage task completion. They do not prove that a message will make someone complete a task. Rather, they show that many clicked notifications received attention quickly and that people placed particular value on communication and event-related information.
Why one conversation can reduce friction
Capture happens where the thought already is
Tasks often surface in the middle of another activity. A separate productivity app asks you to switch contexts and translate the thought into its interface. A message lets you record the thought in the form it arrived: “buy poster board after practice” or “move counseling to 6:30.”
Follow-ups can use context
Human plans change through correction. “Actually, make that Friday.” “I did the first one.” “Snooze it for twenty minutes.” A conversation can preserve the reference to “that” or “the first one,” so the user does not have to reopen and reconstruct the original item.
The reminder can be actionable
A good reminder says what needs attention and arrives when it is useful. TextTodo supports user-requested one-time reminders and snoozing, while tasks with exact deadlines receive reminders ten minutes before and at the deadline. A new user also receives a 7am local task list after confirming a timezone, but that schedule can be changed, replaced with an optional smart check-in, or removed. Empty daily lists are skipped. These rules are designed around the task itself instead of a goal of producing as many notifications as possible.
The risk: turning a trusted channel into noise
The same research that makes messaging interesting also warns against abuse. Frequent, irrelevant notifications become annoying, and people may block or remove the source. A message-based task assistant therefore needs stricter restraint than a feed designed to pull people back.
That means users must be able to edit, snooze, and remove reminders, including the default daily list. Confirmation messages should stay short, and the system should not manufacture urgency or pretend every task deserves an alert. It also has to be honest about delivery: TextTodo reminders are a convenience, not an emergency alarm.
A better measure than opens
The success metric for a task assistant should not be how often it interrupts someone. Better questions are whether the user captured the right task, received the reminder they chose, understood what it referred to, and could update the plan without fighting the interface.
Messages already support quick capture, familiar notification behavior, and contextual follow-up, which gives them a useful advantage over another destination a student has to remember to check. However, that advantage can disappear quickly if the conversation becomes noisy. TextTodo belongs in Messages only for as long as its reminders remain relevant enough to justify the interruption.