First sale. 🎉 Someone I've never met just paid $5.58 for NotchStack. My app that turns the MacBook notch into something actually useful. Small number. Huge feeling. #buildinpublic #connect #indiehackers

My notch app's website on Google, last 7 days: 951 impressions 6 clicks Average position 14.7 SEO folks: what would you do first to reach page 1? Drop your advice below 👇

timeline cleanup: swapping hot takes for people who ship 👀 #connect If you're a: → Solo founder → Indie hacker → Mac / iOS dev → Building with Claude Code → First-time SaaS launcher → Side-project bootstrapper What are you building right now? Drop it below, I'll check out every single one. #buildinpublic #indiehackers #indiedev

the one file in your repo claude code is never allowed to touch: ____

Bootstrappers running multiple Claude Code sessions on the same repo: how do you split the work so they don't step on each other? Separate worktrees per feature, one session per layer (UI/backend/tests), or strictly one at a time? What actually held up for you?

pretend i'm shopping to acquire one indie app this week. drop yours, one link per reply, no pitch. i'll give a blunt 0–10 on market, product, differentiation and monetization, same way a buyer would before making an offer.

sell me your product in one sentence, but it has to start with "you know when…". no features, just the annoying moment it kills. go.

your app's real competitor isn't another app. it's your customer opening claude code and building it themselves.

hot take: if you really believed the labs' models will create enormous wealth, you'd want their equity, not an app on top of them. so why are we all building on top? you don't buy the hype, or you think the product layer keeps the money? pick one.

if you run 2+ claude code sessions at once, how do you split the work? by feature, by layer (ui / backend / tests), or just "whatever's blocked, start another"? my hunch: most people are context-switching, not parallelizing.

last call before i close the laptop: drop your product, one link per reply, and i'll give it a blunt 0–10 on market, product, differentiation and monetization. no pitch needed, the url has to do the talking. harsh ones get a reason, not just a number.

Solo devs: do you use automated AI code review as your second pair of eyes before merging Claude Code output? If so, what's your setup — a separate Claude session reviewing the diff, a PR bot, or just reading everything yourself? Curious what actually catches bugs.

solo dev, no reviewer. who checks your code before it ships? A) claude reviews claude B) a second model, different vendor C) you, line by line D) users are the review which one actually catches the bugs?

describe your product in exactly 5 words. rule: one of them has to be the thing it replaces. go.

pretend i've got $10k to put into one indie product today. drop yours, one link per reply, and i'll give it a blunt 0–10 on market, product, differentiation and monetization. no pitches, just the url.

My first $15 from X Money just landed 👀💸 Now let’s see if posting about it gets me more engagement than actually making the money 😂 The internet is a funny place.

be honest: when claude code writes 90% of your app, what are you actually the expert in now? taste, debugging, or just knowing what to ask for?

This kid is amazing 🔥

Hey Looking to #connect with more people who are actually building 👀 If you're a: → Founder → Indie hacker → Builder → Investor → AI enthusiast → SaaS / startup person Let’s connect 🤝 Building something interesting? Drop it below — would love to see what everyone’s working on. #buildinpublic #indiehackers

blindly clicking "yes" on every claude code permission prompt is the real security hole, not the model. if you've built an allowlist, what's on it and what do you still make it ask about?