Can a custom reading platform handle a whole year group at once?
Yes, and concurrency is the requirement to design for rather than discover. BVIS needed 300–400 students in quizzes simultaneously during class, so the architecture: Next.js, NestJS, MongoDB on AWS, was chosen for that peak rather than for average load.
How do you handle reading levels that do not match year groups?
With access logic that treats level and year as separate things. A student is granted quizzes by reading level, not by the class they happen to sit in, which is what lets a school stretch strong readers and support weaker ones inside one system.
What about copyright on the books themselves?
Book files are never publicly exposed. Access is authenticated and scoped per role, so the assessment content stays inside the school while remaining usable in a normal lesson.
Does a build like this save teachers time?
That is the main return. Assigning, collecting and marking reading assessments by hand is hours a week per teacher. Automating the mechanical part gives that time back to teaching, which is why we track it as an outcome rather than a feature.
Can it grow after launch?
It is designed to. The roadmap includes gamification, progress streaks, class leaderboards and achievement milestones, to turn reading practice into something students compete at rather than complete. See web app development.