Finding a Rescue Pet Without Tracking the Adopter
Imagine looking for a rescue cat from your kitchen table in Petaling Jaya. You want to browse pets in a city you can travel to. Does the app need your phone's location, or could you just tell it which city to use?
We chose the latter for Pawmi, our rescue pet adoption app for Malaysia. It orders the feed by the city on your profile, without requesting location permission or collecting device location.
Pawmi is not run for profit. It exists to help rescue animals find homes, with no ads, donations or payments inside the app. For us, it is a useful example of designing around a specific task rather than collecting data simply because a phone can supply it.
Use the city someone chooses, not the phone's position
“Near you” needs an explanation. In Pawmi, it means the city the person types into their profile. It does not mean a live GPS position, a distance measured from their kitchen or background location tracking.
That distinction belongs beside “near you”, not in a footnote. Our product page spells it out: “No location tracking — just the city you choose.” We mean device location here, not that the app holds no personal information. The city and household details someone supplies are a separate consideration.
The trade-off is worth explaining. A feed ordered by city is not a list of pets ranked by exact distance from your door. It uses the area you have chosen. If a proposed feature needs a precise position, we would ask for a separate justification; “nearby” alone would not be enough.
For another public-service app, write the question before choosing the permission. Does the service need the person's position right now, or an area they are willing to visit? Do not treat those as interchangeable requirements.
Explain the match without pretending to make the decision
Pawmi's PawMatch asks about your home, energy and household. It suggests pets based on those answers, with reasons rather than just a number.
The explanation matters more to us than a score. It gives someone a starting point for a conversation with the rescue: does this reason reflect their household? We would rather help them ask that question than make the result screen sound certain about a decision it cannot make for them.
We describe PawMatch as a questionnaire with explained suggestions, not automatic approval. A match should not be read as a prediction of how an animal will settle into a particular home.
If you are commissioning a matching tool, ask the builder to demonstrate the explanation, not only the ranked list. Can someone understand why an option appeared? Which question should they revisit if the reason does not describe their circumstances?
Keep the rescue visible behind the listing
Every Pawmi listing belongs to a rescue organisation with its own profile. Pet details include photos, age, breed, weight and temperament, alongside information about what living with that pet is like. Applicants can message the rescue directly.
We want those details to help someone ask about the animal, not make adoption feel like a checkout. Saving a pet that catches your eye is a useful first step; it should not imply that suitability has been settled.
When reviewing a similar app, we would follow one question from the pet page into a conversation. Could this cat live with another pet, for example? Can the applicant identify the rescue they are asking and refer back to the listing while discussing the answer?
A rescue profile shows which organisation the listing belongs to. That is not evidence that every statement has been independently checked. We would keep the route to a conversation visible rather than expect a badge or photograph to answer every concern.
Show what happens after the application is submitted
Pawmi lets someone apply inside the app and follow the application through named stages: submitted, under review, shortlisted, meet and greet, home check, approved, agreement and adopted.
The useful detail is the distinction between those stages. An application being received is not the same as being approved. A meeting is not the completed adoption. We would keep that difference visible rather than compress the whole process into a reassuring tick.
For a similar build, we would ask who can move an application forward and what the applicant should see when nothing has changed. We would also ask how a correction or withdrawal should work. Those questions belong in the scope; the stage list alone does not answer them.
One limit matters here: Pawmi has no push notifications. Updates are in-app only, so applicants need to look in the app rather than wait for a phone alert. We would keep that clear in the copy, even if “instant alerts” sounds more appealing.
Leave room for reporting and leaving
Pawmi includes reporting for listings and messages, and a way to block someone. Users can also start account deletion inside the app without contacting us.
These are useful controls, not a guarantee of safety or a complete explanation of data handling. For a similar service, we would ask who receives reports and what happens next. Account-deletion wording would also need to explain what is removed and any retention that applies, rather than leave people to guess.
For an acceptance review, we would ask to see the controls from the place where someone needs them. Start with a listing, then a conversation. Find the report action. Find block. Separately, walk through the account-deletion path and check that its wording explains the action before confirmation.
Include those paths in the demonstration before approving a build. Browsing may be easier to show in a presentation, but reporting and leaving deserve just as much attention.
Give the app a job after the pet comes home
Pawmi also includes a diary for photos and moments, vaccination and vet-visit tracking, and first-week tasks to help a new pet settle in.
That gives the app a purpose beyond the application. We would describe these as record-keeping and settling-in tools, not veterinary advice or evidence that an adoption will succeed. A diary should earn its place by helping the adopter, not by making our feature list longer.
For a public-service project, mark where the main task appears to end. Would a modest follow-up tool help the person more than another browsing feature? In an adoption app, keeping a vet-visit record is a specific task to consider. “More engagement” is not a sufficient brief on its own.
Our mobile app and custom software services cover this kind of work. Before discussing a build, bring one user journey. Mark where information is requested and which decisions need a person. Our local-first app article explores a different privacy choice: avoiding device location does not mean avoiding accounts or keeping every record on one phone.
FAQ
Does Pawmi use GPS to find pets near me?
No. It orders the feed using the city on your profile. It does not request location permission or collect device location.
Does PawMatch approve an adoption?
No. Treat it as a suggestion with reasons based on your questionnaire answers. The application has separate stages, including review and approval.
Are there payments or push alerts inside Pawmi?
No. There are no donations or payments inside the app, and updates are in-app only, without push notifications.
Planning a public-service app? Book a free consultation with Cortex Solution and bring the first permission request you are not sure you need.
Ready to apply these insights?
Our team can help you implement these strategies and solve your specific challenges.
Schedule a ConsultationNeed this for your business? See our web, mobile and automation services.
See how we implement this
No Account, No Server: What a Local-First App Trades
Keeping app data on the phone removes the account and server, but it also changes backup, recovery, sync and support. Here is how we made those choices in Daybook and Viora.
Designing a Kids' App With No Ads, Purchases or Internet
What changes when a children's game cannot rely on ads, purchases, accounts or a network connection? We explain the product decisions behind Mochi Hatch.
How We Scope a Software Project (And Why We Give Fixed Prices)
Most dev shops bill by the hour. We don't. Here's how we estimate projects and why fixed pricing works better for everyone.
What Running an AI Office Taught Us About Handing Work to AI
One job per AI, a supervisor check before anything goes out, memory resets before it gets costly, and stand-ups from real records: lessons from our own AI office.