©2026 Darnell Wilbrink. All Rights Reserved.

Purrflow
<— Back to Projects

What's this about?
PurrFlow is a smart cat feeder app built for WeAreReasonablePeople. The idea is that cat owners can feed their pet remotely and check in on them even when they're not home. Think feeding schedules, a live camera, and voice recordings so you can call your cat from wherever you are.
I worked on the profiles and access sharing section, which lets users create their own account and share access with family or friends so others can help take care of the cat when needed.
Our goal
"Design an app that's both practical and reassuring for cat owners — simple, fast, and without any unnecessary screens or pop-ups."
The problem
·Cat owners can't always be home to feed or check on their pet
·Sharing care with others is awkward without a dedicated system
·Most pet apps are cluttered or confusing
·No easy way to hand off access without losing control
What we were aiming for
·A clean, calm app that works without any explanation needed
·Flexible profile and access management built around trust
·Soft, friendly visual style for the 20 to 40 year old target audience
·No unnecessary steps, just the essentials done well
Design requirements
The brief gave us clear constraints, and as a team we added a few of our own. Here's the visual identity we landed on.
Soft visual style
A warm green and pink palette, paw-print patterns and subtle textures. Professional but with a playful edge to match the audience.
Simple and fast
No unnecessary screens. The app had to work without an instruction manual for any level of tech familiarity.
Functional first
Feeding schedules, live camera, voice recordings. Every feature had to serve a real need for the owner.
Profiles and access
My focus. Users can create profiles, share access with others, and assign roles like Owner, Admin or Viewer.
What we ended up building
A clean, accessible cat care app with a warm visual identity. Here are the main screens I worked on.
Honestly, what did I think?
Choosing profiles and access sharing as my focus was a good call. It looks simple from the outside but has a lot of edge cases once you get into it. Who controls what? What if someone shares access and then wants to revoke it? These questions kept the work interesting.
The target audience shift early on was a useful reminder that your first assumption isn't always right. Going from elderly users to working 20-40 year olds changed almost every design decision, from the tone of the copy to how much we could assume people already knew.
I found the soft visual style a nice change of pace. Working with a warmer, friendlier palette pushed me to be more intentional about where I used colour and why. It's easy to default to something neutral, harder to make something actually feel nice.
If I did it again, I'd push to test the access sharing flow earlier. We got useful feedback in round 3, but that was almost too late to make big changes. Testing rough flows sooner would have saved us some rework at the end.
Pick a focused feature
Working on one specific part lets you go deep and think through the edge cases properly.
Test early, test often
Waiting until round 3 to test the access sharing flow was a mistake. Earlier feedback would have helped.
Audience shapes everything
Shifting from elderly to working adults completely changed the design direction. Challenge your first assumption.
Visual style is a decision
The soft palette wasn't just aesthetic. It shaped the tone of the whole app and how trustworthy it felt.
Where could this go?
PurrFlow has a solid base. Here's what would make it even better.
Better consistency between screens, especially buttons and spacing
A proper walkthrough or tutorial for first-time users
Accessibility improvements like larger tap targets and voice control
Handle edge cases in access sharing, like temporary or limited access
Clearer homepage, it still felt a bit flat in testing
Better onboarding for adding devices, the flow could be more guided
Look at other apps for inspiration on cleaner navigation patterns
More user testing with the actual target group, not just fellow students