Built to order

PG Roommate Finder with Lifestyle Matching

Finding a paying-guest roommate in a new city is luck of the draw — most students pick from broker listings and discover the sleep-schedule clash after moving in. This project is RoomSync, a PG roommate finder that ranks candidates by lifestyle compatibility: a 12-question quiz captures sleep, food, smoking, noise and budget habits, and each match shows a scored breakdown so the decision is informed, not random. Suitable for B.E./B.Tech final-year projects in Computer Science, IT and Web Development.

PG Roommate Finder with Lifestyle Matching — project thumbnail preview
More project photos (2)

The problem

Students relocating to cities like Pune for college or a first job face the same ritual: broker WhatsApp forwards, rushed flat visits, and a roommate chosen on gut feel. The expensive failures are lifestyle mismatches — a night owl paired with an early riser, a smoker with someone who cannot stand it, incompatible food habits in a shared kitchen. Existing listing sites show rooms, not people, and profile-based apps leave compatibility to chat vibes. This project builds RoomSync, a roommate-matching web app centered on a lifestyle quiz. Twelve questions map answers to factor scores across sleep, cleanliness, food, smoking, guests, noise, work routine and budget. Core lifestyle factors carry double weight, preferences single weight, and any deal-breaker mismatch caps the total — so a 92 genuinely means day-to-day compatible. Browse views rank candidates by score with filters; each profile shows a factor-by-factor compatibility breakdown with the honest soft mismatches called out.

How it works

  1. A new user completes the 12-question lifestyle quiz; each answer maps to a 0–100 factor score across the lifestyle dimensions.
  2. Factor scores are weighted — core lifestyle factors double, preferences single — and any deal-breaker mismatch (e.g. smoking) caps the total at 60.
  3. The user publishes a listing with area, budget range and move-in date; the match profile completeness percentage drives how prominently it ranks.
  4. Browse Matches ranks all candidates by compatibility score with filter chips for budget, diet, smoking, sleep, WFH-friendliness and area.
  5. Opening a profile shows the full compatibility breakdown: per-factor bars with explanations and the deal-breaker check calling out soft mismatches.
  6. The user sends a connect request; on acceptance, verified-profile chat unlocks with ID and college-email verification badges visible.
  7. When either side updates their quiz, all affected scores recompute and the ranking refreshes immediately.

Tech stack:

  • HTML5 · CSS3 · vanilla JavaScript (ES6)
  • Single-file front-end app (no build step)
  • browser localStorage persistence
  • SVG score-ring + bar components
  • Quiz state machine (12 steps)
  • Responsive CSS Grid/Flexbox layout
Parameter Value
App format Single-file web app, runs offline after download (design)
Data storage Browser localStorage; no server or install required for the demo
Seeded dataset 6 candidate profiles with full quiz answers in the demo
Quiz 12 questions across 8 lifestyle dimensions
Scoring Weighted 0–100; deal-breaker cap at 60 (documented method)
Filters Budget, diet, smoking, sleep, WFH, area chips
Multi-user Single-user demo; real matching service needs a backend (future scope)

Project features

  • [12-question lifestyle quiz] Sleep, cleanliness, food, smoking, guests, noise, work routine and budget are captured in a guided quiz with a progress tracker and a documented scoring method.
  • [Weighted compatibility scoring] Core factors (sleep, smoking, food) carry double weight, preferences single; any deal-breaker mismatch caps the total at 60, so high scores are trustworthy.
  • [Ranked match browsing] Candidates are ranked by lifestyle compatibility with match-score rings, filterable by budget, diet, smoking, sleep schedule, WFH-friendliness and area.
  • [Factor-by-factor breakdown] Each profile shows per-factor scores with plain-language explanations (both early risers, 11 PM – 6:30 AM) and a deal-breaker check with soft mismatches named.
  • [My listing management] Users publish their own listing with area, budget range and move-in date, and see their match-profile completeness driving visibility.
  • [Verified-profile chat] Connect requests and chat are restricted to ID-verified, college-email-verified profiles with mutual connections shown, keeping the social layer safer.
  • [Score recomputation] Scores recompute instantly when either side updates their quiz, so the ranking always reflects current answers on both sides.

