Time trackingCAN I VIBECODE
Timing?
BUILD FIRST
- One defined user and a repeatable end-to-end job
- A small, clear data model with sign-in only if it is genuinely needed
- Loading, empty, error, and success states that make the workflow feel complete
LEAVE FOR LATER
- Large integration marketplaces
- Multi-region scale and enterprise administration
- Every power-user setting from the established product
RESEARCH NOTES
What this tool actually does.
Timing is a macOS-native automatic time tracker. It runs in the background and records which apps, documents (including full file paths), and websites (URLs) the user opens, so time is captured without start/stop timers. Users categorize captured activity by dragging entries onto projects; option-dragging creates reusable rules that auto-assign future matching activity. An interactive timeline lets users add offline time such as meetings and calls retroactively, and optional manual timers remain available. It also tracks calendar events and reminders, imports Screen Time data, and prompts users to record time after video/audio calls. Optional cloud sync keeps data across Macs, and a companion web app can be installed on a phone to start/stop timers remotely. Productivity scoring lets users rate projects and track improvement. AppleScript, Zapier, and a Web API support automation and expo
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a macOS menu-bar replacement for the Timing automatic time tracker. Core workflow: the app silently records the active app, its window title, and the open document path or website URL, then the user opens a daily timeline, drags activity blocks onto projects to categorize them, and creates rules (match on app name, title keywords, and paths) so future matching activity is assigned automatically. Users can add offline entries (meetings, calls) directly on the timeline, keep a manual timer, and see per-project totals and productivity scores. Technical requirements: native Swift/SwiftUI menu bar app; detect frontmost app changes via NSWorkspace notifications; read window titles and document paths via Accessibility/AppleScript with graceful fallback when permission is missing; store events locally in SQLite; timeline UI with drag-and-drop assignment; rule engine evaluating predicates on each new activity event; EventKit import for calendar events; manual timer; CSV/JSON export; exclusion list with local-first storage. Approach: Xcode project or Swift Package; group app sessions into contiguous time blocks; rules as structs with a match function. Out of scope: do not copy Timing's brand, logo, screenshots, or UI; do not build AI summaries, cloud sync, a phone web app, Zapier/invoicing integrations, or Screen Time import; no tracking of private/incognito data. Deliver a README covering setup (including Accessibility/Screen Recording permission steps and how the app behaves when denied), architecture, build/run instructions, and known limitations.