The Complete Guide to Tracking Your Focus on Mac
Focus tracking is not the same as time tracking.
Time tracking asks, "How long did I spend?" Focus tracking asks a better question: "Was my attention where I wanted it to be?"
That distinction matters on a Mac because knowledge work is messy. You can spend four hours in Chrome and have no idea whether that was writing, code review, admin, or distraction. You can spend three hours in Slack and call it work, but still end the day with no deep block. You can leave an editor open through lunch and trick a simple tracker into thinking you coded.
A useful focus tracker has to read the shape of attention, not only the clock.
What focus tracking should measure
At minimum, a Mac focus tracker should measure five things:
| Signal | Why it matters |
|---|---|
| Active app time | Shows which tools actually got foreground attention |
| Website-level browser time | Splits Chrome, Safari, and Arc into real domains |
| Idle time | Prevents open windows from inflating work |
| Categories | Turns raw usage into productive, neutral, and distracting buckets |
| Switching | Reveals fragmentation, not only total minutes |
Without all five, the report is easy to misread.
Screen Time has some of this. It is good enough for a rough consumer view. It is not good enough for professionals who need to know whether their browser time was GitHub or YouTube.
App tracking is the foundation
App tracking answers the first-order question: which tools got your attention?
For a developer, that might be VS Code, Terminal, GitHub, Slack, and Chrome. For a designer, Figma, Slack, Notion, and Arc. For a writer, Obsidian, Google Docs, Safari, and email.
Focus Meter tracks the frontmost app and records active time locally. The frontmost app matters because background windows should not count as work. Spotify playing in the background is not Spotify work. Slack open behind your editor is not Slack time.
Start with the app and website tracking hub if you want examples by tool.
Browser tracking is where the truth usually hides
The browser is the hardest part of modern Mac productivity.
Chrome, Safari, and Arc are not single activities. They are containers. A single browser process can hold GitHub, Google Docs, Linear, Stripe, YouTube, Reddit, X, and documentation in the same afternoon.
That is why browser-level totals are weak. "Chrome: 5 hours" is barely better than "Mac: 5 hours."
Website-level tracking fixes this by reading the active domain in supported browsers. With permission, Focus Meter can separate github.com from youtube.com, docs.google.com from reddit.com, and work dashboards from news tabs.
The browser usage guide explains the setup. The Chrome guide goes deeper on caveats and sample numbers.
Categories turn data into judgment
Raw usage data is not enough. You need categories.
Focus Meter uses three basic buckets:
- Productive
- Neutral
- Distracting
The important part is that categories are personal. Slack can be productive for a support lead, neutral for a manager, and distracting for a solo maker. YouTube can be productive for a developer watching a specific tutorial and distracting for the same developer ten minutes later.
Do not try to make the taxonomy perfect. Categorize the top apps and domains that actually show up in your week. Leave the rest alone until they matter.
Focus score is a summary, not a verdict
A focus score is useful because it compresses a messy day into one number. It is dangerous if you treat it as a moral grade.
The score should help you notice patterns:
- More productive time usually helps.
- Longer uninterrupted sessions usually help.
- Distracting app and website time usually hurts.
- Constant switching usually hurts.
The number is a prompt for review. If your score dropped, ask why. Did Slack fragment the day? Did Chrome hide a lot of YouTube? Did you have meetings all afternoon? Did your editor time happen in five-minute bursts?
Read What Is a Focus Score? for the deeper argument.
Privacy is not a feature checkbox
Your focus data is sensitive. It can reveal work habits, browsing patterns, job searches, health research, personal interests, and every avoidance loop you have.
That data should not need to leave your Mac.
Focus Meter stores app and website usage locally. There is no account, no cloud dashboard, no team admin view, and no telemetry from the app. The website has normal marketing-site analytics, but the Mac app's usage database stays on your machine.
For the technical and product tradeoffs, read On-Device vs Cloud Time Tracking and How Focus Meter Stores Your Data.
How to review your week
The weekly review should be short. You are not trying to become an analyst of yourself. You are trying to make one better decision for next week.
Look at:
- Top productive apps and domains.
- Top distracting domains.
- Longest focus block.
- Most fragmented day.
- Biggest neutral app, usually Slack or meetings.
Then ask one question: what should I protect next week?
Maybe it is a late-morning coding block. Maybe it is two hours for writing before email. Maybe it is moving meetings away from your best design window. Maybe it is turning Slack off during the first build session of the day.
The best focus data leads to calendar changes instead of self-criticism.
Guides by role
Different jobs need different readings of the same data.
Developers should compare editor, terminal, GitHub, Slack, and browser domains. Start with focus tracking for developers and VS Code tracking.
Designers should separate Figma time from feedback, research, and Slack.
Writers should separate drafting from research from social loops.
Founders should look for the weekly split between building, selling, operations, and distraction.
The profession hub collects the role-specific guides.
What focus tracking cannot tell you
Focus tracking does not measure value directly.
It cannot know whether the code was good. It cannot know whether the meeting was necessary. It cannot know whether an hour in a blank document was deep thinking or avoidance. It cannot replace judgment.
That limitation is healthy. The tool should show evidence. You decide what it means.
The goal is not to optimize every minute. The goal is to stop being surprised by your own week.
If the data says your best work happens before Slack starts, protect that window. If Chrome hides most of your distraction, categorize your domains. If your editor time is high but your output is low, look at switching. If your focus score drops every Thursday, inspect the calendar.
Focus tracking is useful when it changes the next week.