PR review
A focused review thread can be part of shipping, not just another browser visit.
Developer time tracking
Developer time tracking for code, docs, PRs, and drift.
Engineering work moves through IDEs, terminals, GitHub, docs, Slack, and browser research. drifty captures that context automatically, then helps classify which switches supported the task and which ones pulled you away.
Developer focus is fragmented, but not always unfocused.
A real implementation block can move from editor to terminal to docs to GitHub and back again. App-level totals flatten that into noise. drifty keeps the context visible so the review is about intent, not just which window was active.
- See editor, terminal, browser, and GitHub context in one daily timeline.
- Classify docs, tutorials, and issue threads as focus when they support the task.
- Spot Slack checks, search loops, and tab drift that repeatedly break code blocks.
- Review weekly focus blocks without manually tagging every engineering session.
Developer signals worth separating.
These are the moments a simple app timer usually misreads.
Debugging research
Docs, Stack Overflow, and tutorials can be useful during a bug investigation and drift once the task is done.
Launch communication
Slack can support coordination during a release and become reactive checking after the decision is made.
Developer time tracking FAQ.
Does drifty require developers to start project timers?
No. drifty starts from automatic Mac activity capture, then uses classification to make the day easier to review after the work happens.
Can docs and browser research count as focused work?
Yes. The point is context. Docs, tutorials, and issue threads can be focus when they support the current task, and drift when they turn into unrelated browsing.
Is this meant to replace engineering project management?
No. drifty is for understanding attention and time patterns. It can make engineering days easier to explain, but it is not a ticket tracker or billing ledger.
Review your engineering day without reconstructing it by hand.
Use automatic Mac tracking and AI classification to see where deep work held, where context helped, and where drift formed.