Skip to main content
Back to projects
PawPin icon

PawPin

An Android-first phone app for reporting stray animals with an exact location, so nearby rescuers can find them.

Role
Mobile app design + full-stack development
Outcome
One path from spotting a stray to a rescuer arriving at the exact spot.
Stack
ExpoReact NativeSupabase
PawPin banner

What it is

PawPin is a phone app for helping stray animals. A person photographs a stray, the app records exactly where and when the photo was taken, and rescuers nearby see the report on a map and get directions to the animal.

It is built for two kinds of people: reporters who spot a stray, and rescuers who go to help. People can sign in with Google or continue as a guest. An admin account reviews flagged reports and can close them.

This case study covers version 1.1.0 of the Android app and its public landing page. Android is the main target; the browser version only shows that reporting and the map work in the phone app, and an iPhone build is not part of this release.

The problem and the fix

The problem

  • Locations get lost

    Stray posts often leave out the place or describe it loosely; a goal from the project guide

  • Two rescuers, one animal

    Without a shared status, people can set out for the same stray

  • Reports need trust

    Photos, statuses, and guest accounts all need limits against mistakes and abuse

The fix

  • Place fixed at the first photo

    Location, accuracy, and time are recorded when the photo is taken

  • Map, list, and directions

    Urgency-colored pins, nearest-first list, and Google Maps or Waze links

  • One rescuer per report

    I'm on my way changes the status live for everyone through a database function

  • Rules in the database

    Limits, status changes, alerts, and notifications run on the server; several screen checks rest on my own testing

What I did

  • Product planning from the project guide into seven roadmap phases and a hardening pass.
  • Screen design for welcome, map, list, reporting, report page, chats, profile, and the admin's screens.
  • App development with Expo, React Native, and TypeScript.
  • Supabase database design: tables, access rules, database functions, triggers, and 36 numbered migrations.
  • Android release builds and the landing page with the APK download.

All commits in the repository are my own. This write-up does not claim user research or usability testing.

How I designed it

  1. 01

    Make reporting quick

    Permissions, camera, then a short form with fixed choices

    Speed
  2. 02

    Show urgency first

    Paw pins and cards are colored Critical, Needs help soon, or Just sighted

    Priorities
  3. 03

    Two buttons at most

    The report page shows Directions and the one next step for that report

    Focus
  4. 04

    Ask before changing status

    Every status change goes through one shared confirm dialog

    Safety
  5. 05

    Warn, do not block

    The photo check nudges the reporter but never stops a report

    Choice

Main features

Reporting a stray

Take photos in the app's own camera. The place, its accuracy, and the time are fixed at the first photo. Drag the pin, choose the animal's details and urgency, add a landmark, and send.

Photo check

When the reporter leaves the camera, the phone checks whether any photo shows an animal, with no internet needed. If none does, a drawer warns the reporter, who can start over or continue. A report sent anyway is marked for the admin. The check is a nudge, not a guard.

Map and list

Nearby reports appear as paw pins colored Critical, Needs help soon, or Just sighted. The list shows the same reports nearest first, with a filter for whose reports and for a distance of 1, 5, 10, or 25 km.

Directions

One button opens Google Maps or Waze with the animal's location as the destination.

Claiming and outcomes

A rescuer taps I'm on my way. The report changes to Someone is on the way for everyone, live. The rescuer then marks it as rescued or not found, or gives up. Reporters can close their own report, and reports untouched for 72 hours close by themselves.

Alerts and notifications

A new report sends a push alert to users within the distance they chose. Reporters are told when someone sets out, gives up, rescues the animal, or cannot find it, and why a report was closed. Each event is kept in a notifications list.

Chat between reporter and rescuer

While a rescuer is on the way, the two can send text messages about that report. A Chats tab lists these chats and says why a chat ended.

Guests, flags, and the admin

Guests can report up to 3 strays and send up to 3 flags in 24 hours. Users flag fake or abusive reports, and an admin reads flags, sees reports sent with no animal seen, and can close a report with a reason.

Unsent reports

If sending fails, the report stays on the phone so the reporter can send it again without making a second copy.

