Contact person: Business Client

Phone:Show

Email:Show

Location: Pullman, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I am looking for an experienced Full-Stack Developer or team to build a comprehensive medical question bank web application with advanced analytics for student performance. The project involves creating a Student Dashboard, Admin Panel, Stripe integration, and analytics features. I will provide a reference website to emulate and a detailed technical document (190 pages) outlining all required features. The system will include a Student Web App, Admin Web App, Backend API, and Background Workers in a unified monorepo. The product features a QBank with various question types, a quiz builder and player, study tools (notes/highlights/flashcards), analytics (including answer-change analysis), subscriptions/entitlements via Stripe, admin content workflows (including essay grading), notifications, and “study together/study partners” features.

This is a serious production build: server-enforced access control, server-recorded important actions (answers, changes, timing, notes, notifications), and deterministic quizzes (storing the ordered question list for shared/study-together functionality).

**What You Will Build (High-Level Modules)**

1. **Core Architecture**
- One codebase/coherent system containing:
- Student web app
- Admin web app
- Backend API
- Background worker(s) for queues/jobs
- API-first with versioned endpoints (e.g., /api/v1/...) and documented request/response schemas.
- Deterministic quiz blueprints: the backend persists the exact ordered list for each quiz/exam attempt.
- Server-authoritative timers (total time + time-per-question), refresh-safe, device-safe. Auto-submit must be server-side.

2. **Authentication + RBAC**
- Registration/login with email/password + Google OAuth
- Password reset flow
- Session management
- RBAC roles: student, editor, evaluator, admin + fine-grained permissions

3. **Subscriptions, Payments, Entitlements (Stripe)**
- Multiple plans (Course A, Course B, combo), duration-based access
- Stripe Checkout + webhook-based fulfillment (idempotent, signature verification)
- Backend middleware enforcing entitlements on every protected action
- Admin override: comp access, extend end date, etc.

4. **Student Dashboard Shell (Responsive)**
- Responsive layout (desktop sidebar + mobile drawer)
- Global notifications bell + unread count
- Course selector, profile/settings, global search (questions/notes/flashcards/library)

5. **QBank Core + Question Types + Content Workflow**
- Must support question types:
- MCQ (single best answer)
- Essay (human evaluated workflow + ideal answer option)
- Practical/image-based questions (with zoomable images; answer type can be MCQ/short/essay)
- Must support:
- Tag/taxonomy: course → Species/subject/system/topic/subtopic
- Question lifecycle: draft → review → published → archived
- Mandatory versioning: editing a published question creates a new version; attempts keep referencing the version seen.

6. **Quiz Builder + Quiz Attempt System**
- Two entry points:
- Generate Quiz (filters + settings → deterministic ordered list)
- Study-Based (curriculum-ordered navigation)
- Key requirements:
- Tutor vs Exam mode
- Timed vs Untimed + (optional) per-question timing
- Reveal rules (standard vs instant reveal on select, where applicable)
- “Study together” share code uses the stored blueprint/ordered list

7. **Quiz Player + Study Tools (Critical UX)**
- Autosave answers/timing state; refresh-safe resume
- Mark/flag questions; issue reporting (auto-attaches context)
- Highlight tool + eraser mode to remove highlights
- Create flashcard from highlighted text
- Notes + Notebook linked to question_id and attempt_id
- Anti-copy deterrents (disable easy copying, watermark overlay, log suspicious events)

8. **Analytics + Comparisons (Including Study Partners)**
- Analytics hub must include:
- Overview, trends, breakdown drilldowns (Species→Subject → System → Topic → Subtopic)
- Timing analytics and answer-change analysis
- “Test Analysis” includes: full analysis + notes taken during test + shared question list component
- Clicking charts opens filtered question list + supports “Practice this topic” quiz creation

9. **Study Partners Feature (Consent + Privacy Model)**
- Each user has a Study Partner Code they can share
- Partner request flow (name/email/phone), approve/decline (mutual consent)
- Comparison pages can filter: “Only my study partners”
- Ability to remove/block partner and rotate code
- Privacy toggles for what is shared (scores only vs topic breakdown; optional contact visibility)

10. **Notifications System (Admin + System-Generated)**
- In-app notifications with unread count, “wide message viewer”
- Admin can send to one user or large segments
- Large sends must be queued/batched (no looping user-by-user in a single request)
- System notifications triggered by events (e.g., essay graded) with deduplication keys

11. **Admin Panel**
- Question CRUD (all types), tagging, publishing/version history
- Essay grading queue for evaluators/admin (grade + feedback + notify student)
- Users management + RBAC
- Subscriptions/entitlements management
- Reports inbox (“report issue” triage + deep link to question/version)
- Notification composer + history/stats

12. **DevOps / Production Readiness**
- dev/staging/prod environments (separate DBs + Stripe keys)
- CI/CD (lint, type-check, tests, migrations validation)
- Postgres + migrations; DB constraints & indexing; soft-deletes where needed

**Preferred Tech Stack**
- Preferred: TypeScript end-to-end ([login to view URL] for web + NestJS/Express API), PostgreSQL, background jobs/queues, object storage for media (S3-compatible), and a clean OpenAPI/typed contract approach.
- If you propose Django/DRF or another stack, you must still provide strict API contracts (OpenAPI) and match the system constraints above.

**Deliverables (What “Done” Means)**
- Working production-grade system (student app + admin app + API + worker)
- Postgres schema + migrations
- Stripe checkout + webhooks fully tested in staging
- Deterministic quiz blueprints + resume-safe attempts
- Analytics hub with drilldowns and answer-change analysis
- Admin panel with content workflows and essay grading
- Deployment pipelines + documentation (setup, env vars, runbooks)
- Basic automated tests for critical flows (auth, payments, quiz attempt lifecycle)

**Suggested Milestone Plan (Freelancer-Friendly)**

- **Milestone 1 — Foundation**
- Repo setup, environments, CI/CD skeleton
- Auth + RBAC + entitlement middleware
- Base UI shell (student + admin)

- **Milestone 2 — QBank MVP**
- Question model + admin CRUD + publishing/versioning
- Generate Quiz + deterministic blueprint storage
- Quiz player MVP (MCQ, tutor/exam, autosave/resume)

- **Milestone 3 — Payments + Gating**
- Stripe checkout + webhook fulfillment + billing pages
- Admin subscription overrides

- **Milestone 4 — Study Tools + Reporting**
- Notes/notebook, highlights + eraser, flashcard creation from highlight
- Report issue flow + admin report inbox

- **Milestone 5 — Analytics + Study Partners**
- Analytics hub + answer-change analysis + drilldowns
- Study partners (code, request/approve, privacy controls, compare)

- **Milestone 6 — Notifications + Hardening**
- Admin broadcasts + event-triggered notifications
- Performance tuning, logging/monitoring basics, polish

(You can propose a different milestone breakdown—just map it to the modules above.)

**Payment Terms**
- Fixed price preferred (open to reasonable offers)
- Milestone-based payments:
1. Wireframe and design approval
2. Core system: login, question bank engine
3. Admin panel and dashboard
4. Payment integration and deployment

**Ideal Candidate / Team**
- Experience with educational or test-prep platforms
- A solid portfolio with similar projects
- Capable of handling UI/UX, backend, and deployment
- Clean, maintainable code and strong communication

**Timeline**
- Expected launch within 1 to 2 months

**To Apply, please include:**
- Links to similar platforms you’ve built
- Your preferred tech stack
- Fixed quote and estimated delivery time
- Any questions or technical suggestions" (client-provided description)