Mosaic
A JavaFX desktop client, and the three-person team that built it
COMP 361, McGill University
The problem
Eight people, three sub-teams, one semester, and a system split across three repositories — a desktop client, an exchange server and an LLM server. No individual feature was the hard part. The hard part was that three teams had to commit to interfaces early enough to integrate before the demo, while none of them could afford to sit blocked on another.
What I built
- Scoped what the application side owed the project across the semester, then forced four open questions to a decision in a single meeting instead of letting them drift: platform, screens, persistence and stack.
- Argued for a desktop app over a web app. The hardware requirement meant browser permissions and OS support were a demo risk we did not need to carry, and the acceptance demo was the one date that could not move.
- Picked Java 21 and JavaFX 21 specifically so the client and the networking team's work would integrate without version friction. The decision was about the seam between two teams, not about the language.
- Built the foundation myself and got it merged first: Maven and JavaFX bootstrap, the main layout that swaps Splash, Workspace, Expert Selection and Settings, controller stubs with TODOs mapped to issue numbers, and a README. Everyone else branched from it.
- Designed the wireframes and the navigation model — settings behind a gear, switching experts as an explicit action, chat as the permanent workspace, and no in-app window chrome because the operating system already provides it.
- Wrote every issue for the team and then let people assign themselves rather than allocating the work. Discussion stayed in the issue threads, so a decision made in March was still findable in April.
- Built the inference path: token streaming from a local model, and remote inference between two instances of the app running on different machines — one sending a prompt across the network and receiving tokens back — plus peer discovery and direct file transfer of adapters between them.
- Split the design-document work by the kind of work people wanted — modelling, risk analysis, or engineering setup — took the coordination-heavy third myself, and said up front that we would rebalance if anyone's share turned out heavier than it looked.
- Reviewed every pull request on the client, including a teammate's first use of git. Reassurance first, specifics second, and an offer to walk through anything confusing — a review that leaves someone afraid to push again has cost more than it found.
- Ran the team async through two exam weeks rather than letting my own availability become the bottleneck, and kept the integration seam with the networking team moving in parallel.
Outcome
- Shipped and demoed: the client runs against the other teams' LLM and exchange servers, with two instances talking to each other across machines.
- Second-highest commit count of six contributors, at roughly a fifth of the total — and deliberately capped. In the final phase I stopped writing code and asked for the remaining work to be distributed to the two people reporting to me, because they needed the contribution on record more than I needed the commits.
Stack
Note
A course project, built with seven others across three sub-teams. The client is my team's repository; the exchange and LLM servers were other teams' work and I have no commits in either. What I can claim is the application side and the coordination around it.
Next
TaxMapCA
Four questions, one exact Canadian sales-tax rate, and a government source behind every answer. Deterministic on purpose.