Appearance
Platform & Data Notes
These constraints are part of how forcePomo stays predictable across browsers and devices.
Fixed Schedule
- Sessions cannot be manually started, stopped, paused, or resized.
- Focus begins at
:00and:30and lasts 25 minutes. - Check-in closes 15 minutes after focus starts.
- Commit remains available during the break and for the first 10 minutes of the next focus block.
Web App
The web app runs in a normal browser tab. Browsers may throttle or suspend background tabs, but forcePomo recalculates the correct phase when the page becomes active again. Audio may require an initial click or key press because of browser autoplay rules.
Browser notifications require permission. Web Push can deliver a scheduled focus-end notification when supported and configured, but delivery can still be affected by browser, network, battery, or operating-system policies.
Installed PWA
The PWA uses the same web implementation and data model in a dedicated window. Installation can make forcePomo easier to keep open, but it does not remove all browser background or notification restrictions.
Chrome Extension
The extension lives in Chrome's side panel. A background service worker and chrome.alarms maintain timer transitions, an offscreen document handles audio, and the toolbar badge displays remaining time.
Chrome can still suppress sound or notifications because of system mute, Focus mode, permissions, or browser policy.
Google Calendar
- Google sign-in and network connectivity are required for Calendar writes and Calendar-backed history.
- forcePomo creates or reuses a dedicated calendar named
forcePomo; it does not write commits to your primary calendar. - The requested Google scopes let forcePomo list calendars and manage the calendar and events it creates. It does not edit unrelated calendar events.
- A local commit can succeed while its Calendar request fails. Calendar upload is not currently guaranteed to retry automatically.
Google Drive Sync
- Signed-in settings and projects sync through private app data in Google Drive.
- Per-setting logical timestamps resolve current changes automatically; legacy conflicts may require a manual choice.
- Up to 30 automatic, manual, pre-import, and pre-restore settings backups are retained.
- Current-session sync runs only while a forcePomo client is open and may take up to about 15 seconds between polls.
See Calendar & Sync for details.
Local Storage
- The local history cache is capped at 1,440 entries, equivalent to 30 days if every half-hour block is used.
- The web app uses browser local storage; the extension uses Chrome storage.
- Clearing browser or extension data removes local-only history and state.
- Signed-in settings and current-session state can be restored from Google Drive, while completed signed-in commits can be rebuilt from Google Calendar.