Skip to content
CASE STUDY

Mobile App Development

Volunteer delivery app for a food pantry that outgrew group texts

Open Shelf coordinated home deliveries in a text thread. We built a volunteer app for claimed routes, dietary flags, and proof of delivery that a coordinator can see without nagging.

The operational problem

Routes were screenshots. Dietary notes lived in someone’s memory. A missed fridge meant a wasted pack and a hungry household.

Trust with families is the program. Operational slop looks like unreliability.

What was breaking down

  • Group texts as a TMS
  • No flag for allergies on the stop
  • Unclear which volunteer still had a bag

How Striders Tech approached it

We made claiming a route a two-tap job, put dietary flags on the stop card, and required a simple close so the coordinator sees holes early.

What we built

  • Volunteer claim of a route
  • Stop cards with dietary and access notes
  • Photo-optional proof of delivery
  • Coordinator view of open vs closed stops

Results the team can measure

  • Missed stops caught before the warehouse closed
  • Less chat noise on delivery nights
  • Volunteers trained in one evening, not a binder

Who this case study is for

Nonprofits running last-mile kindness on consumer chat apps.

Open Shelf Pantry operates in nonprofit / logistics. The work is a custom system designed around their process, not a generic template with extra fields bolted on.

THE OUTCOME

What changed after the system went live

Missed stops

caught before the warehouse closed

Less chat noise

on delivery nights

Volunteers

trained in one evening, not a binder

THE TAKEAWAY

Good software doesn't add complexity. It removes it.

Discuss your project