DevPulse

Local-first coding activity tracker for VS Code

Visit Website
September 19, 2026 I built a place where builders can get answers instead of “Looks good.”

One of the most frustrating things about building a product is getting feedback that sounds positive but tells you nothing.

“Looks good.”

Okay... but what should I actually improve?

So I built Critique.

It lets builders:

- Share what they're building

- Ask one specific question

- Get focused feedback from another builder

For example, instead of:

“What do you think of my project?”

You can ask:

“Would you actually use this?”

The goal isn't to collect likes or generic opinions.

It's to get an answer you can actually use.

I recently started using analytics to understand where people were getting stuck, and found a real problem in my own flow: people could write feedback, but their draft could be lost when GitHub login was required.

I fixed that, so the feedback now survives login and the user returns to the same project.

Critique is still early, and that's exactly why I'm launching it here.

If you're building something, I'd love for you to try it:

https://critique.page

And if you have a project you're working on, drop it in the comments. I'd be happy to check it out.

One question for other builders:

What's the most frustrating kind of feedback you've received on something you built?

Comment

August 28, 2026 What’s the most useless feedback you’ve gotten on your project?

I keep getting feedback like:

“Looks good.”

“Nice project.”

But honestly, that doesn’t tell me what to improve.

That’s why I started building Critique.

Instead of asking “What do you think?”, you ask one specific question and get feedback around that question.

I’m looking for a few developers to try it with something they’ve built.

https://critique-qqz9.onrender.com

What’s the most useless feedback you’ve received on a project?

Comment

August 21, 2026 I have 21 users for my VS Code extension. What would you do to get the first 100?

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.

3 Comments

  1. 1

    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.

    1. 1

      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.

      1. 1

        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.

About

I wanted a simple coding tracker for VS Code that kept my data private. So I built DevPulse as a local-first, open-source way to track coding time, projects, and progress.