the credential layer for the 92 percent of work linkedin was never built for
a plumber with 600 documented installs. a nurse with 7 years of patient outcomes. a designer who reached 4 million users. none of them has a portable credential. linkedin gives them a title and nothing else.
the 92 percent number is the part nobody talks about. linkedin has 1 billion users but only 8 percent of the working world has a meaningful profile on it. plumbers do not work there. nurses do not work there. drivers do not work there. the other 92 percent has always been invisible.
From dead side-projects to building a community map for expats — what I learned along the way
When vibe coding took off, it became possible to quickly turn product concepts into working software rather than leaving them in Figma or notes. But fast prototyping also made it easy to start projects without clarity, and I ended up abandoning a couple early on.
Now I m focused on one specific problem: building a community app for expats and travelers from my country. It s designed as a curated map where people pin local spots, share trusted services, and find businesses abroad where they can communicate comfortably in their native language.
For those building products for local communities or expats:
How do you approach the initial cold-start problem (getting enough verified places onto the map)?
What has been your biggest takeaway from previous projects that didn't take off?
Free Graph Ops upgrade for safer AI-generated repairs
I built Code Factory for my own needs after too many assistant-generated changes passed tests and then failed when I actually used them. The wasted time and frustration pushed me to put planning, evidence, and review into one proof-first workflow. I am sharing it free.
v0.32 adds a Counterfactual Arena to Graph Ops. It compares 2 12 supplied repair candidates, rejects failed proof, surviving mutants, scope escape, or changed receipts, and explains exactly why the smallest eligible repair won. It cannot generate or apply code; the human remains in control.
Solo builders get a readable choice before accepting an AI fix. Teams get a reproducible, hash-bound decision record. Time, token, and cost savings are shown only with an exact paired baseline; otherwise they remain Not measured.
I also used the open Prestige skill on the UI. In my own observation it materially improved the visual hierarchy and readability; the repo records its deterministic design checks without presenting that observation as measured conversion.
Solo developer here — building a Mac screen recorder
Hey Product Hunt
I m a solo developer and I ve been building NovaCapture, a native screen recorder for Mac.
I started building it because I kept finding that recording a good product demo takes more work than the actual demo. You record the screen, move the cursor around, and then spend more time editing everything to make it easier to follow.
That led me to build NovaCapture around automatic zoom, smooth cursor movement, webcam, and audio with the goal of making a clean demo straight from the recording.
Building BrainOS with my first 20 users
Hey everyone
I m building BrainOS, and honestly, I started it because I could relate to the problem myself.
Sometimes you have a million things you need to do, but getting them out of your head and turning them into an actual plan is somehow the hardest part.
So I built BrainOS to take those messy brain dumps and turn them into something you can actually follow.
What do you look for in a good full-stack project starter?
Hey everyone!
I ve been working on ShipSprint, a full-stack project starter CLI, and we just released v1.0.0.
Just shipped 2FA to Uppale.com! 🔒
I got tired of asking AI whether my startup idea was good
One thing I've noticed while building with AI:
AI is very good at making almost any startup idea sound reasonable.
I’m building FluidVIP — an Indian-style casual puzzle game. I’d love honest feedback.
Hi Everyone
I m working on FluidVIP, a casual water-sort puzzle game for Android.
I m currently improving the game before its final release, and I d really appreciate honest feedback from other makers and gamers.
Current features:
I need some brutal feedback from fellow Founders and makers
I built a product called IndieDeck. The original idea was simple: a place for founders and indie hackers/builders to showcase themselves, their projects, links, products, verified MRR, build log and everything they're working on.
The reality:
It's been live for 5 months
Got users
Got few paid users
But I've realized something uncomfortable and I feels stucked
It's a nice-to-have product, not a must-have product. People like it.
Very few people NEED it.