Guides / How to build

How to Build a Quiz App

Build a quiz app that scores fairly: question types, a question bank, timers, results, leaderboards, and keeping answers hidden until someone submits.

Mythex Team · 2026-09-29 · 5 min read

A quiz app shows questions, collects answers, scores them and shows a result. The simple version — one fixed quiz, scored in the browser — takes an afternoon. The version people rely on for learning, hiring or competitions needs a question bank, answers kept on the server, saved attempts and fair timing. Decide early which one you are building, because it changes the architecture.

Decide what kind of quiz it is

The word "quiz" covers very different products:

A personality quiz with no stakes can safely run entirely in the browser. An assessment cannot. Live quizzes need real-time updates, which is a separate level of complexity — leave them out of version one unless that is the whole point.

What a quiz app needs

Data

• Quizzes — title, description, settings (time limit, attempts allowed, shuffle, pass mark, show answers after?).
• Questions — the quiz, the text, type, points, an optional image and an explanation shown afterwards.
• Options — the answer choices for a question, with which ones are correct.
• Attempts — who took which quiz, when they started and submitted, the score.
• Answers — which option (or text) the person gave for each question in an attempt.

Keeping attempts and answers separate lets you show people exactly what they got wrong and lets you spot questions nearly everyone misses — often a sign the question is badly worded.

Pages

• Quiz editor for the author: add questions, reorder them, mark the correct option, preview.
• Quiz start page with the rules: number of questions, time limit, attempts.
• Question screen, one question at a time on phones, with progress ("4 of 10").
• Results page with the score, pass or fail, and per-question feedback if the settings allow it.
• Author dashboard showing attempts, average score and the hardest questions.

Permissions

Authors create and edit quizzes; takers only take them. If quizzes are for a class or a team, add groups so people only see the quizzes assigned to them. See how to add login to your app.

Scoring rules to write down

Most quiz bugs are scoring bugs. Put these rules in your prompt:

1. Single choice: full points if correct, zero otherwise.
2. Multiple choice ("select all that apply"): decide between all-or-nothing and partial credit. If partial, do wrong picks subtract points? Write an example: "Correct options A and C. Choosing A only scores 1 of 2. Choosing A, B and C scores 1 of 2."
3. Unanswered questions score zero and are shown as unanswered, not wrong.
4. Time limits are enforced on the server using the start time. A browser timer is only a display — anyone can pause or change it.
5. Shuffling changes the order shown, never which option is correct. Store the correct option by its ID, not its position.

Keep the answers off the browser

This is the one technical point every serious quiz app has to get right. If the page receives the questions with the correct answers and scores them itself, anyone can open the browser's developer tools and read the answer key.

The fix is simple to describe: the server sends questions without the correct flags, the person submits, and the server scores the attempt and returns the result. Say this explicitly in your prompt. For a fun quiz it doesn't matter; for anything with a certificate, a grade or a prize, it does.

A first prompt that works

Build a quiz web app. Authors log in and create quizzes with a title, description, optional time limit, number of attempts allowed and a pass mark. Each quiz has questions of type single choice, multiple choice or true/false, with points and an optional explanation. Takers open a quiz by link, see the rules, then answer one question per screen with a progress bar. The correct answers must never be sent to the browser before submission — score attempts on the server and enforce the time limit from the server-side start time. Multiple choice is all-or-nothing. After submitting, show the score, pass/fail and, if the author allows it, each question with the correct answer and explanation. Save every attempt and answer in a database. Give authors a results page with average score and the most-missed questions.

Build steps

1. Editor first. Create one quiz with ten questions of mixed types. If writing questions is painful, authors won't use the app.
2. Taking a quiz. Try it on a phone. Check progress, back and forward, and what happens on refresh.
3. Server-side scoring. Open the browser's network tab while taking the quiz and confirm no response contains the correct answers before you submit.
4. Scoring tests. Give the AI five worked examples with expected scores, including a partially correct multiple-choice answer and an unanswered question.
5. Timer. Start a timed quiz, wait past the limit, then submit. It should be rejected or scored as it stood at the deadline — decide which.
6. Results and analytics. Check the most-missed question list against attempts you made on purpose.
7. Extras. Only now add images, question banks with random selection, certificates or a leaderboard.

Common mistakes

• Answer key in the page. The most common and most serious flaw.
• Trusting the browser clock. Enforce limits on the server.
• Storing the correct answer as "option 2". Shuffling then marks the wrong answer correct.
• Editing a quiz after people took it. Changing a question changes the meaning of old scores. Lock quizzes with attempts, or version them.
• Unlimited retries on an assessment. Decide the attempt rule and enforce it on the server.
• Leaderboards with full names by default. Let people choose a display name, especially for students.

When a ready-made product is the better choice

If you need a quick classroom game, a quiz inside a course platform you already use, or a one-off lead-generation quiz, existing quiz and form tools are faster and often free. Learning management systems already include quizzes with gradebooks. See Typeform alternatives and Google Forms alternatives for the form-style route.

Build your own when the quiz is part of something bigger — a course you sell, a hiring flow, a training programme with your own rules — or when you need scoring, branding or data ownership the tools don't give you. Pair it with a flashcard app for practice, or put it inside an online course platform.

Building it with Mythex

In Mythex you describe the quiz app in chat and try it in the live preview, including a phone-sized view. The agent adds a database when you ask to save attempts, and writes the server-side scoring alongside the front end. For author logins, Mythex wires an auth approach you choose rather than a built-in sign-in product. If a change breaks the scoring, roll back to an earlier checkpoint and try again. Publish to a mythex.ai link, or your own domain on Pro.