The problem
Legazpi City sits on Albay's eastern seaboard, below Mayon Volcano. Its 209,533 residents face three to five typhoons a year, plus tsunami and eruption risk.
When we started, the city's disaster office (DRRMO) shared announcements on its Facebook page and relayed them to barangays through Messenger group chats, falling back to two-way radios when power and internet went down. Evacuation centers reported headcounts by email, group chat, and paper, often only after the disaster had passed.
Two problems made this worse. Some residents wouldn't leave home until a disaster was already underway, because they feared losing their property. And evacuation centers didn't have room for everyone when they did.
My role
This was our capstone project at FEU Institute of Technology, built for the Legazpi City DRRMO by a team of five. I was the lead UI/UX designer, lead developer, and project manager.
I designed the web and mobile interfaces in Figma and built the design system they share. I also ran the project in Agile Scrum sprints (backlog refinement, sprint planning, development, and reviews) and facilitated meetings with our client.
Research
We started with interviews and follow-ups with the DRRMO to understand how information and evacuation data actually moved during a disaster, then mapped the root causes in an Ishikawa diagram. Surveys with potential users covered their experience with disasters, what they do before, during, and after one, the challenges they face during evacuation, and the tools they already rely on.
That gave us three users with very different jobs: residents who need to stay informed and get help, barangay officials who run evacuation centers, and DRRMO staff who coordinate the whole city.
Designing for the worst day
A disaster app gets used when the power is out, the signal is weak, and people are scared. That shaped four decisions:
Split the product by role. Residents get a focused Android app. Barangay officials and DRRMO staff work on the web, where they have room for maps, tables, and records. Anyone can open the public homepage to see announcements and the evacuation and incident maps without an account.
Make offline the default for critical content. Preparedness guides, emergency hotlines, and the evacuation center map are cached on the phone after the first visit, so they still open when the internet doesn't.
Make reports trustworthy. Incident reports only accept a live camera photo, the photo's location has to match where the user is, and nearby reports of the same incident are clustered together. Responders see one verified incident instead of a pile of duplicates.
Turn neighbors into shelter. Adopt-a-Neighbor lets owners of disaster-resilient private buildings volunteer as temporary shelters. The DRRMO approves each one, both sides verify the match, and chat is limited to users in the same barangay. It adds capacity when evacuation centers fill up, and gives hesitant residents a closer place to go.
The web platform
The public homepage shows announcements, incident reports, and evacuation shelter capacity on live maps. Admins, super admins, and barangay users each get a role-based dashboard to manage incidents and responders, publish announcements to the whole city or a single barangay, and moderate the missing persons and pets hub.
Evacuation center monitoring replaced the email and paper headcounts. Barangay officials check evacuees in and out, and each center's capacity updates on the map in real time.
The mobile app
Residents sign up with a national ID and their barangay, then get push notifications for city and barangay announcements. From the home screen they can call emergency hotlines, report an incident with a live photo, post or search for missing persons and pets, view the incident and evacuation maps, and request or offer shelter through Adopt-a-Neighbor.
Testing and results
We ran three rounds of testing between April and June 2025. Announcements, live chat, and ID verification failed the first round and passed the second; offline access took until the third.
For the final evaluation, 30 residents, 5 barangay officials, and 5 IT experts used the system face to face or over video call, then rated it on the FURPS model (functionality, usability, reliability, performance, and supportability). GabaySakuna scored 4.28 out of 5 overall. Usability was rated 4.59 (Excellent) by residents, 4.40 by barangay officials, and 4.16 by IT experts.
What I'd improve next
The lowest scores point to the next round of work. Residents gave 3.43 for the app working correctly every time, so stability comes first. IT experts gave 3.80 for completing tasks without instructions, which matches feedback that the admin dashboard is hard to navigate.
Next, I'd redesign the dashboard with clearer hierarchy, color-coded priority labels, and filters by date, incident type, status, and evacuation center, plus a guided first run for new admins. Beyond that: an iOS version, and smarter Adopt-a-Neighbor matching that accounts for family size, special needs, pets, and distance.
