I’ve been building DevPulse, a local-first coding activity tracker for VS Code.
It tracks coding time, projects, languages, Git activity, streaks, and progress. There’s no account or telemetry, and the data stays on your machine.
I currently have 21 users and want to reach my first 100. I’m trying to figure out what I should focus on next.
If you were building a developer tool from this stage, where would you look for your first real users?
I’d also love to hear from VS Code users:
- What would make you try a coding tracker?
- What would make you keep using it?
- What feels missing from DevPulse?
DevPulse is free and open source.
Try it:
[VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=bistadev.devpulse-code)
Source:
[GitHub](https://github.com/BistaDinesh03/devpulse-tracker)
Honest feedback is welcome. If you think something is unnecessary or poorly designed, tell me — that’s exactly what I’m trying to learn.
The strongest part is the problem framing: the issue isn't lack of tech news, but too much fragmented information and no clear signal about what actually matters.
Thanks for the feedback! Just to clarify, DevPulse is a local-first VS Code coding tracker rather than a tech-news product. If you get a chance to check it out, I’d really appreciate your thoughts on the idea and what would make you actually use it.
That clarification makes sense. The more interesting question then is what job the activity data actually helps a developer understand or change — otherwise tracking can become interesting data without becoming useful feedback.