Musicology-Guesser

Guess the composer given part of the music piece

Learn the story behind the score in https://musicologyguesser.onrender.com/ or https://musicology-guesser.vercel.app/ (If the app is struggle to load, please move to https://musicology-guesser.onrender.com/ to activate the backend)

3 Core Features

• Field Guide

Quick, fun hints on instrumentation, era, composer, and region — built for beginners who want a nudge, not a lecture. Read over this to found the correct solution

• Run the Guesser You'll see a short excerpt of manuscript and a case file of evidence. Decide the instrumentation, era, composer, and region — skip anything you're unsure of for a modest, honest 100 points.

• Collection

A collection of composers based on the mastery gained

Tech stack

Contract: Documents/API_CONTRACT.md. Backend notes: Backend/README.md.

How a round is scored

Four axes, 500 each, 2000 per round.

• Composer, country (where the work was written), and instrumentation: exact match, 500 or 0.
• Year: 500 − 10 × years off, floored at 0.
• Skip a question: 100 honesty points (client).
• Each clue: −20 (client).

Answers are not sent to the browser until you guess. Clue text never names the composer, the work, or the answer country.

Run it locally

Need JDK 21 and Node 20+. Nothing else.

# terminal 1 — API on http://localhost:8080
cd Backend
export JAVA_HOME=/opt/homebrew/opt/openjdk@21/libexec/openjdk.jdk/Contents/Home   # macOS Homebrew JDK 21
./mvnw spring-boot:run

# terminal 2 — app on http://localhost:5173
cd Frontend
npm install
npm run dev

Restart the backend after changing cases, then start a new game.

cd Backend && ./mvnw test
cd Frontend && npm test

API

Team

Manuscripts are cropped from public-domain sources (typically IMSLP).

Built With

• css
• dockerfile
• html
• java
• python
• typescript