Tech Stack

  • Expo SDK 57 and React Native 0.86

    build the Android app from one codebase, with React 19 and React Compiler on.

  • TypeScript

    types for reports, claims, notifications, and messages.

  • Expo Router

    file-based screens and typed routes, with a route guard for signed-in and signed-out users.

  • HeroUI Native, Uniwind (Tailwind CSS 4), and Hugeicons

    interface components, class styling, and icons.

  • Supabase Auth

    Google sign-in and guest accounts.

  • Supabase Postgres with PostGIS

    stores reports and finds nearby ones by distance.

  • Supabase Storage

    holds report photos in a folder per user and report.

  • Supabase Realtime

    sends report changes and new messages to open screens.

  • pg_cron and pg_net

    close stale reports every hour and send push alerts from database triggers.

  • MapLibre with OpenStreetMap tiles

    draws the map and paw pins, with no map key or billing account.

  • Google ML Kit image labeling

    checks report photos for an animal on the phone.

  • Expo Camera, Location, Notifications, and Secure Store

    photos, place, push alerts, and encrypted sign-in storage.

  • Node test runner

    automated tests for screens and helpers; SQL check scripts that roll themselves back.

  • Vite and Vercel

    build and host the landing page.

There is no server of our own; the app talks to Supabase directly, and the database enforces the rules. Directions open in outside apps rather than being drawn in PawPin.

Hard parts and how I solved them

Sending a report twice
A weak connection can send the same report again. The report's id is made on the phone and saved as the row's id, and photos go to a folder named after that id, so a second send does not make a second copy.
Getting a location indoors
A fresh location read often fails indoors or just after the phone wakes. The app falls back to the last known position, then to the last place it read, before showing an error.
Keeping report status honest
The app cannot change a report's status directly. Claiming, giving up, recording an outcome, and closing all go through database functions that allow one rescuer per report, one report per rescuer, and never the reporter on their own report.
Alerts that never break a report
Push alerts are sent by database triggers. Each trigger is wrapped so an error becomes a warning, and the request leaves only when the change is saved.
Drawing routes in the app
A path drawn on PawPin's own map was tried and removed, because the free routing servers were not dependable. Directions now open Google Maps or Waze instead.
Shipping a usable APK
The first release build was about 230 MB. Building only for real phone chips, compressing native libraries, and shrinking code brought version 1.1.0 to 46 MB. Download links to GitHub opened in a small in-app browser on phones with the GitHub app and never finished, so the landing page now serves the file from its own address and passes it on to GitHub Releases.
Limiting guest abuse
One Android device can create a new guest account every 72 hours, enforced by the database. The device id is stored as a hash, but it can change after a factory reset and modified apps can fake it. This is best-effort prevention, not proof of a real device.

How it works

  1. 1

    Get into the app.

    Sign in with Google, or continue as a guest on Android.

  2. 2

    Report a stray.

    Allow camera and location, take photos, check the pin, choose the details and urgency, and send. If no animal is seen in the photos, choose to start over or continue.

  3. 3

    Find strays nearby.

    Open the Map to see paw pins by urgency, or the List to see the nearest first. Tap a pin or card to open the report with its photos and reporter.

  4. 4

    Go and help.

    Tap I'm on my way, open directions in Google Maps or Waze, and chat with the reporter if needed.

  5. 5

    Finish the rescue.

    Mark the animal as rescued or not found. The reporter is notified, the chat ends, and the report leaves the active map.

  6. 6

    Look back.

    The Profile tab holds notifications, Your reports, Your rescues, alert settings, safety tips, and the theme choice.

Results

  • Seven roadmap phases and a production hardening pass are built: sign-in, reporting, the map and list, rescue coordination, alerts and flags with the admin's app, the photo check, and notifications with chat.
  • Version 1.1.0 is released as a 46 MB Android APK, downloadable from the landing page.
  • Most screen checks rest on my own testing on a phone and were not written down line by line. The photo check was tried on pictures shown on a laptop screen, not on a real animal.
  • Migrations 0027 to 0029 exist as files only and are not applied to the live database.
  • Google sign-in works in the Android build only, and the browser version cannot be signed in to.
  • No user numbers, rescue counts, or usability results are reported.

What I learned

What worked

  • Letting the database enforce status changes, limits, and notifications kept the app simple and the rules the same for everyone.
  • Fixing the place and time at the first photo removed a whole class of wrong-location reports.
  • Planning each phase in its own file with a done check kept a large scope manageable.

What could improve

  • Write down screen checks as they are done, instead of relying on memory.
  • Test the photo check on real animals in daylight and at night.
  • Apply or remove the unapplied migrations so the files match the live database.

Future ideas

  • Sightings that build a trail of where an animal moved, and spotting duplicate reports.
  • A directory of vets, shelters, and rescue groups, and verified rescuer badges.
  • An iPhone build and offline report drafts.
Next projectRemindLyRemindLy is a personal task and reminder app that helps people remember what needs to be done and when.Read the story
RemindLy banner