This is a submission for the DEV Weekend Challenge: Community

The Community

A few months ago, a friend reached out to him late at night.

“Do you know any tool that can actually help with this? I’ve been searching for an hour and now I’m more overwhelmed than when I started.”

The friend was a college student. Smart, capable, constantly juggling assignments, exams, and expectations.


He also had ADHD.

The problem wasn’t a lack of tools it was the opposite.

Productivity apps. ADHD planners. Focus tools. Study systems. Recommendation threads. Endless “best apps” lists.

Each search added another decision.


Each decision increased the cognitive load.

By the time the search ended, nothing had been chosen and the overwhelm had only grown.

The person reading that message understood immediately.

He is part of the same overlapping communities:

• a college student
  


• a developer
  


• someone living with ADHD
  

In these communities, the hardest part is often not execution it’s starting.


And starting means choosing. Choosing means evaluating options. And evaluating options is exhausting when your brain is already overloaded.

What actually helped wasn’t finding another tool.

What helped was when someone narrowed the field and said:

“Based on what you’re dealing with right now, start here.”

Bridgy is built for that moment.

What I Built

Bridgy is a transparent, rule based resource matching web app designed to reduce decision paralysis not add to it.

Instead of asking users to browse endlessly, Bridgy:

• Accepts natural language input or a simple 3 question guided flow
  


• Interprets context (community, problem, urgency)


• Matches users to 2–3 curated resources
  


• Explains why each resource was selected


• Suggests one concrete next action
  

There are:

• no black-box recommendations
  


• no scraping
  


• no tracking
  


• no stored personal data
  

Every recommendation is deterministic and explainable.

AI is used only to understand language and rewrite explanations empathetically never to decide what resources are shown.

Demo

Video Demo

Code

GitHub Repository

How I Built It

Architecture Philosophy

Bridgy is intentionally:

• Static-first


• Privacy-first


• Explainable by design

There is:

• no backend database


• no user accounts


• no analytics


• no stored user data

The app works fully even without an API key.

Tech Stack

How Bridgy Works

1. 
   

   User Input

   
   
   
   
   
   • Guided mode (community → problem → urgency)
     
   
   
   • OR free-text natural language
   
   
   
   


2. 
   

   Intent Parsing

   
   
   
   
   
   • Free text is parsed into structured intent using GLM-4.5
     
   
   
   • Falls back to Gemini 2.0 Flash
     
   
   
   • If no API key exists, a keyword-based local parser runs instead
   
   
   
   


3. 
   

   Deterministic Scoring

   
   
   
   
   
   • Community match: +3
     
   
   
   • Problem match: +3
     
   
   
   • Urgency match: +1
     
   
   
   • Human support (when requested): +2
     
   
   
   
   

Same input always produces the same ranked output.

1. 
   Transparent Results
   
   
   
   
   • 2–3 matched resources
   
   
   • “Why this?” explanations
   
   
   • One clear next action
   
   
   
   

Why These Decisions Matter

Bridgy deliberately avoids:

• web scraping


• live search


• user tracking


• black-box AI recommendations

For people who are already overwhelmed, trust and clarity matter more than clever automation.

Every design decision was made to reduce cognitive load not increase it.

Closing

Technology has done a great job building tools for communities.

It has done a much worse job helping people navigate between them.

Bridgy is a small attempt to bridge that gap not by adding more options, but by helping someone take one clear step forward when everything feels like too much.

Sometimes, that’s enough to change the direction of a day.