Contact person: Lightweight Quiz App Development

Phone:Show

Email:Show

Location: United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I want to spin up a stripped-down, browser-based quiz application that keeps the tech stack light but the user flow solid. Visitors will create an account with a standard email-and-password signup, log in, and see a clean interface that serves text-only multiple-choice questions.

Core flow
• Authentication: secure email/password registration and login, basic password-reset flow.
• Quiz engine: loads a set of text questions, shows one at a time with a visible countdown timer, records the selected answer, locks it in when time expires, and advances automatically.
• Scoring: tally correct answers immediately after the quiz, show a concise results screen, and store each attempt.
• Reporting: an internal dashboard or downloadable CSV that breaks down individual user performance—score, time taken, date—so I can track learning progress. No broader usage stats are required.

I’d like the UI to stay minimal and responsive; vanilla HTML/CSS, a lightweight framework such as React or Vue, or even plain JS is fine as long as it’s maintainable. The backend can be equally minimal—Node/Express, Flask, or similar—just enough endpoints to handle auth, questions, and result storage. Data can live in a simple SQLite, PostgreSQL, or even JSON file if you can justify it.

Deployment should work on a standard cloud host (Heroku, Vercel, Render, etc.). Please structure the code so I can drop in new question sets (preferably via a JSON file or an admin textarea) without redeploying.

Acceptance criteria
1. User can sign up, verify email/password login, and reset a forgotten password.
2. Questions render cleanly with a countdown timer; timeout locks the answer.
3. Score and correct/incorrect breakdown appear instantly after completion.
4. Each attempt is stored and reflected in a user-level performance report downloadable as CSV or viewable in the dashboard.
5. Code is commented, environment variables are documented, and a one-command deploy/readme is included.

Let me know the stack you prefer, an estimated timeline, and any third-party services you plan to use so I can green-light them before we start." (client-provided description)