Market Weaver
The Contagion Engine for Global Markets.
Created on 25th January 2026
•
Market Weaver
The Contagion Engine for Global Markets.
The problem Market Weaver solves
The Problem:
I realized that our global economy is incredibly fragile. A single port strike or a chip shortage doesn't just stay local, it ripples across the world in seconds. But right now, traders and managers are flying blind. They rely on static spreadsheets that only show what is happening, never why. I built this because I saw that by the time the news breaks, it’s usually too late to react.
The Solution:
It's a map, not a List. That’s why I created Market-Weaver. I wanted to move beyond simple stock tickers and visualize the hidden "nervous system" of the economy. I mapped over 5,000 real-time connections to show exactly who depends on whom. It lets you see the invisible links—like how a copper shortage doesn't just hurt miners, but cripples real estate developers weeks later.
The most powerful thing people can use it for is Simulation Mode. I built it to act like a financial "Time Machine." You can create a disaster—like spiking oil prices by 40%—and watch the shockwave travel through the network. It allows you to predict the crash before it happens, turning vague anxiety into calculated, actionable confidence.
Challenges I ran into
Building a project as visually ambitious as Market-Weaver was a massive learning curve. One of the biggest hurdles was the "Terminal Refresh" bug. Everything worked perfectly while I was clicking around the UI, but the second I hit refresh on the /terminal route after deploying, the whole app would break with a 404 error. It felt like the server just forgot my app existed. I eventually realized it was a routing conflict with the hosting provider, and I had to manually tell the server to point everything back to the main index file so React could handle the navigation.
Then there was the battle between "cool" and "readable." I started out with so many neon glows and glitch effects that the actual data—the most important part of a terminal—was getting buried. It looked like a sci-fi movie prop, but it was impossible to use. I had to strip back the chaos and find a balance, keeping the "Cyber Blue" aesthetic for the borders and accents while making sure the text remained sharp and professional. It taught me that even in a sci-fi world, user experience still comes first.
On the data side, trying to keep the node graphs and news tickers running smoothly was a challenge. Rendering complex supply chain relationships in React Flow while animating a "Breaking News" marquee started to tank the performance. I had to get smart with how I managed state and rendered components, ensuring that the "high-tech" animations didn't make the dashboard feel laggy. In the end, it was all about making the complex feel simple and the futuristic feel functional.
Tracks Applied (1)
AOPS
Technologies used