DaBuilder - I build micro tools that solve annoying problems. Solo. Shipping daily
Joined December 2023
- Tweets2.2K
- Following349
- Followers220
- Likes126
old me: support emails were interruptions. today me: they're the only unfiltered feedback about what actually breaks. what's the best support message you got that changed how you built something?
noticed something in punchclock support: freelancers log revision rounds for the first time and immediately want to recalculate what they quoted. one person said "oh god, i quoted this all wrong." happens every time someone tracks a full project end-to-end.
old me: build expiro to track passports. today me: tracking domains, ssl certs, api keys, credit cards. turns out people forget anything that doesn't ping daily.
the pattern: every time a framework ships a breaking change, solo devs immediately ask "do i have to upgrade?" the real question is "what do i lose by staying on 14?" those are very different.
med students were copying pdf text into chatgpt manually, waiting for flashcards. klarrity does it in one highlight—streams cards back in ~2 seconds so you're not staring at a loading bar at 2am. exports straight to anki.
every solo dev eventually builds a dashboard to track things. expiro went the other way—just scan, set it, forget it. no login, no dashboard, no daily habit needed. turns out people don't want to manage their expirations. they want to not think about them.
the real tell: founders who panic about rate limits are usually the ones who never built a fallback. if your product dies when an api hiccups, that's a you problem.
you're doing push-ups in a bangkok airbnb because the nearest gym requires a membership you won't use next week. how do you keep chest day real when your equipment is whatever fits in a 40L pack?
you land in lisbon. you train. you open google maps. "gym" returns 47 pins. none of them list if they have a squat rack. none say if day passes exist. you lose a week. nomadfit solves this by letting you filter for the exact equipment you need before you even arrive.
lifetime pricing works for expiro because people buy it once, scan their passport, and never think about the app again until a reminder saves them at the gate. subscriptions require constant engagement. boring utilities don't have engagement.
you land in lisbon. google maps says there's a gym two blocks away. you show up. it has three cable machines and a smith machine. no squat rack. no dumbbells past 20kg. you've lost your lower body day to a map pin.
rust async traits have been "almost stable" for years. indie devs keep waiting for the "right time" to adopt it. there is no right time. you either ship with what works now or you don't ship.
the UAE added expiry alerts to visa apps years ago. the US still mails you a letter. same goal—don't let people travel on dead documents. one actually works.
every freelancer thinks they know their hourly rate until they log unbilled hours. then the number changes.
visionkit won't tell you the expiry date is rotated 90 degrees in the scan. had to rebuild the ocr pipeline twice before i realized passports aren't axis-aligned.
you scan a passport at the airport gate. the app reads the expiry date instantly. you realize it expired last month. two things that look the same—a document and a reminder—but one actually prevents the disaster.
every freelancer hits the moment where raising rates is slower than just not taking clients who need weekly scope calls and three rounds of revisions. the math is the same either way.
#startuplife #solofounder
old me: assumed users would highlight text, wait for cards, then export. today me: streaming generation. cards start appearing in 2 seconds. med students at 2am don't want to watch a loading bar.
every solo dev eventually builds a dashboard to track their dashboards. expiro skipped that entirely — just scan, get reminded, done. no settings to tweak, no sync status to check. turns out people don't want to *manage* expiry dates. they want to forget about them.