DevGlobe

The Strava analogy really nails it. WakaTime is great data but it's fundamentally solo - there's no reason to check it beyond your own curiosity. The social layer is what turns tracking into accountability and motivation. I'm curious how the live globe handles privacy - can you choose what to make public vs keep private? Some devs will love full transparency, others will want to share stats without exposing which specific files they're working on.

Hey Product Hunt 👋

Coding trackers have always been solo dashboards. WakaTime even calls itself the "Fitbit for programmers", and that's exactly it: great data, but it lives alone in a private tab. We wanted the Strava version: the same stats, but live, social, and public if you want it to be.

So the fastest way to get it is to just open the globe: https://devglobe.app, hit play, let the music and auto-rotate kick in, and watch developers light up city by city as they code in real time. Here's my own live profile and stats so you can see what yours would look like: https://devglobe.app/developers/...

We learned why the social part matters the hard way. Our first version got around 170k views and 400 signups, then almost nobody came back. People installed the extension and forgot the site existed, because there was nothing to return to. So we spent two months rebuilding around one idea: make the stats social.

What it does: you connect your IDE and show up live on that 3D globe as you code, with full stats per file, language, project, and branch. Then you can launch your projects in a weekly directory and get upvotes from real builders. Goals, badges, and private leaderboards are there too if you like a nudge to keep going.

Who it's for: developers and builders who want their coding to be more than a private number. Indie hackers shipping in public, freelancers tracking time per project, open-source folks who want a public profile, and the WakaTime/Wakapi crowd looking for a social layer.

The directory is the part I'd point you to. Up to 15 projects launch each week, and the people voting are devs already on DevGlobe for their own stats, not an imported crowd and not bots. So a launch gets real eyes even with zero followers.

On privacy, since an extension that shows where you code deserves real scrutiny, here's exactly how it works:

We track your coding, not your code. Source code, file contents, keystrokes, commits, env vars, and SSH keys never leave your machine. Only metadata is sent: language, editor, coding time, and repo/branch/file names.
Location is city-level only, snapped to the nearest city center, never your exact coordinates.
Three profile modes you can switch anytime: Public (your city), Anonymous (a random city in your country, so you're on the globe but your real location is hidden), or Private (off the globe entirely, stats tracked solo with full history, no 7-day cap).
Every field is individually toggleable locally before anything is sent: hide file names, branch names, or whole project names from your config.toml.
The extensions are open source (MIT) so you can audit every line yourself.
Pricing: tracking, stats, the globe, and the directory are all free. The one ask, and it's by design: once a week you upvote or comment on a project in the directory to keep your stats access active. That small weekly action is what keeps the directory full of real, active voters instead of a ghost-town feed, so every launch actually gets seen. We only charge makers who want extra reach (a featured launch slot or a written article about their product), never for the tracking itself.

I'd love your feedback: if you ship things, would you launch in a weekly directory like this one?

Thanks for checking it out, I'd genuinely love to hear what you think.

— CaadriFR