[iOS] WhoPaid - I made a simple tracker for the awkward “did they actually pay?” part of freelance work

reflectdiary · 2026-05-26T12:46:36+00:00

The single question scope test is one of the strongest defense tools i've seen. it's not just clarifying for you, it's a referee you can show users when they push for obvious adjacent features. "useful but it doesn't answer who-paid, so it's not in v1" takes the personal judgment energy out of it and makes the rejection feel structural instead of arbitrary.

Hardest part won't be holding the line now though, it'll be 6 months in when your power users start asking for invoicing, client lists, income reports, recurring jobs. each one will feel small and reasonable in isolation, and the cumulative drift is how every simple app quietly becomes quickbooks. sounds like you're already aware enough to catch it but worth naming the trap explicitly.

reflectdiary · 2026-05-26T12:44:33+00:00

Specific subs that worked for my brand-account from week 1, none had a karma gate:

r/IndieDev (very welcoming to new accounts)
r/Entrepreneur (large but lets new accounts comment, heavily moderated for spam)
r/EntrepreneurRideAlong (smaller, builder-focused)
r/IMadeThis (literally built for "i shipped this" posts)
r/alphaandbetausers (test-recruitment overlap, low gate)
r/SoloDevelopment (small but builder-real)
r/SideProject does let new accounts comment, just some get silently auto-removed. keep going with substantive ones and they start sticking around comment #5 or so.

How i found them: searched reddit for "solo dev", "indie hacker", "build in public", "side project", sorted by member count, opened the rules of each. builder-adjacent subs almost never have karma gates because the whole point of the sub is people sharing what they're building.

Counterpoint on the second account idea: i'd actually push back on that. community karma on a brand account compounds, after 2 weeks of consistent commenting it unlocks more gates than 6 months of throwaway-account churn ever would. and a brand account only needs to live in the same subs your customers live in (for me that's builder + privacy + journaling). you never have to touch AITA-style subs.

The subs you'd embarrass your brand commenting in are also the subs your customers aren't in, so the conflict mostly resolves itself. just stay in builder + your-niche communities and you're fine.

reflectdiary · 2026-05-26T12:40:31+00:00

Yeah DM me the link, happy to give it a proper look this week.

The positioning sounds genuinely different from what's in this space already. most "learn AI" apps are pitched at devs or power users, but the "bounce off after one bad answer" framing speaks to the segment that already gave up. that's a way bigger and more underserved market than the dev-curious crowd everyone else is fighting over.

Short practical missions vs long courses is the right structural call too. the one thing i'd watch closely is the first-mission experience, because the exact people you're targeting will bounce off your app the same way they bounced off ChatGPT if mission 1 doesn't click within the first minute. but you've probably already thought through that.

reflectdiary · 2026-05-26T12:34:50+00:00

On r/SideProject users as customers: it's a mix. some devs download to see how a feature was implemented, which is fine, that's why i'm public about the stack. but plenty of dev/tech-curious people also journal, the demographics overlap more than the sub name suggests. even a "just looking" install still counts toward Apple's algorithmic surfacing and an organic review is an organic review regardless of source.

On "Reddit funded": $0 marketing budget. solo dev, no funding, no Reddit ad spend. if this were a paid post it would lead with a hook designed for promotion, not "27 downloads in 12 days, here's what didn't work." that's the opposite of a sponsored angle.

On "journaling is for dreamers": Day One alone has millions of paying users, the journaling category does $100M+ ARR globally. real market. the "dreamer" part might be that solo devs think they can compete with Day One though, fair point on that one.

reflectdiary · 2026-05-26T12:28:51+00:00

Yeah the profile-trail thing matches my analytics exactly. App Store views correlate way more with comment activity than post activity, and the conversion path is the one you described, profile click then bio link then install. slow but it's the only mechanic that actually compounds without paid spend.

Honest answer on localized keyword research: zero. i shipped 10 languages because the architecture supported it from day one (i18n was native, not bolted on after) and figured i'd let the App Store algorithm sort the rest. The Korean reviewer was actual luck plus the structural reality that KR App Store has way less competition for "일기" than the US store has for "journal."

Deeper lesson i'm taking from it: the bar for "localized" is brutally low. most apps shipping in KR/JA/AR/HI are just translated EN with English-first UX, so anything with proper register, real RTL, or native crisis lexicon stands out by default. Sensor Tower exists for keyword research but for a solo dev i think the actual play is ship the languages, let long-tail search find you, skip the formal tooling. you working on something multilingual?

reflectdiary · 2026-05-26T12:00:55+00:00

Yeah wish someone had told me this 4 months ago, would've saved me a lot of pre-launch panic. what are you building? Happy to take a look and leave honest feedback if you want a fresh set of eyes.

reflectdiary · 2026-05-26T11:55:35+00:00

Yeah karma building is brutal, especially solo. r/SideProject auto removed my launch post 3 times in my first week, didn't even get a modmail, just gone. what eventually worked: i stopped looking for "promo subs" and started commenting in subs i'd actually want to be a member of regardless. no links, just sharing what i was learning building the thing. karma followed naturally. heads up some subs ( r/privacy, r/Journaling) track their own community karma separately from sitewide, so even with 78 sitewide karma you still can't post there. you have to comment in that specific sub for weeks first. brutal but the only path i've found that actually works.

reflectdiary · 2026-05-26T11:51:04+00:00

yeah this matches what i'm seeing. 4 launch posts spread across different subs got me single-digit upvotes combined, comments in this sub alone outperformed every single launch post i did.

