An Android application that helps people living together organize household responsibilities through shared, visible agreements.
● Product in developmentProduct in development
Household chores are simple individually but surprisingly difficult to coordinate. The problem is often not knowing that something needs to be done, but knowing who is responsible, when it should happen, whether it is complete, and whether the workload is balanced.
When agreements remain implicit, people can develop very different perceptions of how responsibilities are being shared.
I did not want to design another generic to-do list. Household tasks repeat, can be completed by different people, and need to adapt when someone is away or plans change.
Most importantly, the product should help coordination without making the home feel like a workplace dashboard.
How might we make household responsibilities easier to coordinate while keeping the experience collaborative rather than punitive?
The first major decision was to make the home the central object instead of the individual user. A user can create a household and invite members with different levels of access, including guests and registered users.
This reflects the reality that a home can include people with different levels of technical involvement.
A simple checkbox was not enough. Recurring chores may need to be skipped, moved, archived, or temporarily paused.
The system preserves the relationship between the original responsibility and each occurrence, maintaining history without recreating the same task manually.
The application shows who completed a task without turning every interaction into a competition. Members can record completion and, when needed, mark that another person completed it.
Points and lightweight gamification support motivation, but the main goal remains visibility: what needs attention, who is involved, and what has already been done.
Household routines are rarely perfect, so edge cases became part of the main experience rather than afterthoughts.
Because the product is mobile, connectivity cannot always be assumed. I explored how actions should behave offline and synchronize once connectivity returns.
This raised product questions about simultaneous completions, update priority, and how the interface communicates pending synchronization.
What should happen when two people complete the same chore from different devices?
I tested whether the household model and recurring task system were understandable, then refined information hierarchy and reduced ambiguity around task states.
Mitad y Mitad became a mobile system for coordinating shared responsibilities rather than simply recording tasks. Its core value comes from making agreements visible.
Households can manage members, recurring chores, task history, and completion while supporting the unpredictability of real routines.
Recurrence, synchronization, and shared ownership introduce significant product complexity.
Small wording choices can make an interface feel cooperative or accusatory.
Vacations, skipped chores, and simultaneous actions are normal parts of household life.
Recurring schedules and offline synchronization connect interface behavior to the data model.
Screens from the product, covering its main flows and interface details.