Study Bot

A study planner that runs the kind of session research says works. That’s rarely the kind that feels productive.

The Confidence section at the end of a Study Bot session. Confidence matched the result on 6 of 7 rated questions. 1 answer marked Sure wasn’t fully correct, so it comes first in error repair. A chart shows how often answers were right at each level: no answers were marked Guessing, 67 percent of the 3 marked Unsure were right, and 75 percent of the 4 marked Sure

The numbers

5study modes
3confidence levels, picked before you check each answer

Clips

Starting a session from Home. The side rail and top bar slide away, and the font’s roundness axis turns from 0 to 100, so a session looks different from the rest of the app.
On a phone. A wrong answer marked Sure gets a confident error note. Then a repair question: you type your answer, say how sure you are, and score it against the correction rule you wrote after the first miss.

Why I built it

Generic flashcard apps treat every topic, and every student, the same. They don’t know which concepts you’re shaky on, when you’re free, or what your professor spent 20 minutes on last week. I wanted a planner that knew all three.

What I decided

  • Five modes, each based on the research. They’re retrieval, interleaved practice, exam simulation (answer everything, then score it), error repair and worked examples. The repository’s learning science notes cite 44 references. They explain the research behind each principle, how the app uses it and where it stops helping.
  • Rate your confidence before you see the answer. Before anything is revealed, you say how sure you are: guessing, unsure or sure. A wrong answer marked sure gets a confident error note. Feedback fixes mistakes like that well at first, but they tend to return later. That’s why they come first in error repair. Like every miss, they stay open until you get them right on two different days. The end screen shows where your confidence and your accuracy didn’t match.
  • No peeking. No hint, excerpt or answer reaches the screen until you’ve answered. The server enforces that, and an end-to-end test checks it.
  • Put the plan on your calendar. The week’s plan downloads as a calendar file or goes straight to Google Calendar.
  • Every step of answering works from the keyboard. My goal for the redesign was level AA of the Web Content Accessibility Guidelines (WCAG) 2.2. The browser tests run axe, an automated accessibility checker, against the guidelines’ A and AA rules.

Screens

A multiple-choice repair question asking which selector wins when three rules color the same link. It was answered wrong and rated Sure. The chosen answer, .menu .link, is red with a cross, and the right one, #nav a, is green with a check. Under the confidence buttons is a confident error note, partly covered by the red Incorrect bar that shows the correct answer
Marked sure, and wrong. That’s a confident error, so the question comes back on another day.
A repair question asking what the sizes attribute tells the browser when it picks an image from srcset. Below it are the typed answer, the correction rule written after the first miss with three points to check, and buttons to score the answer correct, partly correct or incorrect
A miss from an earlier session comes back as a repair question, and you score it against the correction rule you wrote then.
The study plan for INFO 1300 Prelim 2, with buttons to reschedule sessions and export a calendar file. Progress shows 6 of 11 sessions done, 1 missed and 4 scheduled. Below are a missed error repair session with its own Reschedule button and today’s retrieval session with a Start session button, each with its time, length and topics
The Reschedule sessions button moves whatever you missed and shows you the new times before anything changes. A missed session also has its own Reschedule button.

The October redesign

In July, Study Bot’s home screen was a dark dashboard: session cards, a line of stats, achievements and a year of activity squares. I redesigned the app from 11 to 16 October, in 135 commits.

On the first day, 11 October, I worked on the old app. I moved it from Next.js 14, which had unpatched critical security advisories, to Next.js 16, tightened its security and fixed bugs that had been there since July. Connecting Google Calendar always ended on a page-not-found error. Plans used the server’s clock, so a student in New York could get sessions four hours early.

Before I rebuilt Home, I compared five mockups of it.

Mockup 1, a lecture poster: a huge red 7 for the days until INFO 1300 Prelim 2, black type on off-white paper over a visible grid, a row of squares for the plan’s sessions, later exams in a column and a numbered list of weak spotsMockup 2, an exam timetable: a black header, today’s 2:00 PM retrieval session pinned at the top as the next departure, and the week as a timetable with days as rows and the four courses as columns, each course with its own colored dotMockup 3, a mixtape: the next exam drawn as a cassette tape’s paper insert in blue ballpoint, with the sessions left on side A and error repair on side BMockup 4, a full-screen feed: 7 days in huge white type on a black screen, with Start session, Plan, Weak spots and Chat stacked down the right like the buttons on a video feed, and the weak spots in a side panelMockup 5, the usual study app: a white sidebar, cards for four upcoming exams, weak spots with mastery bars, today’s retrieval session with a blue Start session button, and the next sessions in a table
A lecture poster, an exam timetable, a mixtape, a full-screen feed, and the usual study app with a sidebar and soft cards, all showing the same made-up week. I went with the last one because it’s the plainest, so nothing on the screen competes with the exam countdowns and the mistakes still to fix. Then I made it look like a Google app.

On 12 October I built the design system before touching a screen. The colors come from Material 3, Google’s design system, and study sessions get a palette of their own. The type is Google Sans Flex. A page that only runs in development shows every color pair with its contrast measured live.

On 15 October I rebuilt the screens. A session now works like a Duolingo lesson, with one question per screen and a sheet that slides up after each answer. The new session screens also fixed a bug from July: feedback on a session’s last answer never showed, because the end screen replaced the question as soon as the server marked the session done.

Before, July 2026: the old dark Dashboard, with a top bar of Dashboard, Learn, Plan and Settings, two retrieval session cards for today, a New Plan button, an Achievements heading and a year of activity squares, with my own numbers blanked. After, October 2026: the new light Home, with a navigation rail, countdown cards for four exams starting with INFO 1300 Prelim 2 in 7 days, unresolved errors by course with Repair buttons, and today’s retrieval session with a Start session buttonBefore, July 2026: the old review after a wrong answer marked sure, as dark panels stacked under the question: a high-confidence miss note, the right answer with why the wrong pick was tempting, and a passage quoted from the course notes, above a Next Prompt button. After, October 2026: the wrong answer card in red, the right one in green, Sure selected, a confident error note and the red Incorrect bar with a Next question button
Before, July 2026, and after, October 2026: Home, then a wrong answer marked Sure. I blanked my own results on the July dashboard. The October screens use the demo account’s made-up data.

Status

Study Bot runs locally with a demo account, and there’s no public build yet. The session engine, the modes, the search over your files and the planner have unit, integration and browser tests.

Rate it before you check

Try three questions from the app’s demo course. Pick an answer, then say how sure you are before you check it.

Question 1 of 3CSS specificity

A link sits inside <nav id="main"> and has the class active. Which rule sets its color: #main a { color: navy } or .nav .links a.active { color: red }?

How sure are you?

Optional. Rate before you check.

Checking an answer needs JavaScript.

Error repair

Your next Error repair session asks these in this order. Misses you marked Sure come first.

No misses yet. A wrong answer lands here.

Each one stays until you get it right on two different days.

This runs in your browser. The questions and the wording come from the app, and the list orders misses the way Error repair does. In the real app the server grades your answer, and a miss also gets a repair question at the end of the same session.