Help test Local Time Tracker v1.3.0 on Windows — installation and daily-use feedback

[HafidIdrissi]

We're looking for 5–10 people using 64-bit Windows 10 or Windows 11 to try Local Time Tracker v1.3.0 and share a short, honest report. You do not need to be a developer.

Local Time Tracker automatically records time spent in foreground applications and browser-window titles. Activity stays on your computer: no account, cloud upload, or telemetry.

Download and get started

• Download v1.3.0: choose LocalTimeTracker-Setup-1.3.0-x64.exe or LocalTimeTracker-1.3.0-portable-x64.zip.
• Five-minute first-run guide.
• Checksums are available in SHA256SUMS.txt on the release page. The installer may be unsigned, so Windows can display a SmartScreen warning. Please report installation friction; you do not need to bypass a warning to participate.

Use either the installed app or the portable app, not both at once. The app starts tracking when launched, and window titles can contain personal information.

Try it for one day

1. Install or extract the app and note whether the first launch is clear.
2. Switch between a few applications and browser tabs, then inspect Usage analysis. Do the labels and durations roughly match what you expected?
3. Stop tracking, use another application briefly, then start tracking again. Is the stopped/running state easy to understand?
4. Generate an offline HTML report and try a CSV or JSON export. Are the output and save location clear?
5. Tell us the biggest problem or missing feature that would stop you from using it again.

Shorter tests are welcome. Report only steps you actually tried; “not tested” is useful information. Reset and uninstall are not part of this test.

Reply with this short template

App version: 1.3.0
Windows version:
Setup installer or portable ZIP:
Installation / first launch: worked, blocked, or not tested
SmartScreen or other installation message (if any):
Tracking and displayed durations: what you observed
Stop / restart: worked, problem, or not tested
HTML report / CSV or JSON export: what you tried and the result
Biggest difficulty or missing feature:
Would you use it again? Why or why not?

Please do not upload your activity database, exported history, personal HTML reports, or screenshots with private window titles. Use fictional app/title examples when describing a problem. No personal files are needed to participate.

If something fails, describe the steps, what you expected, and what happened. We will use reproducible reports to create focused issues and prioritize fixes. Security concerns should go through SECURITY.md.

Thank you for helping make a small, local-first Windows app more useful. A brief report about what worked is welcome too.

[HafidIdrissi]

Hi @Ymax27 and @Juhita2005 — thanks again for your contributions! If you’re using Windows and have a little time, would you be willing to try the published v1.3.0 release as an end user?

A short check of installation, tracking, and the reports would help. The download links and feedback template are in the post above. Please report only what you actually tried, and don’t share private activity data.

No pressure if you’re unavailable—thank you!

[Ymax27]

Yes, yes, no problem.