Emercgency_Agent AI

Bhargav Balaji — Fri, 16 Oct 2026 11:31:06 +0000

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle

What I Built

<You built LocalFix as a two-part application:

Frontend: A mobile-first React app built with Vite and Tailwind. It captures the user’s location, lets them choose a service and specific problem, and displays nearby technicians with direct tel: call buttons. The main UI is in App.jsx.
Backend: An Express API with a Mongoose Provider model. Its 2dsphere index and $geoNear aggregation support radius-based technician search; routes also handle registration and availability. See Provider.js and providerRoutes.js.
Data flow: The frontend sends coordinates, radius, category, and specialty to the search API. MongoDB filters to available technicians, calculates distances, and returns results for the UI.
Deployment: GitHub Actions builds the Vite frontend and publishes it to GitHub Pages. The public site hosts the frontend only; the Express API and MongoDB still need separate hosting and configuration for search and registration to work publicly.>

Demo

Code

How I Built It

<I built LocalFix as a mobile-first app with a React and Vite frontend and an Express and MongoDB backend. The interface guides users from location and service selection to a nearby technician’s profile and a one-tap phone call.

The frontend requests the user’s location, then sends coordinates, radius, service category, and problem type to the API. The API uses a Mongoose provider model with a MongoDB 2dsphere index and $geoNear aggregation to find available technicians and sort them by distance. Registration and availability changes use separate API routes.

I added sample Hyderabad technicians for testing and a GitHub Actions workflow that builds and publishes the frontend to GitHub Pages. The public site currently hosts the frontend; live search and registration require a separately hosted API and a configured MongoDB connection.>

Why Does Open Innovation Matter?

<Open innovation matters because useful ideas and expertise aren’t confined to one organization. By collaborating with users, researchers, partners, and other companies, teams can:

Solve problems faster by drawing on knowledge and tools they don’t have internally.
Build better products using real feedback from the people who will use them.
Reduce cost and risk by testing ideas collaboratively before investing heavily.
Reach more people through partnerships, shared technology, and broader networks.
For LocalFix, open innovation could mean working with technicians and residents to refine service categories, verify provider profiles, and improve how urgent repair requests are matched.>

DEV Community: Bhargav Balaji