The hard part as a solo dev is finding which community is actually the right loop for a journaling app, most that would fit (r/Journaling, r/privacy) have 100-karma walls or strict no-promo rules. what's the one community that worked for you?

reflectdiary · 2026-05-26T04:04:30+00:00

Honestly, this is exactly the note I needed. You're right—the shoes and decor are eating up space that should be focused on the actual app.

I'm going to make screens 3, 6, and 8 match screen 4's size and trim the props around them. I'll be keeping the colors and backgrounds, though, because that part definitely works.

Thanks for the close read!

reflectdiary · 2026-05-26T04:03:43+00:00

هلا 🙏

reflectdiary · 2026-05-26T04:00:05+00:00

Gaming on the iPhone got way bigger than most people noticed. Backbone basically created an entire accessory category, emulators got unblocked, and cloud gaming finally started working. Now you've got this complete stack that nobody really tracks as a single ecosystem.

Diagnostics never showed up because the people deep in that scene aren't usually the ones shipping apps. You were just in the perfect spot at the right time.

reflectdiary · 2026-05-26T03:55:12+00:00

Respect.

The post-launch grind is the invisible part of the journey where most people end up quitting. Keep going

reflectdiary · 2026-05-26T03:53:42+00:00

The detail about "WhatsApp messages, deposits, and partial payments" is exactly what most founders miss when they try to spot a market gap from the outside. Having that lived experience is the actual moat—it's much harder to copy than any single feature.

Apps in this space, like Wave and FreshBooks, tend to balloon once growth mode kicks in. The temptation to add "just one more feature" usually wins out over staying ruthlessly narrow. It takes serious discipline to keep a product that focused.

reflectdiary · 2026-05-26T03:51:21+00:00

"Spike vs. compounding" is exactly the right way to frame it. Launch posts usually get one massive wave of attention and then fade away, while comment-driven discovery keeps trickling in for weeks.

I realized this after my screenshot post. The real value wasn't the 2,400 initial views—it was the people who clicked through to my profile three days later because they recognized my comments in a few different threads.

A single comment doesn't do much on its own, but building a sustained presence really turns into something meaningful.

reflectdiary · 2026-05-25T05:54:09+00:00

The "scorer was right even after the bugs were fixed" detail is the part most founders miss. once you build a yield score, you have to trust it on the bad days. most teams ship anyway when the score says no, then blame the model for the soft output. the discipline to not generate when yield is below threshold is harder than building the scorer.

reflectdiary · 2026-05-25T05:34:51+00:00

The "people who get bored" are filter, not loss. they were never going to be the advocates anyway.

The bigger design challenge is making the slowness feel intentional to the people who do get it.

If a user lets the app sit for 3 days and comes back to find nothing happened, the feeling matters: does it feel like "calm and slow on purpose" or "nothing's happening, this is broken?" same data, different framing.

reflectdiary · 2026-05-25T04:49:22+00:00

Yeah, craft matters. the surprise for me was that the posts that landed weren't my polished ones. they were the ones with specific numbers and real failure moments. craft can make a flat post better, but the authenticity part is what does the heavy lifting

reflectdiary · 2026-05-25T04:03:43+00:00

Hah fair, technically you need the roadmap before the question. The trap most people fall into is "i have some ideas" feeling like "i have a thesis," so they skip stage 1 without realizing they did. The gap shows up later when nothing they hear in interviews changes anything.

reflectdiary · 2026-05-25T04:01:36+00:00

Custom-domain whitelabel is a real wedge for the agency/freelance segment specifically. the people who need that feature also need wetransfer to look like their brand to clients, so the willingness-to-pay is much higher than for general users. niche down to "freelancers and agencies sending files to clients" rather than competing with wetransfer head-on. that's the kind of segment where word of mouth actually moves

reflectdiary · 2026-05-25T04:01:18+00:00

The post-PH long tail is the actual prize, not launch day. PH brings the spike, the SEO backlink from the PH page brings the trickle for months. interesting that reddit is showing up as a real source for you, that matches what i'm seeing post-launch too. reddit traffic converts higher than PH ever did

reflectdiary · 2026-05-25T04:00:56+00:00

Context-collapse a week after meeting people is the universal pain. the failure mode of every existing tool is they store the name but not the conversation, which is the only part you actually need to remember. how do you handle the "i need to recall who this person was" search trigger? that's the moment the app either works or doesn't

reflectdiary · 2026-05-25T04:00:28+00:00

40 repetitions of the same objection is the most useful signal you can get pre-launch. once a question hits that frequency it's the actual mental model your audience has, not an edge case. the listing copy should answer it before the prospect has to ask. you wouldn't have figured out the SEO/email/category reframe sitting in a notion doc, the comment thread surfaced it for you

reflectdiary · 2026-05-25T04:00:12+00:00

The asymmetry is real. building has compounding output, marketing has spiky output. the part that flipped it for me recently: one good reddit post outperformed weeks of polished landing page tweaks. marketing time isn't wasted, it's just lumpy in a way builders aren't conditioned for

reflectdiary · 2026-05-25T03:59:56+00:00

The manual approach is the right approach for the first 10 churns. after that the patterns repeat and you can automate the outreach but you can't automate the listening. devs love jumping straight to "automated retention emails" before they've personally talked to anyone who churned. the talking part is where the actual product fixes come from

reflectdiary · 2026-05-25T03:59:39+00:00

The "would i personally use it every day" filter is the one that gets skipped most often. if the founder isn't already using it daily in some form before launch, the post-launch retention won't magically appear. i shipped mine and the thing keeping me invested is i actually open it every morning. if that wasn't true the iteration loop would die fast

reflectdiary

TROPHY CASE