A real user, a real recurring workflow.
Language learning takes place over months and years. As my own Japanese study developed, I wanted a way to coordinate a long-term curriculum without losing the nuance of individual study sessions, immersion activities, vocabulary discoveries, or changing priorities.
The system grew around recurring study needs: quick capture, phase-aware scheduling, meaningful feedback, and reliable handling of synchronization and dates.
A connected study system.
The implementation organizes learning around Google Sheets and modular Google Apps Script functions, with custom sidebars for fast interaction and integrated services for planning and follow-through.
Record the actual work.
Study sessions, kanji and vocabulary, resources, difficulty, tags, and long-form media immersion enter structured phase-specific logs.
Make progress visible.
Dashboard calculations cover learning streaks, study hours, session averages, completion, resource use, and recurring patterns.
Coordinate what comes next.
Phase planning supports Google Tasks and Calendar synchronization; companion routines handle Anki CSV export and progress-report emails.
How I built it.
Its modular Apps Script implementation covers logging, planning, analytics, interfaces, synchronization, export, and routine maintenance. The working components include:
- Learning capture: structured session and vocabulary loggers, plus a season logger for extended media study.
- Analysis: metrics for streaks, progress, study time, tags, resource use, and session characteristics, written into a dashboard.
- Integration: phase-aware task and calendar creation, duplicate checks, chunked operations, and task-completion reconciliation.
- Output: downloadable Anki-compatible vocabulary CSV and daily/weekly email-report functions.
- Usability: custom menus, themed Sheets layouts, bilingual help content, system guidance, and recovery tools.
Scheduling routines support Google Tasks and Calendar workflows; automatic trigger registration is currently disabled. The system remains a personal study platform.
What I learned from building it.
The objective was a dependable daily learning workflow rather than another dashboard. Structured data, custom interfaces, Google integrations, and iterative personal use all shaped the implementation.
Reconciliation, timezone handling, rate-aware batching, reporting, and recovery utilities became just as important as the visible features.