WhatPulse 6.3 is built around one idea: more depth in application visibility, and giving you a faster, cleaner way to see it. The headline changes are window title tracking, a redesigned tray popup, and Pulsar - a fun new desktop avatar - alongside a tidied-up Settings screen and a substantial round of stability and correctness work.

See your time and input per window title​

WhatPulse has always tracked how long you spend in each application. With 6.3 it goes one level deeper and tracks per window title, so you can see not just "2 hours in your Excel or IDE" but which sheets and projects made up those two hours - and the same for your input.

• Time and input per title. Your uptime is broken down by window title alongside the usual per-app totals, and keys, clicks, scrolls, distance, and words are attributed to the title they happened in.
• Expand and search. On the applications pages, click any app to reveal the titles you spent the most time in. A search box lets you find a title across all your apps at once - even ones you have not expanded - and your search stays put as the stats refresh in the background.

We've spent the last few weeks reworking the Productivity dashboard, and if there's one thread running through all of it, it's control. You could already see where your time went. Now you get to decide what counts, clean up the view, and trust that the headline numbers match the way you actually work.

Here's everything that changed.

Read on for the textual version, or watch the video for a quick overview:

Apps and websites, finally in one place​

Developers usually spend their time across a few repeating modes: editor work, browser research, terminal bursts, communication, and the occasional build or review cycle. The useful question is not how many hours sat in a chair. It is which computer activities filled those hours, and whether the mix matched the job you thought you were doing.

If you want the short answer, a developer computer day usually shows up as a mix of application usage, website visits, keyboard activity, mouse activity, and uptime. That combination tells you whether you were building, debugging, reading, reviewing, coordinating, or just leaving the machine awake while life happened elsewhere.

Yes, for most people using it as designed, WhatPulse is safe. It is a personal activity tracker, so the real question is whether you are comfortable recording counts for keyboard, mouse, application, website, uptime, and related stats. If you review the privacy settings, decide which data you want to collect, and keep exports and backups under your control, the setup stays straightforward.

That is the short answer. The longer answer is more useful. A safety check for tracking software should ask four things. What data does it collect, who can see it, how easy is it to export or remove, and can you turn off the parts you do not want. WhatPulse gives you enough knobs to make those decisions without turning the whole thing into a hobby in itself.

Keyboard lifespan is usually measured in parts, not in one dramatic collapse. Mechanical switches are often rated in tens of millions of presses per key, so a normal user can get years of use before switch wear becomes the main problem. Keycaps shine, stabilizers loosen, batteries age, cables fail, and dirt gets in the way long before the whole board gives up.

The useful question is simple: how much typing do you actually do? If you know your average daily key count, you can estimate how long a keyboard will last, spot which parts are wearing first, and decide whether you need cleaning, repair, or replacement. WhatPulse helps because it turns that guess into a record.

What actually limits keyboard lifespan​