The stress isn't always the material.
People close to me are in medical school. Being in their corner through it, I have watched what the planning overhead alone does to a person. The stress is not always about the material. A lot of the time it is about feeling like you are never organized enough, never on top of it.
I am not a medical student. So I did not try to build a better study guide. I built the thing I actually understood: a way to remove the organizational chaos so they could just focus on learning.
Answer the question that comes before "what to study."
Most study tools for medical students are content tools. They tell you what to study. Rotaset answers the question that comes before: when do I study what, given everything else going on in my life right now. The output is specific enough to be immediately useful: not "study cardiology" but "UWorld, Cardiology, 40 questions timed."
Six decisions that shaped the product.
Scheduling philosophy
The scheduler does not just block time. It takes in exam type, difficulty, weeks until the exam, available study hours, block style preferences, sleep and wake times, workout days, and existing Google Calendar events to generate a conflict-free daily plan grounded in spaced repetition science, cognitive load theory, and attention restoration research. The result is a plan that accounts for how the brain actually works, not just how many hours are available.
No-exam fallback
Students without upcoming exams still get a daily schedule. Rather than blocking on an empty state, Rotaset defaults to a general review mode so the product is useful from day one, not just in the weeks before a high-stakes exam.
Auth and calendar decisions
Google OAuth handles signup and calendar permission in a single flow. Apple Sign In was added for iOS-native trust. One detail that required real thought was Apple's private relay email flow, where users who choose to hide their email get an anonymized address. That had to be handled explicitly so it did not break account creation. iCal was added as a secondary calendar path for students whose schools publish iCal feeds, with a guided in-app walkthrough because dropping users into that setup without support would have created friction at a critical moment.
Anki integration built for both user types
The SM-2 spaced repetition algorithm is built directly into Rotaset so students get Anki-aware scheduling without any setup. For power users who want live deck sync, AnkiConnect API access is available in settings without getting in the way of the default experience.
Rebrand mid-build
Rotaset shipped originally as Velum and was rebranded mid-development. That meant a full DNS migration, OAuth consent screen updates, and environment variable changes across all environments. It went live without downtime. Worth mentioning not because it was glamorous but because managing that kind of change cleanly while continuing to ship is what working in a real product environment actually looks like.
Assessed and documented before launch.
Rotaset does not collect health data. User data is limited to study schedules, exam dates, and calendar events. HIPAA non-applicability was explicitly assessed and documented before launch.
Google Calendar access uses read-only scope, nothing broader than what the feature requires. Row Level Security is enabled on all Supabase tables, auth tokens are stored server-side, and VAPID keys for push notifications live in environment variables.
Legal pages shipped at launch covering GDPR, CCPA, and FERPA given the student user base. Consent is recorded to Supabase with version tracking.
Close the loop on what was actually completed.
A progress layer. Rotaset generates the schedule but does not close the loop on what was actually completed. The next version would let students log sessions, surface patterns over time, and use that data to improve future schedule generation.
Two things that shaped every decision.
Start with what you actually understand. I am not a medical student. So I focused on the part of their problem I had watched up close and knew I could solve.
The right question for Rotaset is not how many schedules were generated. It is whether the person who used it felt less overwhelmed opening their laptop the next morning.