What is included

  • Complete RoomSync web app source code (single-file HTML/CSS/JS)
  • Seeded demo dataset (candidate profiles with quiz answers, listings)
  • Matching-algorithm documentation (weights, deal-breaker rules, worked example)
  • Project report PDF (background, scoring methodology, data model, screenshots)
  • PPT presentation for final review
  • Viva Q&A preparation document
  • User manual
  • Installation/deployment guide

Limitations & prerequisites

  • Compatibility scores model lifestyle fit from quiz answers — they are a screening aid, not a guarantee of a good living relationship.
  • The demo runs single-user with seeded profiles; a real service needs user accounts, verification infrastructure and moderation (future scope).
  • Verification badges are demo representations; real ID/college-email verification needs backend services.
  • Scores are only as honest as the quiz answers; the app cannot detect misrepresentation.
  • The app does not handle payments, agreements or broker interactions — it introduces compatible people.

Frequently Asked Questions

How does the compatibility score actually work?

Each quiz answer maps to a 0–100 factor score. Core lifestyle factors — sleep, smoking, food — carry double weight; preferences like music and guests carry single weight. Any deal-breaker mismatch, such as smoking, caps the total at 60 regardless of other factors. The method is documented in the app itself, and scores recompute instantly when either side updates their quiz.

Why cap the score on deal-breakers instead of just lowering it?

Because some mismatches are not compensable. A 95 on cleanliness does not fix a smoking deal-breaker for a non-smoker. The cap guarantees that a high score really means day-to-day compatible, which is exactly the trust the app is selling.

How is this different from a flat-listing site?

Listing sites show rooms; RoomSync matches people. Filters are lifestyle-first (sleep schedule, diet, smoking, WFH-friendliness) rather than price-and-area-first, and every candidate carries a scored, explainable breakdown instead of just photos and a phone number. The deal-breaker check goes further than any listing filter: it refuses to hide a fundamental mismatch behind an otherwise attractive profile.

What keeps the platform safe?

Connect requests and chat are restricted to verified profiles — ID verified and college-email verified — with mutual connections shown before contact. The demo represents this as a profile-trust layer; a production build would add reporting and moderation.

Is this project suitable for a final-year project?

Yes — for Computer Science, IT and Web Development programs. It combines a documented scoring algorithm, quiz state management, ranked search with faceted filters, profile trust design and a genuinely relatable user problem, giving the student both a solid codebase and a strong viva story. Suitable for B.E./B.Tech final-year projects in Computer Science, IT and Web Development.

Components & software requirements
  • HTML5 · CSS3 · vanilla JavaScript (ES6)
  • Single-file front-end app (no build step)
  • browser localStorage persistence
  • SVG score-ring + bar components
  • Quiz state machine (12 steps)
  • Responsive CSS Grid/Flexbox layout
Delivery information

Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.

Support terms

Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.

Download abstract (PDF)

Related guides

All guides
Technical illustration of a cloud server pushing event envelopes outward to web application endpoints for payments, dashboards and chat.Web development and IoT students who have built a REST API or an ESP32 project and now need external services (payments, GitHub, messaging) to notify their app when things happen

Webhooks Explained: Receive Data from Payments, GitHub and IoT

A webhook lets a service call your server the moment an event happens — payments, code pushes, form submissions. This guide explains the event anatomy, HMAC signature verification, the fast-acknowledge reliability pattern, local testing, and how webhooks compare with polling, WebSockets and SSE.

Read guide
Illustration of Docker Compose orchestrating a full-stack application with frontend, API, database, and cache containers connected in one network.B.E./B.Tech Computer Science and IT students whose full-stack projects need a frontend, backend, and database running together and are tired of setup instructions that only work

Docker Compose for Full-Stack Projects

Stop juggling four terminals and setup docs that only work on your laptop. This guide builds a complete Docker Compose stack — frontend, API, database, cache — with annotated config, healthchecks, persistent volumes, and a dev/prod split that survives demo day.

Read guide
Illustration of a web page with a comment section: a shield filtering user input so scripts are neutralized into harmless text before rendering in visitors' browsers.B.E./B.Tech Computer Science, IT and Web Development students building web applications with user-generated content: comments, profiles, forums, dashboards

XSS Attacks Explained for Students

Cross-site scripting turns your comment section into code running in visitors' browsers. Learn the three XSS types conceptually, why browsers execute injected input, what it enables, and the defender's toolkit: output encoding, Content Security Policy, safe DOM handling, and hardened cookies. No payloads — prevention only.

Read guide
Get a quotation