Important Notes & Limitations
While forcePomo is designed to be a powerful focus tool, there are some important architectural decisions and limitations you should be aware of.
🕒 Fixed Schedule (The "Forced" Nature)
- No Manual Control: You cannot manually start, stop, or pause the timer. The cycles are fixed to the clock (every 30 minutes).
- Strict Windows: If you miss the 15-minute check-in window, the session is locked. If you miss the 10-minute commit grace period, the session cannot be logged to Google Calendar.
🔗 Google Calendar Integration
- Write-Only Access: For your privacy, forcePomo only requests permission to create events. It cannot read, modify, or delete your existing calendar events.
- Single Calendar: Events are created in your primary calendar associated with the logged-in Google account.
- Sync Requirement: You must be online at the time of "Committing" for the session to be synced to Google Calendar.
💻 Browser & Platform Differences
While both versions share the same core features (Google Calendar sync, focused UI, strict scheduling), there are fundamental architectural differences:
| Feature / Area | 🌐 Web App (Browser Tab) | 📱 Web App (PWA) | 🧩 Chrome Extension |
|---|---|---|---|
| Timer & Performance | Browsers throttle background tabs to save battery. The timer catches up when you return, which may delay phase transitions. Keep tab active. | Similar to the browser tab, but running in a dedicated window makes it less prone to aggressive background tab-discarding by the browser. | Runs reliably in a background service worker using chrome.alarms. Time is tracked precisely even when Chrome is minimized. |
| Audio & Notifications | Subject to browser "Auto-play" policies. Requires an initial user interaction (click) to unlock audio. Notifications use Web Push APIs. | Operates under less strict auto-play policies once installed. Notifications integrate seamlessly with your OS native notification center. | Uses an "offscreen document" for reliable audio without interaction. Native Chrome UI integration updates the extension icon badge with the exact remaining time. |
| User Interface & Flow | Runs as a standard full-page web app inside your browser tab. Standard OAuth popups for Calendar. | Runs as a standalone, distraction-free app window outside the browser UI. Feels like a native application. | Lives persistently in the Chrome Side Panel. Monitor sessions without crowding your tab bar. Calendar authentication integrates seamlessly. |
Data Syncing
Currently, session state (whether you checked in or committed) is stored locally on your device. It does not automatically sync between the Web App and the Extension. Google Calendar serves as the only unified record of your completed sessions.
💾 Data Storage
- Local History: The in-app history view is limited to the last 50 sessions. For long-term tracking and analytics, we recommend using the Google Calendar integration.
- Storage Type: Data is stored in
localStorage(Web) orchrome.storage.local(Extension). Clearing your browser data will remove your local project settings and session history.
🔊 Audio & Notifications
- System Mute: forcePomo cannot override your system or browser tab mute settings. Ensure audio is enabled to hear session cues.
- Focus Mode (OS): If your operating system is in "Do Not Disturb" or "Focus Mode", browser notifications may be suppressed.