Skip to main content
Back to projects
PokeDen icon

PokeDen

A student study workspace for subjects, assignments, notes, exams, and focused sessions, with an optional study companion.

Role
Web app development
Outcome
One connected path from planning academic work to starting a focused study session.
Stack
Next.jsTypeScriptReact
PokeDen banner

What it is

PokeDen is a student study workspace that brings subjects, assignments, notes, study plans, exams, and a Pomodoro timer into one web app. It is for students organizing their own academic work, rather than a school managing classes or grading students.

The main journey is knowing what needs attention, choosing what to study, starting a focused session, and checking preparation afterward. A Pokémon-inspired companion adds reactions, experience points, and evolution, but students can hide it or reduce its movement.

This case study covers the current web application. Academic data is saved in the browser, with Google sign-in and Supabase snapshot sync code for signed-in use. Those online flows were inspected in the source, not tested against a live service for this write-up.

The problem and the fix

The problem

  • Plans need a path into action

    A product goal, not an interview finding: connect academic planning to starting a study session

  • Academic records belong together

    Subjects, assignments, notes, and exams need shared context rather than repeated entry

  • Progress needs clear meaning

    Reviewed topics are not mastery, and completed breaks currently enter focus totals

  • Saved is not the same as synced

    Local save confirmation and cross-device availability need distinct, trustworthy feedback

The fix

  • Subject-centered workspace

    Related tasks, notes, plans, and exams share academic context

  • Plan directly into Pomodoro

    Starting a session retains its duration and linked academic work

  • Derived calendar

    Schedules, deadlines, plans, and exams supply the calendar's events

  • Local storage with an account layer

    Validated browser data and snapshot sync code exist; save feedback and live sync still need checks

What I did

  • Web app implementation for the subject-centered dashboard, tasks, planner, notes, exams, calendar, and settings.
  • Connecting planned study sessions to the timer while retaining subject, task, and exam-topic context.
  • Managing shared academic state, browser persistence, and data validation.
  • Integrating companion reactions, study rewards, and optional visibility and movement controls.
  • Connecting the local workspace to the application's Google sign-in and snapshot sync layer.

This write-up focuses on app-specific development built on an existing Next.js admin template. It does not claim the template was created from scratch, sole authorship of every component, or a formal student research study.

How I designed it

  1. 01

    Start with what needs attention

    The dashboard brings due work, classes, exams, and study suggestions into the student's daily view

    Priorities
  2. 02

    Keep academic context attached

    Subjects connect records, and planned sessions pass their links and duration into focus

    Continuity
  3. 03

    Offer a useful first action

    Setup and empty-state actions help students add subjects, tasks, and study plans

    Guidance
  4. 04

    Let students control the companion

    Visibility, movement, and reduced-motion preferences keep the playful layer optional

    Choice
  5. 05

    Treat design review as a starting point

    The supplied observations identify save, sync, and progress concerns; participant testing is still open

    Evidence

Main features

Subjects and assignments

Create subjects with class schedules, then organize tasks by subject, deadline, priority, status, and subtasks. Tasks can be completed or reopened, and subjects can be archived while retaining their related history.

Study planning

Plan a session with a subject, topic, date, duration, and optional task or exam-topic link. Starting the plan opens a focus timer with that context already attached.

Subject notes

Write rich-text notes with titles, tags, and optional academic links. Search, subject filters, pinning, and automatic saving support finding and continuing notes. Save feedback still needs care when browser storage fails.

Pomodoro and breaks

Start, pause, resume, stop, or reset focus and break intervals. The running timer uses elapsed clock time rather than relying only on screen updates, and completed intervals become activity records.

Exams and preparation

Track exam dates, review topics, plan topic sessions, and record results. Readiness is calculated from reviewed topics; it does not measure knowledge or predict an exam grade.

Dashboard and calendar

See due work, upcoming exams, class schedules, study plans, and activity summaries. Calendar events are derived from the underlying records rather than saved as a second independent set.

Optional study companion

Select a companion, earn study experience from supported activities, and unlock growth and evolution. Hide the companion or adjust movement and reduced motion without removing the academic tools.

Accounts and storage

Academic records are saved to browser storage. Google sign-in and authenticated server routes support sending and retrieving a workspace snapshot through Supabase. Live sign-in, cross-device sync, and recovery were not verified for this case study.

