SIDE PROJECT
CAT CARE
PROTOTYPE
Feasty’s: Less Guesswork, Happier Bowls
Feasty’s: Less Guesswork, Happier Bowls
A side project for comparing cat foods, remembering meals, and keeping Momo’s care in view.
Explore the walkthrough ↓
Feasty’s interactive prototype · 25-second walkthrough
PROJECT TYPE
Side project · UX/UI concept
MY ROLE
Research, product design, visual design, prototyping
TOOLS
Figma
STATUS
Interactive prototype
INTERACTIVE PROTOTYPE · Survey insights and one informal walkthrough
OVERVIEW
It started in the cat-food aisle.
Standing in PetSmart, I kept researching whether a brand or flavour would suit Momo. At home, my mom and I shared his care without a shared record of his meals.
I started with food comparison, then added meal logging and reminders to connect everyday feeding with the next food decision.
How might we make cat food nutrition easier to understand, so owners can choose meals with confidence?
Cats can be particular about their food, but remembering every meal they enjoyed or refused, is not always easy. Between daily responsibilities and conflicting food advice, owners may have limited time to research each product or keep track of what has worked before.
Cats can be particular about their food, but remembering every meal they enjoyed or refused, is not always easy. Between daily responsibilities and conflicting food advice, owners may have limited time to research each product or keep track of what has worked before.
I wanted to explore how those everyday observations could become more useful. Feasty’s is a concept app where owners can record what their cat eats, note preferences, and compare foods while shopping. It connects feeding history with product information so owners can make decisions with their own cat in mind.
I wanted to explore how those everyday observations could become more useful. Feasty’s is a concept app where owners can record what their cat eats, note preferences, and compare foods while shopping. It connects feeding history with product information so owners can make decisions with their own cat in mind.
The idea is personal to how I think about caring for cats: they cannot tell us what they need in words, but their behaviour gives us something to pay attention to. Feasty’s helps owners remember those observations and bring them into their next decision.
The idea is personal to how I think about caring for cats: they cannot tell us what they need in words, but their behaviour gives us something to pay attention to. Feasty’s helps owners remember those observations and bring them into their next decision.
THE PROBLEM
Buying the food was only part of the problem.
Had Momo tried this food? Did he like it? What had he already eaten? In my household, those answers often lived in someone’s memory. I wanted to learn whether other owners faced similar gaps.
Had Momo tried this food? Did he like it? What had he already eaten? In my household, those answers often lived in someone’s memory. I wanted to learn whether other owners faced similar gaps.
RESEARCH APPROACH
Was I designing for Momo, or for other cat owners too?
I surveyed cat owners to look beyond my own experience and understand how they choose food and manage feeding.
I surveyed cat owners to look beyond my own experience and understand how they choose food and manage feeding.
Initial planning: starting ideas, assumptions to validate, and questions to explore. Click the board to view full size.
First, I asked about the routine.
The survey explored feeding habits, purchasing priorities, and uncertainty around price, ingredients, nutrition, and preferences.
The survey explored feeding habits, purchasing priorities, and uncertainty around price, ingredients, nutrition, and preferences.
Survey Findings
Different homes. Different feeding routines.
Responses revealed different priorities and feeding routines. These are qualitative themes, illustrated by paraphrased responses.
In-store uncertainty
Carolyn described feeling overwhelmed in-store, checking TikTok while balancing deals with confidence in choosing healthy food.
Design direction
Compare prices on a consistent basis and show clear, sourced product information.
Different cat preferences
Sameer explained that their two cats like different foods, making those preferences difficult to remember.
Design direction
Keep likes, refusals, and food history tied to each cat.
Sharing feeding information
Bea found preparing instructions for a sitter overwhelming.
Other responses mentioned family or roommates feeding their cats.
Design direction
Explore a shareable care summary and a record of who last fed the cat.
A useful record shouldn’t become another chore.
Remembering and sharing were closely connected: a cat’s preferences become harder to manage across multiple cats or caregivers.
Routines varied, so reminders are optional. Whether detailed logging is useful still needs testing.
Competitor Review
To understand how cat owners currently manage feeding routines and make food decisions, I reviewed three experiences: 11pets, Compare Cat Foods, and Google Keep. I focused on four key tasks: recording meals, finding dietary preferences, comparing cat foods, and sharing feeding instructions.
To understand how cat owners currently manage feeding routines and make food decisions, I reviewed three experiences: 11pets, Compare Cat Foods, and Google Keep. I focused on four key tasks: recording meals, finding dietary preferences, comparing cat foods, and sharing feeding instructions.
Task-based comparison
| Task | 11pets | Compare Cat Foods | Google Keep |
|---|---|---|---|
| Record a meal | Documented | Not established | Manual notes |
| Keep individual food preferences | Not established | Not established | Manual notes |
| Compare two foods | Not established | Documented | Manual notes |
| Share feeding information | Documented | Not established | Documented |
Documented = provider-confirmed. Manual notes = a possible workaround. Not established = unconfirmed, not necessarily absent. This is a feature comparison, not a usability result. Scroll sideways on smaller screens.
Finding 01 — A broader care app may overlap with existing tools
What I noticed: 11pets covers general pet health and care, including appointments, records, and reminders. For appointment reminders, I would already use my personal calendar.
Why it matters: This raised a question for me: which feeding tasks offer enough value to justify a separate app? My preference for a calendar is a personal observation, not evidence that other owners do not need pet-care tools.
What I’d explore in Feasty’s: Keep the focus on food decisions, each cat’s preferences, and meal history. Make reminders optional rather than the main reason to use the app.
Finding 02 — Start with a simple overview, then offer detail
What I noticed: Compare Cat Foods offers extensive nutrient tables and explanations. I found the amount of information, including dry-matter basis, per-100-kcal, and as-fed values, demanding to interpret during a quick comparison.
The comparison screen I reviewed includes detailed nutrient rows and several unit options. Select the image to view full size.
Why it matters: Someone checking food while shopping might want a simpler starting point. That is a design hypothesis to test, rather than a finding about all users.
What I’d explore in Feasty’s: Start with a short, clearly labelled overview and reveal detailed nutrients and explanations on demand. Keep units and information sources visible.
Finding 03 — Caregiver sharing should be simple
What I observed: Google Keep allows users to quickly create and share editable notes, while 11pets provides more structured pet-care information.
Why it matters: Cat owners need a convenient way to communicate feeding schedules, preferences, and instructions when someone else is caring for their pet.
What I’d explore in Feasty’s: A shareable feeding summary that includes meal times, portions, dietary restrictions, and care instructions.
Key Takeaway
The opportunity I want to explore is a focused food-care experience: a clear comparison overview, food history tied to each cat, and simple caregiver instructions. The next step is to test whether this adds value beyond the tools owners already use.
THE SOLUTION
A food diary, with the next purchase in mind.
Feasty’s now brings three activities into one concept:
Feasty’s now brings three activities into one concept:
Record: Log meals, portions, feeding times, and observations such as whether a cat ate, left, or refused the food.
Remember: Review previous meals and set optional reminders that fit the household’s routine.
Explore: Compare foods using consistent product information alongside the cat’s recorded preferences.
Record: Log meals, portions, feeding times, and observations such as whether a cat ate, left, or refused the food.
Remember: Review previous meals and set optional reminders that fit the household’s routine.
Explore: Compare foods using consistent product information alongside the cat’s recorded preferences.
Momo’s meal history
Log a meal
Food suggestions
Compare foods
INFORMATION ARCHITECTURE
Giving each part of the routine a place.
I grouped the experience around three activities: daily feeding in Today, food research in Food Explorer, and individual preferences and history in My Cats.
I grouped the experience around three activities: daily feeding in Today, food research in Food Explorer, and individual preferences and history in My Cats.
The prototype uses Discover for Food Explorer. Aligning these labels is part of the next refinement.
The prototype uses Discover for Food Explorer. Aligning these labels is part of the next refinement.
User Flows
I mapped out the key journeys of Feasty’s to understand how cat owners would navigate between food discovery, comparison, and meal tracking.
I focused on making everyday actions quick and intuitive, particularly for owners checking products while shopping or logging meals at home. These flows helped me identify opportunities to reduce unnecessary steps, provide alternative paths when information is unavailable, and connect food recommendations with each cat’s dietary history.
Proposed journeys, including paths beyond the current prototype. Select a diagram to view full size.
01 / Scan & compare cat food
02 / Personalized onboarding
03 / Log a meal
KEY DESIGN DECISIONS
The choices behind the screens.
1. What happened today?
Momo’s name, photo, meal entries, and next reminder keep the daily context visible. Owners can recognize recorded information rather than rely on memory.
Momo’s name, photo, meal entries, and next reminder keep the daily context visible. Owners can recognize recorded information rather than rely on memory.
Daily dashboard
1
2
3
1. The overview labels amounts served rather than a recommended daily target.
2. The upcoming feeding reminder sits alongside the daily meal record.
3. The orange floating add button makes recording the next meal easy to find.
2. Enjoyed it… but left some.
Liking a food and finishing it are different observations. Separate selections record enjoyment and leftovers without treating one as a substitute for the other.
Liking a food and finishing it are different observations. Separate selections record enjoyment and leftovers without treating one as a substitute for the other.
Logging a meal
1
2
3
1. Amount and unit are separate, explicit fields.
2. Enjoyment and leftovers are recorded independently.
3. A prominent Save meal action completes the task.
3. One task at a time.
A white task card beneath the purple header separates setup controls from context. Profile and reminder flows share this structure.
A white task card beneath the purple header separates setup controls from context. Profile and reminder flows share this structure.
A focused space for reminder setup
1. A white task card separates reminder settings from the purple contextual header. 2. The Repeat setting makes the recurring schedule visible before saving.
4. Two foods. A clearer basis for comparison.
Side-by-side charts use consistent product colours, visible values, and labelled units. Each nutrient has its own scale; testing will check whether owners interpret the comparison correctly.
Side-by-side charts use consistent product colours, visible values, and labelled units. Each nutrient has its own scale; testing will check whether owners interpret the comparison correctly.
The example values are marked as fictional prototype data.
The example values are marked as fictional prototype data.
Comparing two foods
1
2
3
1. The header labels the values as fictional demo data.
2. Purple and orange identify the two products consistently.
3. Each nutrient has its own labelled unit and chart scale.
5. A preference match isn’t a health recommendation.
Preferences describe what a cat has liked; reviews describe other owners’ experiences. Neither establishes medical suitability, so preference matches need to remain distinct from veterinary guidance.
Preferences describe what a cat has liked; reviews describe other owners’ experiences. Neither establishes medical suitability, so preference matches need to remain distinct from veterinary guidance.
Preference-based discovery
1
2
3
1. Preference chips keep the discovery context visible.
2. Compare two foods is separate from browsing suggestions.
3. Each recommendation shows a preference match; it is not a medical suitability claim.
VISUAL DESIGN
A little playful. Still easy to read.
Purple gradients and playful headings give Feasty’s personality. White cards keep forms and details distinct; orange highlights key actions and selected navigation.
Purple gradients and playful headings give Feasty’s personality. White cards keep forms and details distinct; orange highlights key actions and selected navigation.
Simpler text supports forms and nutrition details. The stylesheet below documents the visual system.
Simpler text supports forms and nutrition details. The stylesheet below documents the visual system.
PROTOTYPE AND EVALUATION
Here’s how it fits together.
The Figma prototype connects profile creation, meal logging, reminders, discovery, and food comparison.
The Figma prototype connects profile creation, meal logging, reminders, discovery, and food comparison.
This is an interactive concept; live notifications and data storage are not implemented.
This is an interactive concept; live notifications and data storage are not implemented.
A first walkthrough: familiar, with gaps to resolve.
A first walkthrough: familiar, with gaps to resolve.
I asked one person to explore the Figma prototype and talk through their thoughts. These are early observations, not a measure of task success.
Navigation came first
They checked the bottom navigation first to understand what each section did.
A familiar concept
They compared Feasty’s to MyFitnessPal for cats and liked being able to review previous days.
Unfinished paths
They tried clicking elements I had not connected yet, revealing paths to complete before the next walkthrough.
NEXT STEPS
Test the routine, then refine.
Connect the unfinished paths, then ask cat owners to log a meal and review a previous day. Observe hesitation and label interpretation before making revisions.
Connect the unfinished paths, then ask cat owners to log a meal and review a previous day. Observe hesitation and label interpretation before making revisions.
REFLECTION
A project about cats became a project about remembering.
The biggest lesson has been precision: served is not eaten, enjoyment is not an empty bowl, and a preference match is not medical guidance.
The biggest lesson has been precision: served is not eaten, enjoyment is not an empty bowl, and a preference match is not medical guidance.
Feasty’s began with me and Momo. Next, I want to learn whether it earns a place in someone else’s routine.
Feasty’s began with me and Momo. Next, I want to learn whether it earns a place in someone else’s routine.
SIDE PROJECT
CAT CARE
PROTOTYPE
Feasty’s: Less Guesswork, Happier Bowls
A side project for comparing cat foods, remembering meals, and keeping Momo’s care in view.
Explore the walkthrough ↓
Feasty’s interactive prototype · 25-second walkthrough
PROJECT TYPE
Side project · UX/UI concept
MY ROLE
Research, product design, visual design, prototyping
TOOLS
Figma
STATUS
Interactive prototype
INTERACTIVE PROTOTYPE · Survey insights and one informal walkthrough
OVERVIEW
It started in the cat-food aisle.
Standing in PetSmart, I kept researching whether a brand or flavour would suit Momo. At home, my mom and I shared his care without a shared record of his meals.
I started with food comparison, then added meal logging and reminders to connect everyday feeding with the next food decision.
How might we make cat food nutrition easier to understand, so owners can choose meals with confidence?
Cats can be particular about their food, but remembering every meal they enjoyed or refused, is not always easy. Between daily responsibilities and conflicting food advice, owners may have limited time to research each product or keep track of what has worked before.
I wanted to explore how those everyday observations could become more useful. Feasty’s is a concept app where owners can record what their cat eats, note preferences, and compare foods while shopping. It connects feeding history with product information so owners can make decisions with their own cat in mind.
The idea is personal to how I think about caring for cats: they cannot tell us what they need in words, but their behaviour gives us something to pay attention to. Feasty’s helps owners remember those observations and bring them into their next decision.
THE PROBLEM
Buying the food was only part of the problem.
Had Momo tried this food? Did he like it? What had he already eaten? In my household, those answers often lived in someone’s memory. I wanted to learn whether other owners faced similar gaps.
RESEARCH APPROACH
Was I designing for Momo, or for other cat owners too?
I surveyed cat owners to look beyond my own experience and understand how they choose food and manage feeding.
Initial planning: starting ideas, assumptions to validate, and questions to explore. Click the board to view full size.
First, I asked about the routine.
The survey explored feeding habits, purchasing priorities, and uncertainty around price, ingredients, nutrition, and preferences.
Survey Findings
Different homes. Different feeding routines.
Responses revealed different priorities and feeding routines. These are qualitative themes, illustrated by paraphrased responses.
In-store uncertainty
Carolyn described feeling overwhelmed in-store, checking TikTok while balancing deals with confidence in choosing healthy food.
Design direction
Compare prices on a consistent basis and show clear, sourced product information.
Different cat preferences
Sameer explained that their two cats like different foods, making those preferences difficult to remember.
Design direction
Keep likes, refusals, and food history tied to each cat.
Sharing feeding information
Bea found preparing instructions for a sitter overwhelming.
Other responses mentioned family or roommates feeding their cats.
Design direction
Explore a shareable care summary and a record of who last fed the cat.
A useful record shouldn’t become another chore.
Remembering and sharing were closely connected: a cat’s preferences become harder to manage across multiple cats or caregivers.
Routines varied, so reminders are optional. Whether detailed logging is useful still needs testing.
Competitor Review
To understand how cat owners currently manage feeding routines and make food decisions, I reviewed three experiences: 11pets, Compare Cat Foods, and Google Keep. I focused on four key tasks: recording meals, finding dietary preferences, comparing cat foods, and sharing feeding instructions.
Task-based comparison
| Task | 11pets | Compare Cat Foods | Google Keep |
|---|---|---|---|
| Record a meal | Documented | Not established | Manual notes |
| Keep individual food preferences | Not established | Not established | Manual notes |
| Compare two foods | Not established | Documented | Manual notes |
| Share feeding information | Documented | Not established | Documented |
Documented = provider-confirmed. Manual notes = a possible workaround. Not established = unconfirmed, not necessarily absent. This is a feature comparison, not a usability result. Scroll sideways on smaller screens.
Finding 01 — A broader care app may overlap with existing tools
What I noticed: 11pets covers general pet health and care, including appointments, records, and reminders. For appointment reminders, I would already use my personal calendar.
Why it matters: This raised a question for me: which feeding tasks offer enough value to justify a separate app? My preference for a calendar is a personal observation, not evidence that other owners do not need pet-care tools.
What I’d explore in Feasty’s: Keep the focus on food decisions, each cat’s preferences, and meal history. Make reminders optional rather than the main reason to use the app.
Finding 02 — Start with a simple overview, then offer detail
What I noticed: Compare Cat Foods offers extensive nutrient tables and explanations. I found the amount of information, including dry-matter basis, per-100-kcal, and as-fed values, demanding to interpret during a quick comparison.
The comparison screen I reviewed includes detailed nutrient rows and several unit options. Select the image to view full size.
Why it matters: Someone checking food while shopping might want a simpler starting point. That is a design hypothesis to test, rather than a finding about all users.
What I’d explore in Feasty’s: Start with a short, clearly labelled overview and reveal detailed nutrients and explanations on demand. Keep units and information sources visible.
Finding 03 — Caregiver sharing should be simple
What I observed: Google Keep allows users to quickly create and share editable notes, while 11pets provides more structured pet-care information.
Why it matters: Cat owners need a convenient way to communicate feeding schedules, preferences, and instructions when someone else is caring for their pet.
What I’d explore in Feasty’s: A shareable feeding summary that includes meal times, portions, dietary restrictions, and care instructions.
Key Takeaway
The opportunity I want to explore is a focused food-care experience: a clear comparison overview, food history tied to each cat, and simple caregiver instructions. The next step is to test whether this adds value beyond the tools owners already use.
THE SOLUTION
A food diary, with the next purchase in mind.
Feasty’s now brings three activities into one concept:
Record: Log meals, portions, feeding times, and observations such as whether a cat ate, left, or refused the food.
Remember: Review previous meals and set optional reminders that fit the household’s routine.
Explore: Compare foods using consistent product information alongside the cat’s recorded preferences.
Momo’s meal history
Log a meal
Food suggestions
Compare foods
INFORMATION ARCHITECTURE
Giving each part of the routine a place.
I grouped the experience around three activities: daily feeding in Today, food research in Food Explorer, and individual preferences and history in My Cats.
The prototype uses Discover for Food Explorer. Aligning these labels is part of the next refinement.
User Flows
I mapped out the key journeys of Feasty’s to understand how cat owners would navigate between food discovery, comparison, and meal tracking.
I focused on making everyday actions quick and intuitive, particularly for owners checking products while shopping or logging meals at home. These flows helped me identify opportunities to reduce unnecessary steps, provide alternative paths when information is unavailable, and connect food recommendations with each cat’s dietary history.
Proposed journeys, including paths beyond the current prototype. Select a diagram to view full size.
01 / Scan & compare cat food
02 / Personalized onboarding
03 / Log a meal
KEY DESIGN DECISIONS
The choices behind the screens.
1. What happened today?
Momo’s name, photo, meal entries, and next reminder keep the daily context visible. Owners can recognize recorded information rather than rely on memory.
Daily dashboard
1
2
3
1. The overview labels amounts served rather than a recommended daily target.
2. The upcoming feeding reminder sits alongside the daily meal record.
3. The orange floating add button makes recording the next meal easy to find.
2. Enjoyed it… but left some.
Liking a food and finishing it are different observations. Separate selections record enjoyment and leftovers without treating one as a substitute for the other.
Logging a meal
1
2
3
1. Amount and unit are separate, explicit fields.
2. Enjoyment and leftovers are recorded independently.
3. A prominent Save meal action completes the task.
3. One task at a time.
A white task card beneath the purple header separates setup controls from context. Profile and reminder flows share this structure.
A focused space for reminder setup
1. A white task card separates reminder settings from the purple contextual header. 2. The Repeat setting makes the recurring schedule visible before saving.
4. Two foods. A clearer basis for comparison.
Side-by-side charts use consistent product colours, visible values, and labelled units. Each nutrient has its own scale; testing will check whether owners interpret the comparison correctly.
The example values are marked as fictional prototype data.
Comparing two foods
1
2
3
1. The header labels the values as fictional demo data.
2. Purple and orange identify the two products consistently.
3. Each nutrient has its own labelled unit and chart scale.
5. A preference match isn’t a health recommendation.
Preferences describe what a cat has liked; reviews describe other owners’ experiences. Neither establishes medical suitability, so preference matches need to remain distinct from veterinary guidance.
Preference-based discovery
1
2
3
1. Preference chips keep the discovery context visible.
2. Compare two foods is separate from browsing suggestions.
3. Each recommendation shows a preference match; it is not a medical suitability claim.
VISUAL DESIGN
A little playful. Still easy to read.
Purple gradients and playful headings give Feasty’s personality. White cards keep forms and details distinct; orange highlights key actions and selected navigation.
Simpler text supports forms and nutrition details. The stylesheet below documents the visual system.
PROTOTYPE AND EVALUATION
Here’s how it fits together.
The Figma prototype connects profile creation, meal logging, reminders, discovery, and food comparison.
This is an interactive concept; live notifications and data storage are not implemented.
A first walkthrough: familiar, with gaps to resolve.
I asked one person to explore the Figma prototype and talk through their thoughts. These are early observations, not a measure of task success.
Navigation came first
They checked the bottom navigation first to understand what each section did.
A familiar concept
They compared Feasty’s to MyFitnessPal for cats and liked being able to review previous days.
Unfinished paths
They tried clicking elements I had not connected yet, revealing paths to complete before the next walkthrough.
NEXT STEPS
Test the routine, then refine.
Connect the unfinished paths, then ask cat owners to log a meal and review a previous day. Observe hesitation and label interpretation before making revisions.
REFLECTION
A project about cats became a project about remembering.
The biggest lesson has been precision: served is not eaten, enjoyment is not an empty bowl, and a preference match is not medical guidance.
Feasty’s began with me and Momo. Next, I want to learn whether it earns a place in someone else’s routine.