Use cases
Explore 60 concrete household problems — including the needs behind searches for a chore app for kids, couples, families or roommates, a chores management app, and Last Done tracking. The home page stays simple; this is the problem library.
All 60 examples are grouped below. Search only changes what is shown on screen; every use case is part of this public page.
Who is responsible, whose turn is it, and what happens when somebody else steps in?
Trash, bathroom cleaning, and kitchen resets turn into recurring group-chat debates about whose turn it is.
Use Rotation so the current turn stays visible while the real completion history records what actually happened.
See how Done When handles thisParents know what a child should do, but repeating the same reminder every day creates unnecessary friction.
Use an Assigned task with a daily or weekly frequency so the responsibility and latest completion stay clear.
See how Done When handles thisGeneral trash, paper, glass, and recycling can follow different rhythms and may rotate between different people.
Combine Rotation or Assigned responsibility with frequency and Last Done in one shared task record.
See how Done When handles thisIn dorms and student apartments, nobody wants to manage everybody else or search old messages for chore history.
Use Rotation, Assigned, or Anyone per task and keep real completions attached to the chore instead of the chat.
See how Done When handles thisHallways, stairs, and entrances belong to everybody, which often means responsibility is unclear.
Use Rotation to circulate the chore while the actual completer remains part of the history.
See how Done When handles thisA small shared kitchen has recurring jobs but usually does not need a full project-management system.
Use Rotation, Assigned, or Anyone depending on whether the job needs turns, an owner, or simply a completion.
See how Done When handles thisSmall shared spaces need lightweight recurring responsibility without turning household-style chores into work projects.
Keep a small set of shared tasks with clear responsibility, frequency, and completion history.
See how Done When handles thisThe person responsible for a task is not always the person who actually completes it.
Done When keeps responsibility separate from the actual completer so helping does not falsify the shared history.
See how Done When handles thisRecurring cleaning jobs that are easy to repeat too soon or forget for too long.
Both people do things around the home, but neither remembers when a specific job was last done. It gets repeated too soon or forgotten for too long.
Last Done keeps the latest real completion visible, while frequency and Needs Attention add context about when the task matters again.
See how Done When handles thisIt feels like the sheets were changed recently, but nobody can remember whether that was last week or last month.
Keep the latest real bedsheet change visible and compare it with the expected rhythm instead of guessing.
See how Done When handles thisBathroom cleaning often happens by feel, so it is hard to tell whether it was done recently or has quietly slipped.
Last Done gives the household a shared reference point and frequency adds the expected rhythm.
See how Done When handles thisOne person may vacuum again because they did not know somebody else already handled it, or everybody may assume it was done.
Use an Anyone task so whoever vacuums can record Done and make the latest completion visible to everyone.
See how Done When handles thisMopping is easy to postpone and equally easy to repeat when household members do not share the same memory.
Keep the latest real completion visible and use a recurring frequency to show the expected cadence.
See how Done When handles thisTowels look familiar every day, which makes the last change surprisingly hard to remember.
Track the towel change as a recurring task and keep the latest completion visible at a glance.
See how Done When handles thisA small everyday item can stay in use far longer than intended because its replacement is not memorable.
A recurring task keeps the last replacement date visible and can surface when the task needs attention again.
See how Done When handles thisFridge cleaning often waits until there is an obvious mess because nobody remembers the previous deep clean.
Keep a low-frequency cleaning task with Last Done so the history survives long gaps between cleanings.
See how Done When handles thisOven cleaning may happen every few months, which makes the previous date almost impossible to remember accurately.
Use Last Done as the shared reference and an expected interval when a more exact cadence is useful.
See how Done When handles thisSmall cleaning jobs disappear from attention because they never feel urgent enough to remember.
A recurring task keeps the latest real cleaning visible instead of relying on somebody noticing first.
See how Done When handles thisWindow cleaning happens only a few times a year, so households usually remember the season better than the actual completion.
Use a long-term recurring task so the latest real completion stays available months later.
See how Done When handles thisA deep clean is memorable while it happens but the exact timing disappears after a few weeks.
Record each real completion so the next decision starts from what actually happened rather than an assumed calendar date.
See how Done When handles thisThe bag gets taken out regularly, but cleaning the actual bin is a separate job that is easy to forget.
Track bin cleaning separately so its own Last Done and frequency do not get confused with taking out trash.
See how Done When handles thisLow-frequency jobs where the latest real completion matters more than memory.
Filters, descaling, deep cleaning, and periodic checks happen too infrequently to stay reliably in memory.
Keep the latest completion attached to each maintenance task and use recurrence or frequency as context for the next cycle.
See how Done When handles thisThe filter is out of sight, so replacing it too early or leaving it too long both become easy.
Keep the latest replacement visible and compare it with the expected interval instead of estimating from memory.
See how Done When handles thisWithout the last replacement date, a filter can be changed unnecessarily early or left in place much longer than intended.
Last Done provides the real starting point for deciding whether the filter needs attention again.
See how Done When handles thisSeveral people may use the same purifier while nobody remembers who changed the filter or when.
Keep one shared replacement task with its latest real completion and expected cadence.
See how Done When handles thisDescaling happens infrequently enough that 'recently' can mean a few weeks or several months.
Track the real descaling completion so the next maintenance decision follows the machine's actual history.
See how Done When handles thisThe appliance keeps working every day, so its own cleaning cycle is easy to overlook.
Keep a recurring maintenance task with Last Done and surface it again when it becomes stale.
See how Done When handles thisThe dishwasher is used constantly, but its filter tends to be remembered only after performance gets worse.
Use a recurring task so filter cleaning has a visible completion history before a problem appears.
See how Done When handles thisGrease-filter maintenance is easy to defer because the previous cleaning date is rarely memorable.
Keep the latest completion and recurring cadence attached to the maintenance task.
See how Done When handles thisThe robot remembers to clean the floor, but nobody necessarily remembers brushes, filters, and its own cleaning.
Give the robot's maintenance its own recurring task with a visible Last Done history.
See how Done When handles thisDefrosting may be separated by many months, making the previous completion difficult to place in time.
A long-term task preserves the real completion date instead of asking the household to remember it.
See how Done When handles thisPreventive drain care tends to disappear until there is an obvious problem.
A recurring task keeps preventive maintenance visible and records the latest real cleaning.
See how Done When handles thisA job done every few months is exactly the kind of date people confidently misremember.
Keep the last rotation visible and let the next cycle start from the actual completion.
See how Done When handles thisSeasonal exterior work can quietly skip a cycle when there is no shared record of the last completion.
Track the real cleaning date as a long-term maintenance task that stays visible across seasons.
See how Done When handles thisPreventive checks are easy to lose between people because nothing looks urgent when everything is working.
Use a periodic shared task so the latest check remains visible even when there was nothing notable to report.
See how Done When handles thisBackground appliances run quietly while their cleaning schedule fades out of memory.
Keep the latest real maintenance visible and use frequency to bring the task back into context.
See how Done When handles thisShared routines where everybody needs to know whether care was already handled.
Shared pet care can lead to two opposite mistakes: everybody assumes somebody else did it, or two people do the same routine.
Anyone can mark the task Done, and the household immediately sees when that care was last completed.
See how Done When handles thisIn a shared household, one person can easily miss that somebody else already took the dog out.
Mark the walk Done so everyone can see when the latest walk happened without another message.
See how Done When handles thisOne person may clean it without telling anyone, or everybody may assume somebody else already did.
Use an Anyone task and keep the latest cleaning visible to the whole household.
See how Done When handles thisGrooming happens less often than feeding or walks, so the previous date is easy to lose.
Keep a low-frequency pet-care task with a visible completion history.
See how Done When handles thisAquarium care follows a recurring rhythm but the last maintenance can be difficult to remember across household members.
Use Last Done and frequency to keep the latest real aquarium cleaning visible.
See how Done When handles thisFilter maintenance is separate from visible tank cleaning and can be forgotten even when the aquarium looks fine.
Track the filter as its own recurring task with its own completion history.
See how Done When handles thisAvoid doing the same care twice while still catching work that has been missed.
Plants can be watered twice because nobody knew somebody else did it — or not watered at all because everybody assumed someone had.
An Anyone task makes the latest watering visible before the next person reaches for the watering can.
See how Done When handles thisFertilizing happens in longer intervals than watering, making unnecessary repetition and forgotten cycles both likely.
Keep the latest real fertilizing date and recurring interval in one task.
See how Done When handles thisWhen friends or household members take turns during travel, the next person may not know what was already done.
Use shared completion history so watering and other care remain visible across handoffs.
See how Done When handles thisWeather and travel make lawn care irregular, so a fixed weekly assumption can drift away from reality.
Keep the actual mowing date visible and use frequency as context rather than pretending every week is identical.
See how Done When handles thisOne person can water in the morning and another repeat it later because the first watering was invisible.
Record Done after watering so the latest real care is visible to everyone sharing the garden.
See how Done When handles thisPruning, cleanup, and other seasonal work can be separated by months, making the previous completion hard to remember.
Use a long-term recurring task to keep the real completion history available across seasons.
See how Done When handles thisKeep a shared record when different people visit or maintain the same place.
Different people visit at different times, so nobody knows when the lawn was mowed, a filter was checked, or equipment was inspected.
A separate Household becomes shared memory for the location and keeps the latest real work visible between visits.
See how Done When handles thisThe same set of seasonal jobs returns, but different family members may handle different parts on different visits.
Keep each recurring responsibility in the cottage Household with visible completion status and history.
See how Done When handles thisClosing a second home involves several recurring responsibilities and it is easy to lose which person handled which job.
Use Assigned or Anyone tasks and record real completions so the shared record reflects what was actually done.
See how Done When handles thisThe next visitor may arrive weeks later with no idea what maintenance the previous visitor already completed.
Completion history keeps the place's latest real work visible between visits.
See how Done When handles thisSiblings or co-owners may all help while nobody has one reliable record of the work already completed.
Use a shared Household to keep responsibility and real maintenance completions in one place.
See how Done When handles thisSiblings may help with shopping, garden work, or maintenance at different times without seeing what the others already handled.
A shared Household can keep recurring responsibilities and the latest real completions visible across helpers.
See how Done When handles thisSimple shared status for equipment that several people use or maintain.
Several people use the car, so the last cleaning can feel recent to one person and overdue to another.
Keep a shared Last Done record so the next clean starts from the actual completion rather than memory.
See how Done When handles thisWith a shared car, a simple household action can be duplicated or missed when nobody knows whether somebody already handled it.
Use an Anyone task to make the latest completion visible to the household.
See how Done When handles thisChain care and periodic checks are easy to forget when several people use the same bike.
Track maintenance as a recurring shared task with a visible real completion history.
See how Done When handles thisBattery changes in household devices can be separated by many months and rarely leave a memorable date.
Give each important device a low-frequency maintenance task with Last Done.
See how Done When handles thisWhen several people use the same equipment, nobody has a reliable memory of the last cleaning.
Use Last Done as the shared status so cleaning is not repeated unnecessarily or forgotten.
See how Done When handles thisKeep recurring work in the same app without making it visible to the household.
Some recurring work belongs next to household tasks but should remain personal.
Private Tasks keep the task owner-only while preserving Last Done and recurring context for that person.
See how Done When handles thisTry Done When free, or explore the interactive demo on the home page before creating an account.