Jay Marsh

Solo founder lesson from this week: the bug that took three days was a five minute fix. The other two days and 55 minutes was not having anyone to tell me it was a five minute fix. Working alone makes small decisions expensive. #buildinpublic

@sth886 Those first downloads are the hardest you will ever get. My early numbers were worse than yours. What moved them was talking to the few users I had instead of chasing the next ten. 100 in a month is doable if you keep shipping and show up where they hang out.

5 Downloads after 2 days might not be that much, but my goal is to have 100 downloads after 1 month. How were your numbers for your first app? #goal #indiehacker #ios #solopreneur #productivity

@Exposes_ Two solo builds here. One shows what you can actually spend once upcoming bills and savings goals are accounted for, not just the bank balance. The other syncs Todoist projects into Google and Apple calendars both ways. Quiet progress most days but it stacks up. What are you on?

Most people consume. A few people create. An even smaller group builds every single day. If you're building something right now AI, SaaS, Startup, App, Agency, or Content Drop it below. 👇 I want to connect with real builders, not spectators. 🚀 #BuildInPublic #AI #Tech

Question for solo builders: how do you decide a feature is actually done? I keep finding one more edge case to polish and it stops me shipping. Curious where other people draw the line between good enough to ship and still needs work. #buildinpublic

@CMekelachi85842 The tester hunt is its own grind, separate from building the actual thing. What worked for me was asking in small niche communities where people already use that kind of app, not broad "who wants to test" posts. You get real feedback that way, not just silent installs.

🚀 Looking for 5 people to test my task management app for free. All I ask is a little feedback and willingness to join a small Telegram group. Interested? Comment "I'm in" below. 👇 #BuildInPublic #IndieHackers #WebDev #SaaS #DevCommunity

@Utsav56 Centralized error handling on day 2 is a smart call. The thing that bit me later was streaming responses fighting the global error middleware, since the headers are already sent by the time something throws mid-stream. Worth deciding early how you want to handle that.

@mantraist45 The inspiration scroll turns into a comparison spiral fast. Everyone posts the wins, nobody posts the three weeks of nothing in between. Building solo, the isolation is the underrated part. Talking to a couple of other builders helped more than any productivity trick.

Started looking for inspiration. Found depression instead. #Solopreneur #BuildInPublic #StartupLife #SaaS #Bootstrapped

Build in public: spent the morning watching a tester count instead of writing code. Google makes you run 12 testers for 14 straight days before you can ship to production. Turns out the hardest engineering problem is finding 12 humans with Android phones. #buildinpublic

@AnthonyCasauria A font load taking the whole thing down six times before you spotted it is so on brand for this work. The bug always hides in the line you'd never think to suspect. The render path stuff is the worst to trace because nothing in the error points at it. Nice find.

was working on MyLinks and my whole setup kept crashing — 6 times in a row. turned out loading a single font was killing it every time. one line fix once i finally traced it. live at mylinks.page #buildinpublic #indiehacker

@engwaliullah 93 in 25 days with zero ad spend is the part most people underrate. Getting to 100 is easy to fixate on, but the signal worth watching is how many of those 93 came back a second time. Curious which channel did the most work for you so far.

7 users away from 100. 93 signups. 112 resumes uploaded. 95 AI analyses done. 25 days. Zero ads. Who's going to be user #100? resume.codisim.com — free, 12 analyses/week #buildinpublic #indiehacker #SaaS

Build-in-public update: spent this week watching how people read the Money Me dashboard. Nobody cares about the breakdown, they just want the one number that says what's safe to spend today. Cutting detail to surface that has been my highest-leverage change in months.

@manoj_dharani For me, showing one 'safe to spend' number at the top of the dashboard instead of a balance plus a list of upcoming bills. Same data, but collapsing it into a single figure changed how people used the app overnight. The maths was trivial, the framing did the work.

Indie hacker question: Whats one small improvement you made recently that had a bigger impact than expected? For me: tweaking the overdue status tracking in FluxWillow invoice tool. Drop yours 👇 #buildinpublic #indiehacker

@DipojjalC Shipping member-to-member messaging is a big step. The auth page is the one screen where people bounce hardest, so the split-screen plus dark mode work is time well spent. Curious whether the messaging is realtime or polling under the hood?

Spent today giving salesforcedictionary.com some love 🛠️ Redesigned the sign-in/up pages — split-screen layout + dark mode that finally looks right — and shipped phase 1 of member-to-member messaging 💬 Come check it out → salesforcedictionary.com #buildinpublic #salesforce

@merts_dev The first-20-posts thing is real. A year into building a finance app solo, early on it felt like shouting into a void. What kept me going was treating each post as a note to my future self about why I made a call. The documenting habit paid off before the audience did.

Building in public is underrated. Even if nobody reads your first 20 posts, you're building a habit of shipping and documenting. The audience comes later — the practice is the point. #BuildInPublic #IndieDev

Day whatever of the Android closed testing grind. Google wants 12 testers active for 14 straight days before you can ship to production. Building the app was the easy part. Finding 12 humans who will keep it installed for two weeks is the actual final boss. #buildinpublic

@redditech The shift from "documentation" to "a way to stop the repeat incident" is what most teams miss. Docs written for completeness rot. A playbook written for the next 2am page stays useful, because someone actually needs it. How do you decide what earns one?

A playbook is not documentation after the fact. It is a way to stop yesterday's bug from becoming tomorrow's “wait, why did this happen again?” #AgenticAI #buildinpublic

@btrmasaladosa WisprFlow is the one I've kept too, voice into the editor saves more than I expected. Beyond that just Perplexity for quick research and a cheap transcription tool. Everything else got cut once the trial ended. Is yours mostly for writing or coding?

@JustLaunchedFYI The "one tiny ask" that triggers an accidental rewrite is the realest line here. I started writing the tiny asks down and not touching them for a week. Half lose their shine by then, and the ones that survive turn out to be the actual roadmap.

Quick feature request" is indie founder for "see you in 3 weeks when this becomes the entire roadmap." One tiny ask, 14 edge cases, accidental rewrite, launch delayed, coffee doubled. Ship it anyway. Then list it on justlaunched.fyi #indiedev #buildinpublic

@jxngrx Building Money Me, a finance app that shows what's coming, not just what you spent. Bank balance minus upcoming bills and savings, plus expected income, so you see what's safe to spend this month. Solo, manual entry, grinding through the Android testing gate.

65 new followers in one notification. 🤯🚀 A huge welcome to everyone who recently joined😍☺️😍 If you're a: 💻 Developer 🚀 Founder 🤖 AI Builder 📈 Marketer 🛠️ Builder Drop a comment and tell me what you're working on 👇 Let's connect and grow together. #BuildInPublic #Founder #Developer #AI #Startup #IndieHackers #TechTwitter

A money habit that actually stuck for me: once a month, before I look at the balance, I list every bill due in the next 30 days. Seeing the outgoings first changes what "I can afford this" means. The balance tells you today. The list tells you the truth.