During emergencies, people often struggle to find the nearest hospital, police station, or government office—especially in rural areas. Many existing apps show too much irrelevant data, outdated results, or require stable internet.

This inspired us to build Community Resource Finder, a simple, fast, and reliable platform to help citizens find essential public services within seconds. Our goal was to create a tool that reduces panic during emergencies and brings real-world impact to local communities.

🎯 About the Project

Community Resource Finder is a location-aware web application that helps users quickly discover important community resources such as hospitals, blood banks, police stations, fire stations, and government facilities.

It focuses on:

Speed (easy access during emergencies)

Accuracy (verified data + user updates)

Accessibility (works in low-network areas)

Simplicity (clear UI, no clutter)

We also added offline caching, emergency call shortcuts, and route navigation to improve usability.

🛠️ How We Built the Project

We followed a structured development cycle:

1. Understanding the Problem

We interviewed students and local community members and confirmed that they often rely on Google Maps—but struggle due to too much information or network issues.

1. Designing the Architecture

We planned a modular structure:

Frontend → APIs → Backend → Database → Map Services

1. Development Process Frontend (React / JavaScript)

Designed UI with clean and minimal components

Integrated maps using Google Maps API / OpenStreetMap

Implemented filtering & category-based searches

Backend (Node.js / Firebase / MongoDB)

Built REST APIs for resource retrieval

Added user submissions + crowdsourced updates

Integrated real-time database sync

Geo Features

We implemented distance calculation using the Haversine formula:

𝑑

2 𝑅 ⋅ arcsin ⁡ ( sin ⁡ 2 ( Δ 𝜙 2 ) + cos ⁡ ( 𝜙 1 ) cos ⁡ ( 𝜙 2 ) sin ⁡ 2 ( Δ 𝜆 2 ) ) d=2R⋅arcsin( sin 2 ( 2 Δϕ ​

)+cos(ϕ 1 ​

)cos(ϕ 2 ​

)sin 2 ( 2 Δλ ​

) ​

)

This helps users see the exact distance to each service.

1. Offline Mode

We added service-worker based caching so the last known data remains available even without internet.

🧠 What We Learned

Working on this project gave us valuable learning experiences:

How to use location APIs and manage map-based data

Building scalable REST APIs

Concepts of geolocation, reverse geocoding, and distance algorithms

Importance of user-centered design during emergencies

Managing real-time data sync and offline storage

Testing UI for accessibility & speed

⚡ Challenges We Faced

1. Handling Inaccurate Map Results

Some API results were outdated or missing. We solved this using:

secondary data sources

user-submitted resource verification

1. Performance with Multiple Markers

Displaying many locations slowed down maps. We optimized using:

clustering

lazy loading

1. Offline Mode

Implementing service workers was tricky at first, especially syncing cached data with new updates.

1. Designing Simple Yet Powerful UI

Balancing emergency-friendly UI with full features required multiple design revisions.

🌟 Conclusion

Community Resource Finder is more than a project—it is a tool that can genuinely help people during critical moments. We built it with the vision of making public services more accessible, reliable, and easier to find for everyone.

We plan to keep improving it with AI-based recommendations, multi-language support, and real-time community updates.