The problem
Matching what someone has to give with what someone else needs, and keeping every request accountable as it moves through review, is more of a workflow problem than a listing problem. A simple post-and-browse feed doesn’t answer who approved a request or where it currently stands.
What I built
I built a donation management Android app end to end: user signup and profiles, donation posts with multiple images, requests against those posts, and messages to admins. Admin dashboards track donations, requests, and messages through waiting, accepted, and declined states, so nothing sits in limbo without a visible status. It’s a self-built project I designed and tested myself; it isn’t tied to any real charity, beneficiary, or donor network, and no real donations moved through it.
Tech stack
The Android client is written in Java, using Firebase Auth for accounts, Firebase Realtime Database for posts and requests, and Firebase Storage for donation images.
What I learned
Donation products need moderation and transparent status before real-world use.
Designing the waiting, accepted, and declined states taught me that a donation app’s hardest problem isn’t the listing screen, it’s making sure every request is accounted for.