Hannah covered the load, and it's fine. What I'd check before Monday is the write side. One row per answer in reviews is no problem for 200 students, but make sure the insert policy ties the row to the student. If it's with check (true), one curious student with devtools can write reviews for the whole class, and with teenagers someone will try.
create policy "own reviews" on reviews for insert
with check (user_id = auth.uid());And do a dry run on Friday: open the app in five browser profiles and click through at the same time. It won't test load, but it finds the login and session bugs that only show up with more than one account, which is what usually breaks on day one.
reviews(user_id), and whether each card view fetches the whole deck.