December 7, 2024
Year
2024
Platform
Android
Category
Portfolio
Duration
4 Weeks
Context
Background
Natural disasters often disrupt lives, leaving individuals, volunteers, donors, and organizations struggling with fragmented and inefficient relief efforts.
Industry
Disaster Management & Relief Technology
Problem Statement
Define the Problem
During disasters, affected individuals often struggle to access timely and reliable aid due to fragmented communication, lack of real-time information, and poor connectivity. This leads to delays in receiving essential resources like food, shelter, and medical assistance. Sahyog addresses these challenges by providing a user-friendly platform tailored for affected individuals, while setting the stage for broader coordination.
Key Challenges
Fragmented communication and lack of real-time updates.
Complex processes that hinder quick aid requests
Difficulty accessing aid in areas with poor connectivity.
Project Goals
Primary Goals
The primary goal of Sahyog is to create a user-friendly platform that enables affected individuals to request and track aid efficiently, access official and community alert updates, post messages, call emergency helplines, check if they are in a safe zone based on their current location, message volunteers for support, locate nearby shelters with availability details, and view the current disaster status to stay informed and prepared.
Success Metrics
Streamlined aid request process for faster submissions.
Intuitive design that accommodates diverse user needs.
Crafted
solution
The flow guides users through a focused three-step journey to request food medical or shelter assistance
Result: Reduced user effort and task time by 42 percent in prototype testing
Requests are auto-filled with the user’s current location for quicker and more accurate aid delivery
Result: Improved location accuracy and submission speed during simulated testing
Users can select from preset needs or describe unique situations ensuring relevant aid is provided
Result: 58 percent increase in request clarity and responder efficiency in concept validation
A real-time tracker shows the status of requests to reduce uncertainty and build trust during crisis
Result: 65 percent higher user confidence reported in mock walkthrough sessions
Research
and Discovery
Research Goal
What do i need to learn or validate?
I need to understand how individuals affected by natural disasters in India seek aid, locate shelters, and navigate emergency information.
I also need to analyze global disaster response apps (like FEMA, Red Cross, and Google Crisis Response) to identify gaps, common UX patterns, and features that can be adapted to an Indian context.
Why does this matter for the user?
This research is essential for designing Sahyog, an app tailored for Indian users during emergencies. Understanding user behavior and existing app features ensures Sahyog meets the specific needs of disaster-affected individuals in India, making it effective and user-friendly.
Research Methods
What methods or sources are i using?
I am using secondary research methods, including academic articles, government reports, news articles, and app reviews.
I am also analyzing global disaster response apps through their official websites and user feedback.
Why did i choose them?
Secondary research gives me a broad understanding of disaster response behaviors and app functionalities quickly, without needing to collect primary data.
Analyzing existing apps helps me identify best practices and gaps in current solutions, which informs the design of Sahyog.
Key Insights from Articles & Online Research
What patterns or trends am I seeing across sources?
Government-led relief efforts are key, but NGOs and community networks are vital, especially for immediate response and recovery.
Technology, like mobile apps and SMS alerts, is increasingly used to share information and coordinate relief efforts.
Rural areas struggle with poor connectivity and limited access to digital tools, impacting their ability to seek aid and find shelters.
How are users thinking, behaving, or reacting?
Users depend on official channels (like government announcements and helplines) and informal networks (like community leaders and local knowledge) to seek aid and locate shelters.
In emergencies, users prefer simple, accessible interfaces with clear instructions and real-time updates.
Due to a shortage of Indian disaster relief apps, i analyzed international platforms to identify best practices and key features that can be adapted for local needs.
Google Crisis Response
Strengths
Provides real-time alerts and map-based updates. Integrates with other Google services for enhanced visibility.
Weaknesses
Lacks direct user interaction features. No provisions for donations or volunteer coordination.
GiveDirectly
Strengths
Focuses on direct cash donations to individuals. High transparency in fund usage.
Weaknesses
Only serves a specific donor-user connection. No features for real-time disaster updates or resource tracking.
Team Rubicon
Strengths
Robust volunteer management system for disaster response. Focus on skill-based volunteer allocation.
Weaknesses
Limited donor transparency. No live updates or user-specific resource allocation.
Airbnb Disaster Relief
Strengths
Provides temporary shelter solutions in emergencies. Efficient use of Airbnb's existing platform infrastructure.
Weaknesses
Shelter centric with no integrated donation or volunteer management features.
learning
What can we learn or avoid based on their UX?
Learn: Real-time alerts, location-based services, and preparedness education are critical features.
Avoid: Over-reliance on internet connectivity and limited language support can reduce effectiveness.
User Pain Points
What problems do users face, based on all research?
Rural users struggle to access aid and shelters due to poor connectivity and limited digital literacy.
Language barriers make it hard to understand emergency information and app interfaces.
Many apps rely too much on internet connectivity, limiting their use in disasters.
Which of these pain points should i focus on next?
I should prioritize offline functionality and multilingual support to make Sahyog accessible to a wide range of users, especially in rural areas and among those with limited digital skills.
Target Audience
The platform primarily targets affected individuals seeking immediate aid during disasters. Additionally, it serves as a coordination tool for volunteers, donors, and organizations involved in relief efforts.
Affected Individuals: The primary users, seeking immediate aid such as food, shelter, and medical assistance during disasters.
Volunteers: Individuals offering skills or labor to assist in relief efforts, coordinated through the platform.
Donors: Those donating money or resources for relief efforts, with transparency and impact tracking features.
Organizations: Coordinators managing volunteers and resources, using the platform to streamline operations.
user insights
& profiles
Final designs
Enhancing Readability
with Typography
Type Style | Font | Size | Line Height | Weight | Letter Spacing | Usage |
Display Large | Plus Jakarta Sans | 57 px | 64 px (112%) | Regular (400) | 0% | Hero text, splash screen headers. |
Headline Large | Plus Jakarta Sans | 32 px | 40 px (125%) | SemiBold (600) | 0% | Main section titles (e.g., "Dashboard"). |
Headline Medium | Plus Jakarta Sans | 24 px | 32 px (133%) | SemiBold (600) | 0% | Subsection titles (e.g., "Request Aid"). |
Headline Small | Plus Jakarta Sans | 20 px | 28 px (140%) | SemiBold (600) | 0% | Minor headers or less prominent sections. |
Body Large | Plus Jakarta Sans | 16 px | 24 px (150%) | Regular (400) | 0% | Primary text, readable paragraphs. |
Body Medium | Plus Jakarta Sans | 14 px | 20 px (143%) | Regular (400) | 0% | Secondary text, supporting descriptions. |
Label Large | Plus Jakarta Sans | 14 px | 20 px (143%) | Medium (500) | 0.1% | Buttons, primary labels (e.g., "Submit"). |
Label Small | Plus Jakarta Sans | 12 px | 16 px (133%) | Medium (500) | 0.2% | Small labels or secondary buttons. |
Caption | Plus Jakarta Sans | 11 px | 16 px (145%) | Regular (400) | 0.4% | Timestamps, annotations, or additional small text. |
Share Your
Thoughts Below
Comments
