Why 'minutes watched' is the wrong number for language learning
Open any watch-time tracker and it will tell you a number: minutes watched. It is the easiest number to produce and, for a language learner, close to the least useful.
Three things it hides
Whether the audio was in your target language. A learner’s viewing is mixed. Recaps in their own language, a video with commentary in a third one, a tutorial they clicked out of curiosity. “Minutes watched” adds them all up as if every minute pulled in the same direction.
Whether the video was actually playing. An open tab isn’t listening. Ads aren’t input. A player that buffered for a minute didn’t deliver a minute. Wall-clock trackers count all of this, and the padding is invisible because it’s spread evenly across every day.
Whether you followed it. Forty minutes of native news you caught a third of, and forty minutes of learner content you followed nearly all of, are the same forty minutes to a tracker and nothing like the same thing to your brain. This one no tool can measure for you, but a tool that reports the other two honestly at least leaves you a clean number to attach your judgement to.
What a better number looks like
The number worth keeping is hours of input in the target language that actually played. It is smaller than minutes watched, sometimes a lot smaller, which is exactly why people don’t like producing it. But it’s the number every roadmap and every “how long does it take” estimate is talking about, and comparing a padded total to those estimates is how learners conclude the method has failed them when it hasn’t.
Getting there needs three things a tracker rarely does:
- Count from the player’s own clock, so pauses, ads and a sleeping laptop don’t count, and a hidden tab does.
- Listen to the audio and decide what language it’s in, and hold back time in a language you already speak instead of adding it in.
- Show the held-back time next to the total, so the parts still add up and nothing looks like it vanished.
Recorded is not the same as counted
That last point matters more than it sounds. A tool that silently deletes your English minutes is indistinguishable from a bug. A tool that says “52 minutes of Japanese, and 14 minutes of English not counted” is telling you something true about your day. The distinction, recorded but not counted, is the whole design of Kiku Hours, and it’s why the panel never shows a number it can’t explain.
The point isn’t a smaller number
It’s a number you can trust next week. Progress in listening is slow and mostly invisible from the inside; the only reliable way to see it is to compare this month to three months ago. That comparison is only meaningful if the units didn’t change, and “minutes watched” changes its meaning every time your viewing mix does. Hours of real input doesn’t.
Kiku Hours is a free Chrome extension that counts the hours of comprehensible input you actually listened to.
Add to Chrome