MeowMinder
Turning fragmented pet care into one shared household system
MeowMinder started as a concept for a social pet app, but research showed that users did not want another place to share photos. They needed one reliable system to manage feeding, reminders, health records, and household responsibilities.
This project pivoted from social sharing to a private, utility-first care ecosystem designed to reduce cognitive load and support both daily coordination and long-term pet health
MeowMinder
Turning fragmented pet care into one shared household system
MeowMinder started as a concept for a social pet app, but research showed that users did not want another place to share photos. They needed one reliable system to manage feeding, reminders, health records, and household responsibilities.
This project pivoted from social sharing to a private, utility-first care ecosystem designed to reduce cognitive load and support both daily coordination and long-term pet health.
Role: UX/UI Designer, researcher, information architect, prototyper.
Scope: Research, synthesis, product strategy, IA, wireframes, usability testing, and iteration.
Goal: Replace fragmented pet care tools with one clear system.
Outcome: A Health Hub and household coordination experience built around real user needs.
The problem
Cat owners cared deeply about their pets, but their care routines were fragmented. Important information lived in memory, paper vet booklets, chats, and household notes, which increased cognitive load and created obvious failure points like missed vaccinations or accidental double-feeding.
The real issue was not engagement. It was coordination. People were managing recurring care tasks with tools that were never designed to support shared responsibility or long-term memory.
Research
To test the original concept, I ran moderated interviews, surveys, and card sorting. The goal was to understand current habits, uncover unmet needs, and map how users naturally organized pet care information.
The clearest insight was that users did not want another public feed. They already had Instagram and WhatsApp for sharing. What they lacked was a private, practical tool that helped them remember, organize, and coordinate care.
Strategic Pivot
That insight invalidated the original assumption. Instead of designing around social sharing, I pivoted the product toward utility: a private system for feeding, reminders, medical history, and shared household coordination.
This was the key product decision of the project. It transformed MeowMinder from a concept app into a meaningful care ecosystem with clearer value and stronger retention potential.
"Users do not want another public feed; they require a private, utilitarian log for medical history and chronological memories."
Personas
I translated the research into two behavioral archetypes. Kate represented a busy owner trying to stay on top of daily care, while Diana represented a more detail-oriented pet parent focused on health tracking and preventive routines.
These personas showed that the product needed to support both fast daily actions and structured long-term record-keeping.
Product Strategy
I repositioned MeowMinder as a household pet management ecosystem. The product strategy had two layers of value: frequent engagement through shared chores and reminders, and long-term retention through centralized medical history and care records.
That made the product more useful and more defensible. A shared care log drives recurring use, while accumulated health history increases switching costs over time.
Design Direction
The interface was designed for clarity, not novelty. Instead of emphasizing social activity, I prioritized fast access to tasks, health data, reminders, and coordination between household members.
This shaped both the information architecture and the visual tone of the product. The result feels less like a lifestyle app and more like a dependable care companion.
Testing and Iteration
I tested the experience in Maze and Zoom. Usability testing revealed three major issues: navigational bloat, false affordances, and confusing naming.
I used those findings to simplify navigation, improve labels, and refine interaction patterns so the product matched user expectations more closely.
Final Solution
The final concept centered on a unified Health Hub inside a broader household care system. Users could manage reminders, records, and responsibilities in one place instead of relying on scattered tools.
The strongest part of the solution is not just the UI. It is the logic behind it: the product now reflects observed behavior, supports both short-term and long-term needs, and solves a real coordination problem.
Outcome
The most important outcome of the project was strategic. Research invalidated the original concept and led to a more useful product direction, showing that the design process was driven by evidence rather than assumptions.
Even without quantitative metrics, the case shows mature UX thinking: identifying the wrong premise, reframing the opportunity, and improving the solution through testing and iteration.
Link to the Prototype : https://www.figma.com/proto/zplaYzdW98tcaGI6e6QPp7/MeowMinder?node-id=273-4082&starting-point-node-id=273%3A4082&t=ZuYkzkvzZ774P8UG-1
Reflection
This project reinforced a simple lesson: a strong concept is not the same as a real user need. The most valuable decision was not visual polish, but the willingness to pivot when research showed the original direction was wrong.
It also strengthened the importance of clear naming, simple navigation, and system-level thinking in product design.
Role: UX/UI Designer, researcher, information architect, prototyper.
Scope: Research, synthesis, product strategy, IA, wireframes, usability testing, and iteration.
Goal: Replace fragmented pet care tools with one clear system.
Outcome: A Health Hub and household coordination experience built around real user needs.
The problem
Cat owners cared deeply about their pets, but their care routines were fragmented. Important information lived in memory, paper vet booklets, chats, and household notes, which increased cognitive load and created obvious failure points like missed vaccinations or accidental double-feeding.
The real issue was not engagement. It was coordination. People were managing recurring care tasks with tools that were never designed to support shared responsibility or long-term memory.
Research
To test the original concept, I ran moderated interviews, surveys, and card sorting. The goal was to understand current habits, uncover unmet needs, and map how users naturally organized pet care information.
The clearest insight was that users did not want another public feed. They already had Instagram and WhatsApp for sharing. What they lacked was a private, practical tool that helped them remember, organize, and coordinate care.
Strategic Pivot
That insight invalidated the original assumption. Instead of designing around social sharing, I pivoted the product toward utility: a private system for feeding, reminders, medical history, and shared household coordination.
This was the key product decision of the project. It transformed MeowMinder from a concept app into a meaningful care ecosystem with clearer value and stronger retention potential.
"Users do not want another public feed; they require a private, utilitarian log for medical history and chronological memories."
Personas
I translated the research into two behavioral archetypes. Kate represented a busy owner trying to stay on top of daily care, while Diana represented a more detail-oriented pet parent focused on health tracking and preventive routines.
These personas showed that the product needed to support both fast daily actions and structured long-term record-keeping.
Product Strategy
I repositioned MeowMinder as a household pet management ecosystem. The product strategy had two layers of value: frequent engagement through shared chores and reminders, and long-term retention through centralized medical history and care records.
That made the product more useful and more defensible. A shared care log drives recurring use, while accumulated health history increases switching costs over time.
Design Direction
The interface was designed for clarity, not novelty. Instead of emphasizing social activity, I prioritized fast access to tasks, health data, reminders, and coordination between household members.
This shaped both the information architecture and the visual tone of the product. The result feels less like a lifestyle app and more like a dependable care companion.
Testing and Iteration
I tested the experience in Maze and Zoom. Usability testing revealed three major issues: navigational bloat, false affordances, and confusing naming.
I used those findings to simplify navigation, improve labels, and refine interaction patterns so the product matched user expectations more closely.
Final Solution
The final concept centered on a unified Health Hub inside a broader household care system. Users could manage reminders, records, and responsibilities in one place instead of relying on scattered tools.
The strongest part of the solution is not just the UI. It is the logic behind it: the product now reflects observed behavior, supports both short-term and long-term needs, and solves a real coordination problem.
Outcome
The most important outcome of the project was strategic. Research invalidated the original concept and led to a more useful product direction, showing that the design process was driven by evidence rather than assumptions.
Even without quantitative metrics, the case shows mature UX thinking: identifying the wrong premise, reframing the opportunity, and improving the solution through testing and iteration.
Link to the Prototype : https://www.figma.com/proto/zplaYzdW98tcaGI6e6QPp7/MeowMinder?node-id=273-4082&starting-point-node-id=273%3A4082&t=ZuYkzkvzZ774P8UG-1
Reflection
This project reinforced a simple lesson: a strong concept is not the same as a real user need. The most valuable decision was not visual polish, but the willingness to pivot when research showed the original direction was wrong.
It also strengthened the importance of clear naming, simple navigation, and system-level thinking in product design.