Statistics
The Statistics page displays SpringNote's usage records, note counts, desktop widget timer results, and AI model usage. The page data falls into two categories: note counts are read from the current note directory; usage counts, timer earnings, and model usage come from statistical records saved during application runtime.
Statistics Range
The top of the page allows selecting the statistics range:
- All: Aggregates from the start of historical statistics to today, showing dates with data.
- Last 30 days: Includes today and the previous 29 calendar days.
- Last month: Covers the first through the last day of the previous calendar month.
- Last quarter: Covers the complete calendar quarter before the current quarter.
- Custom: Select a start and end date; statistics cover the calendar days between them.
Both the start and end dates are included in the range. After switching the range, the annual heatmap retains its one-year display; the overview and usage trends recalculate according to the selected range.
Annual Heatmap
The annual heatmap displays daily activity counts for the last year. Dates are arranged left to right by week and vertically by day of the week. Color intensity indicates daily activity:
- 0: No activity;
- 1–2: Low activity;
- 3–4: Medium activity;
- 5–7: High activity;
- 8 or more: Very high activity.
Activity counts come from successful home page content organization events and edit completion events. Launching the application, opening pages, browsing existing notes, or simply starting the desktop widget do not increase heatmap counts. Hovering over a date cell shows the date and its corresponding activity count.
The heatmap tracks application activity events, not daily note file counts, word counts, or AI token counts. If a daily note exists on a given date but no statistical events occurred, that date may still show zero.
Overview
Each number in the overview corresponds to the currently selected time range:
Total Generations
The number of successful home page content organization events. A maximum of 10 per day; generations beyond 10 do not increase this metric. This counts successful events, not the number of columns displayed on the home page or daily note files.
Edit Completions
The number of successful AI edit completions. Failed, cancelled, or effectively empty completions do not increase this metric.
Total Notes
The total number of daily, weekly, and monthly notes within the statistics range. This is the sum of the three categories and does not represent input records beyond Markdown file counts.
Daily / Weekly / Monthly Counts
The number of Markdown notes matching the corresponding file rules within the current range. Daily notes are counted by file date; weekly and monthly notes by their coverage date range. Therefore, weekly or monthly notes spanning the range boundary may be counted as long as their coverage falls within it.
After deleting or adding note files, the file counts are re-read only when the statistics page is reloaded. Whether a file's content is empty does not affect the count, as long as the file matches the corresponding type and date rules.
Input Tokens
The number of input tokens sent to the provider with model requests, typically including the prompt, context, and current input. This reflects the request size and is not equivalent to the user's character count.
Output Tokens
The number of output tokens generated by the model's response. Streaming responses are counted after the request completes and usage information is received.
Cached Tokens
The number of cached input tokens returned by the provider. If the provider does not provide cache usage, this value is zero; zero does not indicate request failure.
App Launch Count
The number of application launch events. When "All" is selected, this is compatible with launch counts saved by older versions. When a limited date range is selected, only launch records that can be attributed to specific dates are counted.
Work Duration & Earnings
Work duration comes from the desktop widget's accumulated timer. Earnings are calculated from the same timer based on current configuration. Accumulated portions are committed on pause, stop, or application exit. Brief unsaved timer data from abnormal exits may not be included in statistics.
Earnings are an in-app estimate and do not represent actual salary or real income. Modifying configuration such as hourly wage only affects future timer calculations; it does not recalculate already-saved historical statistics.
Usage Trends
Usage trends display model token usage by date within the current range. The bar height for each day scales relative to the maximum token count in the current chart; bars are segmented by provider.
Hovering over a date with usage shows:
- The date;
- Total tokens for the day;
- Input, output, and cached token breakdown, or provider token breakdown;
- Token counts for major providers.
The legend shows the top 8 providers by usage; remaining providers are grouped as "Other". Provider usage is aggregated by provider name and model call date; multiple models under the same provider are consolidated into that provider's segment.
When no model calls are recorded, the trends area shows an empty state. Days with no token usage do not generate visible bars, but dates remain arranged according to the selected range. Under "All", the chart only expands on dates with actual usage records; under limited ranges, the full date axis is preserved.
Data Updates & Errors
Statistical records are written to the local data directory after events occur. Home page organization, edit completions, app launches, desktop widget timer, and model requests are each recorded separately; failure of one type does not prevent other features from working.
If the statistics file cannot be read, the statistics page shows empty results; this does not prevent note editing, app launches, or AI requests. Zero values in this case indicate that statistics were not obtained from the current read, not that historical data has been deleted.
If a model provider does not return token usage, that request may not appear in the usage trends. Failed requests are not counted as successful home page organizations or edit completions. If note files cannot be read, the note count may temporarily show zero, but actual note files are not deleted.
