A practical look at the architecture, tradeoffs, and engineering decisions behind QuickMark's interactive exam-practice platform.
Past papers are the backbone of exam preparation, but the workflow around them is usually fragmented. Students often jump between PDFs, answer sheets, notes, and separate tools for tracking progress.
QuickMark was built to reduce that friction. The goal was simple: keep practice, feedback, and progress tracking in one place so revision sessions become more consistent and easier to repeat.
For most IGCSE, O Level, and AS and A Level students, the hard part is not finding questions. The hard part is building a reliable loop. If any step is slow, students skip it.
Keep interactions fast so students complete full practice loops.
Keep state reliable so attempts and progress are not lost.
Keep real-time flows consistent in ranked sessions.
Keep the system modular so full-paper and topical modes can evolve independently.
One of the biggest design choices was where PDF handling should happen. We process question extraction in the browser using PDF.js. This keeps the interaction immediate and avoids introducing extra upload-processing latency.
Next.js App Router, React, TypeScript
Fastify, Node.js, Prisma
Durable Records
High-Speed Coordination
Ranked play needs strict consistency. Two players should see coherent match state even if their network conditions differ. Socket-based events are used so the server can coordinate key transitions.
Fast experiences only help when they are reliable. Reliability is not a single feature; it is a collection of small safeguards across the full session lifecycle.
No architecture choice is free. We accepted a few deliberate tradeoffs to prioritize learner experience.
Client-heavy interactivity increases implementation overhead.
Real-time features require rigorous design and observability.
Multiple data systems improve performance but add operational complexity.
QuickMark is designed as an exam-practice system first, not just a paper viewer. The architecture prioritizes speed, consistency, and repeatable feedback.
Students do better when the loop practice → review → fix is easy to repeat. Our technical decisions are built around protecting that loop.
Start a short focused session and review every mistake before your next paper. Consistency compounds quickly.
The twelve hours before your exam matter more than most students realise. Here is a practical, calm guide to your evening routine, what to avoid, and how to arrive ready.
Stop guessing what to revise. Your QuickMark Reports page gives you a full breakdown of wrong answers, skipped questions, and weakest topics so you can plan next week with data instead of instinct.
Turn mark schemes into actionable revision: log what matters, spot recurring errors, and choose your next study session with a concrete 20-minute workflow.