Tech Stack

  • Next.js 16 and React 19

    build the web screens, route navigation, and server endpoints for snapshot sync.

  • TypeScript

    defines academic records, shared actions, and timer and companion behavior.

  • Tailwind CSS 4 and shadcn/ui

    style the workspace and provide interface components.

  • Zustand

    holds shared academic state and actions across the app.

  • Zod

    validates academic data before browser persistence and incoming sync snapshots.

  • Tiptap

    provides rich-text note editing.

  • Browser localStorage

    saves the academic workspace and a previous valid snapshot for recovery.

  • Supabase Auth and database

    support Google sign-in and account-linked workspace snapshots through server routes.

  • date-fns

    supports date comparisons, calendar derivations, and daily and weekly summaries.

  • Biome

    provides source formatting and lint checks.

The app has both local persistence and online account code; it is not a local-only prototype. Dependency presence and source inspection do not prove successful deployment or reliable cross-device sync.

Hard parts and how I solved them

Keeping related views consistent
A deadline can appear in Tasks, a subject view, the dashboard, and Calendar. Shared academic records and derived calendar events keep those views connected without maintaining separate copies of the same event.
Moving from a plan into focus
Starting a planned session needs to preserve its purpose. The timer receives the plan's subject, topic-related references, duration, and linked task or exam so the activity remains connected to the original work.
Recovering timer time
A browser tab can pause screen updates or be reopened. The timer combines accumulated time with the difference between its start timestamp and the current clock. This supports recovery from delayed updates, though full interruption behavior was not tested here.
Making saved work trustworthy
Browser storage can reject a write, and saving locally is different from syncing online. The repository validates records and reports storage errors, but the note editor can still show Saved after an action that records an error in shared state. Background pushes also do not provide reliable visible sync confirmation. These remain limitations, not solved reliability claims.
Giving progress an honest meaning
Exam readiness counts reviewed topics, not mastery. Current daily and weekly activity totals also include completed break records, so focus labels can overstate study time. Separating focus from breaks is a proposed correction, not a completed change in this case study.
Syncing whole-workspace snapshots
The sync logic compares local and remote timestamps, with rules for a fresh workspace and deliberate resets. It chooses a whole snapshot rather than merging each record. Concurrent edits and failure recovery therefore need live checks before claiming dependable cross-device use.

How it works

  1. 1

    Set up the study workspace.

    Enter profile and study preferences, add subjects, and choose how visible the companion should be.

  2. 2

    Find work needing attention.

    Use the dashboard or open a subject to see assignments, class schedules, notes, plans, and exams.

  3. 3

    Turn work into a study plan.

    Choose a topic, date, and duration, with an optional task or exam-topic link.

  4. 4

    Start a focused session.

    Open the plan in Pomodoro, use the timer controls, and return to the associated work afterward. Companion reactions and rewards remain optional additions to the academic flow.

  5. 5

    Review preparation.

    Check tasks, reviewed exam topics, recorded activity, and the calendar. Treat readiness as a review checklist, and note that current focus totals also include completed breaks.

  6. 6

    Continue later.

    Local records are read back from browser storage. When configured, the account layer offers Google sign-in and snapshot sync, but live account and cross-device behavior were not exercised for this write-up.

Results

  • Source inspection confirms a connected academic workspace covering subjects, tasks, plans, notes, timers, exams, calendar views, and companion progression.
  • A planned session carries its academic context into the timer, and calendar entries are derived from shared records.
  • Browser persistence, validated snapshots, Google sign-in, and authenticated sync routes are implemented in the current source; live account and cross-device behavior were not tested for this write-up.
  • Known limitations include note-save feedback that can conflict with storage errors, silent background sync failures, and focus totals that include completed breaks.
  • The supplied manual QA checklist is unchecked. No completed student usability study, usage metrics, grade improvements, or productivity gains are claimed.
  • Portfolio content and rendering checks verify this case-study integration, not the study app's full behavior.

What I learned

What worked

  • Shared subject context connects planning, notes, deadlines, and focus without making them separate products.
  • Deriving calendar views from academic records reduces duplicated information.
  • Optional companion controls give the workspace personality without making study depend on animation.

What could improve

  • Make note-save feedback reflect confirmed persistence, with a clear recovery action when saving fails.
  • Show whether online sync succeeded, failed, or still needs another attempt.
  • Separate focused study time from completed breaks and explain readiness as reviewed topics.
  • Use PokeDen consistently; some account screens still use Pokademia.

Future checks

  • Observe students creating a task, planning focus, saving a note, and explaining their progress.
  • Test sign-in, simultaneous edits, storage failures, and cross-device recovery against the configured service.
  • Complete the documented manual QA journeys on phones and desktops before making release-readiness claims.
Next projectPawPinAn Android-first phone app for reporting stray animals with an exact location, so nearby rescuers can find them.Read the story
PawPin banner