Project Info
Inspiration
Information today is increasingly consumed through audio—lectures, meetings, podcasts, and interviews—but audio is inherently linear and difficult to revisit. We were inspired by the question: what if spoken ideas could be transformed into structured, visual workflows automatically? We wanted to help students, researchers, and creators turn dense audio into something explorable, skimmable, and actionable.
What it does
Mappit! takes an audio file as input and automatically generates a visual flowchart representing the key ideas, concepts, and relationships discussed in the audio. Instead of reading long transcripts, users can explore a structured graph that highlights major themes while still preserving supporting details.
How we built it
We designed Mappit! as a modular pipeline powered by AI agents: Speech-to-text using Whisper to generate accurate transcripts Concept extraction agents that identify topics, subtopics, and relationships Node generation agents that create raw graph nodes from extracted concepts Cleaning and filtering logic to reduce noise and organize the graph Frontend visualization using an interactive flowchart interface to display nodes and edges Each agent operates independently, acting like a function in the pipeline. This made the system easier to debug, extend, and iterate on under hackathon constraints.
Challenges we ran into
One of our biggest challenges was overpopulation of the graph. Audio naturally contains many small, niche ideas, and naïvely converting them into nodes resulted in cluttered and overwhelming visualizations. Balancing completeness with clarity—deciding what concepts truly mattered—was a nontrivial problem. We also faced challenges in designing layouts that felt intuitive rather than chaotic, especially as the number of nodes increased.
Accomplishments we're proud of
Successfully transforming raw audio into a structured visual representation Building a fully modular, agent-based pipeline that can be extended easily Creating an interactive flowchart that makes long-form audio more digestible Tackling a real usability problem rather than just a technical one
What we learned
We learned that visual clarity is just as important—if not more—than model accuracy. Extracting information is easier than organizing it in a way that humans actually want to explore. We also gained valuable experience working with multi-agent AI systems, designing pipelines under time pressure, and iterating quickly based on visual feedback.
What's next
for Mappit! Introduce hierarchical abstraction, grouping minor nodes under higher-level concepts Add importance scoring so only the most relevant ideas appear by default Improve graph layout and clustering for readability Improve connections between nodes Enable live usage, such as live streams or real-time video conferencing
Mappit!
Inspiration
Information today is increasingly consumed through audio—lectures, meetings, podcasts, and interviews—but audio is inherently linear and difficult to revisit. We were inspired by the question: what if spoken ideas could be transformed into structured, visual workflows automatically?
We wanted to help students, researchers, and creators turn dense audio into something explorable, skimmable, and actionable.
What it does
Mappit! takes an audio file as input and automatically generates a visual flowchart representing the key ideas, concepts, and relationships discussed in the audio. Instead of reading long transcripts, users can explore a structured graph that highlights major themes while still preserving supporting details.
How we built it
We designed Mappit! as a modular pipeline powered by AI agents:
- Speech-to-text using Whisper to generate accurate transcripts
- Concept extraction agents that identify topics, subtopics, and relationships
- Node generation agents that create raw graph nodes from extracted concepts
- Cleaning and filtering logic to reduce noise and organize the graph
- Frontend visualization using an interactive flowchart interface to display nodes and edges
Each agent operates independently, acting like a function in the pipeline. This made the system easier to debug, extend, and iterate on under hackathon constraints.
Setup
Prerequisites
- Node.js (v14 or higher) and npm
- Python (v3.8 or higher) and pip
- FFmpeg (required for audio processing)
Installation
1. Clone the repository
git clone https://github.com/yourusername/mappit.git
cd mappit
2. Backend Setup
cd backend
pip install -r requirements.txt
3. Frontend Setup
cd frontend
npm install
4. Environment Variables
Create a .env file in the backend directory with the following variables:
OPENAI_API_KEY=your_openai_api_key_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here # if using Claude
5. Run the Application
Start the backend server:
cd backend
python api.py
In a new terminal, start the frontend:
cd frontend
npm start
The app should now be running at http://localhost:3000
What's next for Mappit!
- Introduce hierarchical abstraction, grouping minor nodes under higher-level concepts
- Add importance scoring so only the most relevant ideas appear by default
- Improve graph layout and clustering for readability
- Improve connections between nodes
- Enable live usage, such as live streams or real-time video conferencing
Analysis
View
Metric
- 14
- 10
- 2
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- FlaskIn code
- HTMLIn code
- JavaScriptIn code
- LangChainIn code
- OpenAIIn code
- PythonIn code
- PyTorchIn code
- ReactIn code
9 of 9 appear in the indexed code.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
65 KB
Source files
17
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
sohamgarg2020/MindMap
34 files · 36.8 MB · @ c7fe7b0
Structure
Application logic
13 files · 38%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- Python44%
- JavaScript43%
- Markdown9%
- HTML3%
- CSS1%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
backend/requirements.txt
pypi · 19- flask
- flask-cors
- langchain
- langchain-anthropic
- langchain-community
- langchain-core
- langchain-openai
- langchain-text-splitters
- langsmith
- numpy
- openai
- openai-whisper
- pydub
- python-dotenv
- regex
- tiktoken
- torch
- tqdm
- +1 more
frontend/package.json
npm · 9- @testing-library/dom
- @testing-library/jest-dom
- @testing-library/react
- @testing-library/user-event
- react
- react-dom
- react-scripts
- reactflow
- web-vitals
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.