Zync
A collaborative workspace that brings project planning, communication, GitHub activity, notes, tasks, meetings, and design discovery into one place for distributed teams.
Why We Built It
Working together in person was easy. Working remotely wasn't. We were constantly jumping between GitHub, calls, meetings, messages, notes, and project updates just to keep the work moving. Zync started as our attempt to bring those scattered parts of collaboration into one place.
From an Idea to a Workspace
We didn't start with a complete product plan. We started by listing the things that kept slowing us down and gradually turned those problems into features. Projects, tasks, meetings, chat, notes, GitHub activity, design references, and team collaboration eventually became parts of the same workspace.
What I Built
I worked across several of Zync's core systems. I built the GitHub integration and dashboard, the collaborative Notes experience, the design discovery system, the architecture generation workflow, and the landing page. The GitHub integration connects user accounts and repositories through OAuth and GitHub Apps, while the dashboard pulls contribution data, activity, repositories, and project information through GitHub's REST and GraphQL APIs.
Making Notes Actually Collaborative
Real-time editing was one of the parts that took the most experimentation. We used BlockNote for the editor, Yjs for CRDT-based document state, IndexedDB for local persistence, and Socket.IO to move updates between connected clients. Each client maintains the same Yjs document. Changes become binary updates, travel through the Notes Socket.IO channel, and are applied by the other clients. Presence and cursor information are handled separately, while IndexedDB allows the document state to persist locally.
Understanding Before Building
Some of the hardest parts were the things I didn't know how to build yet. The design scraper is a good example. Instead of trying to make an AI agent solve it for me, I had to understand how the target sites worked, inspect their structure, research scraping approaches, and build the scrapers around what I found. Zync now searches multiple design sources in parallel through a shared Puppeteer browser and turns the results into a single design discovery experience inside the workspace.
From a Repository to an Architecture
I wanted Zync to understand the projects people were working on, not just link to their repositories. The architecture generator reads a linked GitHub repository, gathers its project context, sends the relevant structure to an AI model, and turns the response into a structured architecture overview. The system caches repository analysis using repository metadata, processes the repository tree, sends structured context to Gemini 3 Flash or a configurable OpenAI-compatible provider, stores the generated result, and renders the architecture back inside the project page.
The Architecture Changed
Our first architecture wasn't the right one. As we started pushing collaboration, chat, and real-time features further, we realized our initial database setup wasn't going to fit the way we wanted the system to work. We stopped, researched the available options, evaluated the trade-offs, and changed the setup instead of forcing the original design to survive. Zync ended up using MongoDB-compatible database access for the application's main data and Firestore where its client-side real-time listeners made sense. MongoDB handles the application's broader data model, while Firestore acts as a real-time team-state layer.
What Zync Taught Me
Zync taught me that knowing a technology isn't the same as knowing when to use it. Most of the difficult decisions came before writing the code: understanding the problem, researching possible approaches, choosing the right trade-offs, testing them, and changing direction when they didn't hold up. It also changed how I learn. When something doesn't work, I don't want to keep guessing until an AI gives me an answer. I want to understand what's actually happening underneath so I can fix it myself.