¿Dónde Está?

2025 · UX/UI Designer

The app that brings animals and families back together.

UX/UI
MOBILE APP
PRODUCT DESIGN

Swipe sideways or use the arrows

Context

Scattered information, missed reunions

What I did

I proposed a native Android app, designed end to end, as a help network where people post a lost or found pet in the moment. Argentina had no centralized, community-driven and accessible app for this.

Why

Plenty of people are willing to help, but the information stays scattered across posters and isolated posts that almost never reach the people who need to see them. Without one shared place to post and search, chances of reunion are lost.

Illustration of a person worried about a lost pet

Research

The voice of people living the problem

What I did

I combined qualitative interviews, two user personas validated with them, a point of view and a benchmark of four animal rescue apps and websites.

Why

I wanted to understand the motivations, frustrations and needs of people who lose or find an animal before designing, and see what other rescue apps already solve.

What I found

The frustrations repeat: information gets lost in stories or unclear posts, current apps are confusing or full of ads, and cases get little reach. The references fall short too: exposed privacy on the map, geolocation that doesn’t work, regional reach only, or services that are no longer active.

Scope

The essentials first

What I did

I defined an MVP and sorted the remaining features with MoSCoW: what the app must, should and could have.

Why

I was after a minimum core that would fulfill the main purpose, posting and locating lost animals, without loading the first version with everything else.

What I found

The MVP came down to five features: a post feed, posting an animal with photo and details, a geolocated map, search and filters, and proximity alerts. Profile, guides, contact, shelters and automatic matches were left for later.

Structure

People’s mental model shapes the app

What I did

I set up a card sort with 19 features and six sections. From it I defined the information architecture, two task flows (lost and found pet) and the user flow for the happy paths.

Why

The idea was for the app to follow how people grouped its features, and for every path, from signing in to posting or searching for an animal, to have a clear next step.

What I found

Posting permissions, sharing, alerts, match notifications and contacting the admins had no clear place: people saw them as cross-cutting actions. So I merged Home with Community. After the usability tests, the architecture settled into six sections: Login, Home + Community, Post an animal, Geolocation, Profile, and Resources and help.

View how people move through the app

Task flow · Someone who lost a pet

Opens the app and signs in (or signs up the first time).
Goes to “Report lost animal”.
Fills in the form: photo, type, description, date and time it went missing, and the place on the map.
Confirms the post.
Sees the published report and shares it on social media.

Task flow · Someone who found a pet

Opens the app and signs in (or signs up the first time).
Goes to “Report found animal”.
Fills in the form: photo, type, physical traits, observed behavior, location and contact details.
Confirms the post.
Sees the published report and shares it on social media.

User flow · From the home screen

Community: nearby posts, comments and chat through animal connection.
Post an animal: report a lost or found animal, or mark a reunion; then follow the case and share it.
Map: nearby reports, shelters and vets.
Profile: my posts, my pets and settings.
Resources and help: guides, tutorials and contact with support.

Design

From sketch to a prototype with its own identity

What I did

I went from hand sketches to low- and mid-fidelity wireframes for the report-posting flow, and from there to a high-fidelity working prototype, with a moodboard and a UI Kit based on Material Design.

Why

The goal was to validate structure and navigation before adding detail, and to reach a friendly, empathetic identity with a coherent system that would make implementation easier.

From sketch to high fidelity

Hand sketches. Quick paper sketches of the four screens in the report-posting flow.
Low fidelity. Digital wireframes to validate structure and navigation.
Mid fidelity. Hierarchy and flow refined, closer to the real experience.
High fidelity. The working prototype, with its identity and UI Kit, used in the usability tests.

1 / 4

Tap each level or swipe to compare

Notification and chat screens of the prototype, in perspective

Validation

What worked and what didn’t

What I did

I tested the prototype with two usability tests: finding a cat’s owner and reporting a lost animal. I measured success rate, misclicks, steps, an opinion scale and hotspots.

Why

I needed to tell whether people completed each task or only managed it with effort.

What I found

People complete the tasks, but high misclicks point to confusion: unclear buttons or too many options on screen. In test 2 the path isn’t linear, and the form needs to be filled step by step. Next steps: clarify buttons and labels, reduce visible options, streamline the test 2 flow and test again.

Results

Test 1 · Finding a cat’s owner

100%

Completed the task
Misclicks before reaching the solution53%
Overall perception8.4 / 10