Pick the trigger before the wording.
Some reminders belong at a time: put the bins out at seven. Others belong before an event: bring the signed form to school. Some depend on something happening: ask your partner about the repair when you are both home. The trigger determines what information the reminder system needs.
Use a time-based reminder when the system cannot reliably know the condition. “Before we leave” sounds simple, but it requires dependable departure context. A fallback reminder at a known time is better than assuming a condition will be detected.
Keep the reminder useful.
- Name the action: “Put the library books in the school bag” is more useful than “Books.”
- Choose a recipient. A shared speaker is not the same as a message to one person.
- Include what changed. If pickup moves from four to five, update the original reminder.
- Set an end point. Completing or cancelling a task should stop its future reminders.
- Keep sensitive details private. A room announcement may be heard by visitors or other family members.
What “Am I forgetting anything?” should return.
Start with the few things that matter now: a confirmed commitment due soon, an item needed for the next event, or an unfinished action you chose to track. Separate those from guesses. A reminder based on yesterday’s observation should say when that observation happened.
A long recap of every open task is rarely useful as you walk out of the door. Give the person a short answer, then let them ask for the full list. If the calendar is not connected or the information is old, the assistant should say so.
Where Aspen fits.
The Aspen household developer preview includes local tasks and a reminder scheduler. We are building toward reminders that can use authorized household context, including the conversations and rooms you opt into. Condition-based and departure experiences on the site illustrate that direction.
The full consumer experience is in development. Reliable person recognition, room context and event timing matter before a reminder can be delivered automatically. A reminder system is also not a substitute for an emergency alarm or medical monitoring.
Put it to work
Tomorrow’s library books.
A simple reminder workflow you can use today with a calendar or task app. Aspen’s context-aware version is an illustrative experience in development.
Get the detail right.
Confirm which child needs which books, and on which date. “Tomorrow” needs to become the actual school day.
Choose a useful moment.
Remind the person packing the bag the evening before, rather than alerting the whole household after everyone has left.
Stop when it is done.
Mark the packing task complete. If plans change, edit that reminder instead of adding another overlapping one.
Who this is for.
For households where the problem is remembering at the right moment, especially school items, returns, errands and promises made during a busy day.
A few good questions.
How is a reminder different from a task?
A task records work to do. A reminder decides when to bring it back to someone’s attention. One task may need a reminder, but repeated reminders should not create duplicate tasks.
Can Aspen remind me when I see someone?
That is a context-aware experience we are building toward, not a universally available capability. It needs permission, reliable identity and useful presence information. A time-based fallback may still be needed.
Can a shared speaker announce personal reminders?
Treat a room speaker as shared space. Choose which reminders may be spoken aloud, and keep personal details out of household announcements unless the person has chosen to share them.