Context
Bantay Bata 163 is ABS-CBN Foundation's child welfare program, known for its 163 hotline. This app is designed for two groups who support it: donors who give regularly, and concerned citizens who need to report a case or get help quickly.
The problem
Supporting a cause like this usually means jumping between channels: a phone call to report, a website to donate, social media for news. Each extra step loses people, and in an urgent case, delay matters. Donors also rarely see what their money achieved, which makes it harder to keep giving.
Two users, two mindsets
The two groups arrive in very different states. A concerned citizen may be worried or upset, and needs to act fast with as little thinking as possible. A donor is calm and comes back over months, and needs a reason to keep giving.
One app has to serve both without the urgent path getting buried under fundraising, or the donor experience feeling like an emergency tool.
Design principles
I wrote four principles into the design system before designing the flows, and used them to settle decisions along the way:
Clarity first. Reduce what people have to think about in urgent moments: one question per screen, large targets, short labels.
Color carries intent. Blue for primary actions and navigation, red only for emergencies and destructive actions, green for success, yellow for warnings. A color always means the same thing, so people can read a screen before reading its words.
Consistency. A 4pt and 8pt spacing grid, one card style and one header pattern across every screen.
A warm, readable typeface. Poppins, a rounded, human-feeling font, used in a small set of sizes.
Home: one question, four answers
After a short splash screen and sign-in (with Google and Facebook options, so first-time users don't need another password), the home screen asks "What would you like to do?" and offers four large cards: Donor Dashboard, Quick Report, Emergency Hotline and Donate. Each has its own icon and color, so people recognize their option without reading every label.
Campaigns like "Double the Donation" sit below the four actions, so fundraising is visible without pushing the urgent options down. The bottom navigation (Home, Donate, Helpline and Account) keeps the helpline one tap away from every screen.

Getting help: designed for the worst moment
The helpline screen is for people who may be scared or in a hurry, so it asks only "What do you need?" with three large choices: Call Hotline, Report Abuse and History. A red banner below it covers the most urgent case: in immediate danger, call 163 or 911.
Calling is one tap from a list of three hotlines (Bantay Bata, the national emergency line and DSWD crisis intervention), each with a one-line description so people pick the right one. Before the call connects, a short confirmation reminds the caller to make sure they're in a safe place. It adds one tap, but in a child abuse situation, the person calling may be near the abuser. A calm "Connecting your call" screen follows, so nobody wonders whether the tap worked.

Reporting a case
The report form opens with a reassurance: "All reports are confidential and free." The name field is optional and defaults to Anonymous, because someone who is afraid of being identified might not report at all. Only three things are required: a contact number, the incident location and what happened.
When a required field is missing, the error explains why it matters, instead of just saying it's required: "The incident location helps us dispatch the right response team quickly." A Talk to a Representative button sits under Submit on every step, for people who would rather explain to a person than fill in a form.
After submitting, people get a case number and can follow every report in Report Status, with clear Under Review and Resolved labels, so they know their report didn't disappear.


Giving: make it easy to start and fair to stop
Donating starts with one choice, monthly or one-time, plus a link to past transactions. Monthly giving is a three-step form with a progress bar: amount and details, payment method, then confirmation. Preset amounts (₱200, ₱300, ₱500 and ₱1,000) remove the hardest decision, and a custom field covers everyone else. Payment options are local and familiar: GCash, Maya, cards and online banking.
The receipt welcomes the new monthly donor and states exactly when the first charge happens. Monthly donations can be adjusted or cancelled from one screen. Cancelling shows what will stop and when, and suggests reducing the amount instead, but Keep my Donation and Yes, Cancel are both clear. Making it easy to leave is part of earning a donor's trust to stay.
The donor dashboard turns giving into impact: the total donated, children helped, a plain-language "Your impact so far" message, a donation trend and the full history.


Design system
Every screen is built from one documented system: a color palette where each color has a single job, a Poppins type scale with six styles, six button types with default and disabled states, a 24px filled icon set, and states for success, warning and error. Accessibility is written in: contrast checks for text on each color, 44×44px minimum touch targets, and color never used as the only signal.

Outcome and next steps
A complete high-fidelity mobile app in Figma, with around 50 screens covering sign-in, home, the helpline and calling, reporting and tracking a case, one-time and monthly donations, managing donations, notifications and account settings, all built on one design system.
The biggest thing I'd change next: the app opens on a login screen, so someone has to sign in before they can reach the hotline or report a case. Reports can already be anonymous, so I'd let people call and report without an account, and only ask them to sign in to donate or track impact.
