A fractured glass panel in modern architecture — structured but broken in specific ways.

Photo by Zhanna Filimonenko on Pexels

screen-timemaccritique

5 Things Apple Screen Time Gets Wrong About Your Mac Usage

Screen Time is free and built in, so people assume it's the default answer to “where did my day go?” For knowledge workers, it's wrong in five specific ways. Here's each one, with what to do instead.

Mike6 min read

5 Things Apple Screen Time Gets Wrong About Your Mac Usage

Screen Time on Mac is one of those Apple features that looks complete on the marketing page and reveals its limits the moment you try to use it for something real. It was designed to tell a parent how much time a teenager spent on TikTok. It was not designed to tell a professional how much of their day was deep work.

Here are the five specific ways it gets your usage wrong, in order of how much each one distorts the picture. If even two of these apply to you, Screen Time is not a tool you can trust for decisions about your own attention.

1. It counts "app open" as "app used"

Screen Time's definition of time-in-app is "app was in the foreground." That's it. No mouse activity check, no keyboard check, no idle detection beyond a very coarse system-sleep heuristic.

What that means in practice:

  • Step away from your desk to grab lunch with your editor frontmost: 45 minutes of Xcode logged.
  • Lock the screen with Slack open: 2 hours of Slack logged overnight.
  • Let a YouTube video auto-play while you answer a phone call: 45 minutes of Safari logged.

For someone comparing their kid's TikTok time to their kid's Duolingo time, this doesn't matter much — both get the same over-count. For someone trying to measure deep work, it's a real problem. The number you care about is "time you were actively engaged," and Screen Time isn't measuring that at all.

What to do instead: any tracker that uses HID input signals (keyboard and mouse activity) will pause the clock after a configurable idle period. Focus Meter defaults to 3 minutes. That cuts the overnight-Slack phantom time to zero and makes the "deep focus stretch" metric meaningful.

2. It can only see inside Safari

We covered this in detail in another post, but it bears repeating in the context of things Screen Time gets wrong — not just things it's missing.

Screen Time tells you chrome.google.com: 0 minutes and Chrome: 4 hours. It thinks Chrome is an app you use; it thinks chrome.google.com is a place you don't visit. That's because it can see Safari's tabs but not Chrome's. For a Chrome user, the entire site-level breakdown is missing, and the one it does show you is a picture of a Safari usage pattern that barely exists.

The error compounds. If you spend 10 minutes in Safari and 4 hours in Chrome, Screen Time shows you a pie chart where 96% of your browsing is one gray wedge called "Chrome" with no subdivision, and your 4% of Safari time gets surgical-level detail. It's not that Screen Time is partially wrong — it's that it optically inverts where the useful information is.

What to do instead: a tracker that uses the macOS Automation permission to read URLs from every browser, not just Safari. See this walkthrough.

3. It counts meeting apps as active use

Zoom is in the foreground for 90 minutes during a standup. Screen Time logs 90 minutes of Zoom. Fine.

But here's what actually happened in those 90 minutes: 20 minutes of you actively listening and speaking, 30 minutes of you half-listening while editing a doc in another window (which Screen Time counted as "Google Docs: 30 min," double-counting parts of the meeting), and 40 minutes of you fully tuned out, reading Slack and a PR.

The overall meeting length is fine as raw data, but treating it as "time spent meeting" distorts anything downstream. Teams with a lot of video calls routinely find that their Screen Time-reported "meeting hours" are 1.5x to 2x their actual engaged meeting hours.

What to do instead: any tracker that detects activity-based idle time will recognize that "Zoom was frontmost but you didn't touch your keyboard or mouse for 15 minutes" means the meeting had you half-there. It's not perfect, but it's closer to reality than a raw foreground count.

4. It has no notion of focus

Screen Time can tell you that you used Xcode for 3 hours. It cannot tell you:

  • Were those 3 hours one continuous stretch, or was it 52 small sessions interrupted by Slack?
  • How many app switches happened inside those 3 hours?
  • What's your typical longest uninterrupted session for the day? For the week?
  • Does your focus trend up or down week over week?

These questions aren't niceties. They're the actual difference between a productive day and a busy one. Screen Time gives you totals; it doesn't give you structure. And when the question is about deep work, structure is the whole answer.

What to do instead: a tracker with a Focus Score or similar composite metric that incorporates productive-app time, session length, and context-switching rate. More on Focus Scores here.

5. It flattens your profession

Apple assigns every app to a category (Creativity, Productivity, Social, Entertainment, etc.) and shows you a pie chart based on those buckets. You can't meaningfully override this per-app, and the buckets are locked to Apple's taxonomy.

That works fine for a teenager. It falls apart for professionals, because the category depends entirely on the job:

  • Figma is productive for a designer, neutral for a PM, idle browsing for a lawyer.
  • Twitter is productive for a marketer, distraction for a developer.
  • YouTube is productive for a musician learning a piece, distraction for most people, legitimate professional development for some.
  • Slack is productive up to a point, then rapidly becomes a distraction — a nuance no category system captures.

Screen Time's pie chart is wrong for virtually every professional use case because it refuses to let you define productive for you. The pie chart is telling you what Apple thinks about your day, not what you think about your day.

What to do instead: a tracker that lets you tag apps and websites against your own productive / neutral / distracting definitions, and then builds the report off of those. Every Focus Meter report uses your categories, not some pre-baked taxonomy.

The pattern these errors share

Three of the five errors come from Screen Time being designed for parental oversight, not personal analytics. One (Safari-only URLs) comes from Apple's internal architecture. One (category flattening) comes from a one-size-fits-all taxonomy that can't model what "productive" means for different jobs.

Understanding the origin helps you see why "better Screen Time" is not really what's needed. What's needed is a tool built for a different question: what actually happened in my day, by my definition of what matters?

Focus Meter is built for that question, the same way Screen Time was built for a very different one. $19 once, all on-device, and an honest answer to "where did my attention go today?"