THE GREAT DISCONNECT

• 

  choose ur poison

• 

  homepage

• 

  gathering survivors

• 

  username selection

• 

  fingers crossed

• 

  Test of time

Inspiration

Of course. Here is a draft for your "About the Project" section, written from your perspective.

About The Great Disconnect Inspiration In a world saturated with endless digital content and superficial connections, I wanted to explore a simple question: What does a connection truly mean when it becomes finite?

The Great Disconnect was inspired by the idea of digital scarcity. I imagined a scenario where the internet, our infinite bridge to others, was about to disappear forever. This project is a narrative experiment that challenges users with a high-stakes choice: if you had one last 10-minute chat to find a soulmate, would you bet it all on a 50/50-coin toss from destiny? It's about creating a moment of urgency and profound meaning in our final digital hours.

How It Was Built This project is a full-stack MERN application, designed to handle real-time interaction and a unique user experience.

Frontend: The client-side was built with React (using Vite) to create a fast, responsive, and modern user interface. It was deployed globally via Netlify.

Backend: The server is a robust Node.js application using the Express framework to handle API requests, user authentication, and the core matchmaking logic. It is hosted on Render.

Real-time Communication: The heart of the 10-minute chat is powered by Socket.IO, enabling low-latency, bidirectional communication between users.

Matchmaking & Caching: To manage the high-speed matchmaking queue and handle temporary session data efficiently, I integrated Redis as an in-memory data store.

Database: MongoDB serves as the primary database, storing user profiles and the outcomes of their final connections.

Challenges Faced The most significant challenge was implementing the core real-time logic. Ensuring the 10-minute timer was perfectly synced for both users and that the final 50/50 location reveal was both truly random and securely delivered required careful state management between Socket.IO and Redis.

Additionally, deploying a distributed full-stack application was a major learning curve. Configuring CORS policies, managing environment variables securely across Netlify and Render, and establishing a stable connection between the Node.js server and the separate Redis instance were complex but essential hurdles to overcome.

What I Learned This project was an incredible learning experience. Technically, it solidified my skills across the entire MERN stack, particularly with real-time technologies like Socket.IO and the practical application of Redis for high-performance state management. I also gained invaluable hands-on experience in modern CI/CD and multi-service deployment workflows.

Conceptually, I learned about the power of narrative design in software. Building an experience with high emotional stakes taught me how to create not just a tool, but a story. It underscored how principles like scarcity and urgency can be used to create a deeply engaging and meaningful user experience.

Built With

• express.js
• netlify
• node.js
• react
• socket.io
• vite