How it is built
The interface and the back end work together
The screens are one part of the product. Sign-in, saved sessions, catalog data, and access rules support the experience behind them.
Front end · What people see and use
React & TypeScript
The customer questionnaire, recommendation cards, feedback controls, and owner dashboard are built as a React application. Vite builds the application, Tailwind provides styling, and Motion animates screen transitions and the record-selection experience.
Application server · Serving the experience
Express
The production server serves the application and exposes a recommendation endpoint that runs the catalog-based recommendation logic.
Back end · Identity and saved information
Firebase & Firestore
Firebase Authentication supports Google sign-in. Firestore stores the album catalog, private customer sessions, and de-identified customer-interest signals used by the owner experience. The catalog is populated using the Discogs API, which supplies release information such as artist, title, genre, style, and cover artwork.
Access controls · Who can see what
Customer privacy and owner roles
Firestore rules separate private customer records from owner access. Customers cannot assign themselves the owner role, and the cross-customer demand view is restricted.