Appearance
Calendar & Sync
forcePomo keeps different kinds of data in different places. Google sign-in is optional, but it unlocks Calendar-backed history and cross-device continuity.
What Is Stored Where
- Local device: timer state, check-ins, a cache of commit history, preferences, and projects. Settings can also be exported to a file.
- Google Calendar: completed commits from signed-in sessions. These events are the shared long-term history.
- Private Google Drive app data: signed-in preferences, projects, current-session state, and up to 30 settings backups.
Google Calendar
On the first signed-in commit, forcePomo looks for a calendar named forcePomo. If none exists, it waits for three to five seconds, checks again, and then creates one. This second check reduces duplicate calendars when the web app and Chrome extension start at nearly the same time.
Each commit creates or updates a 25-minute event for the focus block. The event contains the selected project, optional memo, and a #forcePomo marker. The app reads those events to rebuild history and calculate streaks.
If more than one forcePomo calendar exists, clients choose the same one deterministically. Empty duplicates may be removed; non-empty calendars are preserved and included when history is read.
Connection required for Calendar writes
The timer and local history work offline, but a Calendar write attempted without connectivity is not guaranteed to upload later. Reconnect before committing when the Calendar event matters.
Google Drive Settings Sync
Preferences and projects are stored in Google Drive's private app data folder. New changes carry a per-setting logical timestamp, so changes from multiple devices normally converge automatically to the latest value for each setting. Legacy conflicts without that metadata may still ask you to choose values per setting.
forcePomo creates hourly settings backups and safety backups before import or restore. You can also create a backup manually. Up to 30 versions are retained.
Current Session Sync
The current or immediately previous check-in and commit state is stored separately from preferences. While forcePomo is open, signed-in clients poll for changes at intervals of up to 15 seconds and also refresh on launch, window focus, visibility return, and network recovery.
This sync covers the active workflow, not the complete commit archive. Google Calendar remains the shared record for completed signed-in sessions.
Using More Than One Client
The web app and Chrome extension can use the same forcePomo calendar when both are signed in to the same Google account. They use separate local storage and authentication sessions, so a brief delay before changes appear is expected. Use Sync Calendar or return focus to the app to refresh history.