iOS Indie Launch Day 60:
Real Time + Money Numbers

No hype. This is what 60 days of AI-assisted solo iOS development actually looks like: hours spent, dollars in, dollars out, and what I’d do differently. Published 2026-05-08.

Days live

Revenue earned

$296

Total spent

600

Substack subs

Apps in review

Section 1 — Time Invested

Estimate based on daily session logs. Claude Code autonomous loops ran 18–36 hrs/session; human oversight averaged 2–4 hrs/day.

Week	Days	Hrs/Day (human)	Total Hours	Focus
Week 1–2	14	5	70	App architecture, ASC setup, CI/CD
Week 3–4	14	4	56	4 iOS apps coded + IAP integration
Week 5	7	3	21	App Store screenshots, metadata, review submit
Week 6	7	4	28	IAP 2.1(b) rejection fix, resubmit
Week 7–8	14	3	42	GitHub Pages site, Gumroad SKUs, content
Week 9	4	2	8	Substack, dev.to, B2B outreach
Total			225 hrs	Human oversight

Claude Code autonomous loops added an estimated 400–600 machine-hours. Human cost: ~225 hours over 60 days = 3.75 hrs/day average.

Section 2 — Money Spent

Item	Cost (USD)	Period	Notes
Apple Developer Program	$99	Annual	Required to submit to App Store
Claude Code Pro (Anthropic)	$100	2 months	$50/mo × 2; all build loops run here
Resend (email API)	$0	Free tier	3,000 emails/mo included
Cloudflare (DNS + tunnel)	$0	Free tier	Pages + Workers free plan
GitHub Pages	$0	Free	Site hosting, no limit on public repo
Gumroad	$0 setup + 10% fee	Per sale	No monthly fee; 10% on each transaction
Substack	$0	Free tier	Free up to 1M subs on free plan
Domain (jiejuefuyou.github.io)	$0	—	GitHub Pages subdomain, no custom domain yet
ASC API key	$0	Included	Bundled with Apple Developer account
Xcode + Mac	$0 (sunk cost)	—	Existing hardware; Xcode is free
Total Cash Out	$199	—	Hard spend (Apple + Claude Code)

Opportunity cost (225 hrs at any freelance rate) not included. Pure cash outlay: $199 over 60 days.

Section 3 — Money Earned

Day 60 reality: apps are WAITING_FOR_REVIEW. No App Store revenue yet. Gumroad is live but no paid conversions recorded.

Source	SKUs / Units	Revenue	Status
App Store IAP (4 apps)	4 apps × $2.99 IAP	$0.00	WAITING_FOR_REVIEW
Gumroad — TF Debug Bible	0 units sold	$0.00	Published, no sales
Gumroad — Indie Toolkit 2026	0 units sold	$0.00	Published, no sales
Gumroad — AI Prompt Vault	0 units sold	$0.00	Published, no sales
Gumroad — Prompt Packs (×3)	0 units sold	$0.00	Published, no sales
Consulting (B2B inquiries)	0 signed	$0.00	0 leads from 47 captures
Total Revenue	—	$0.00	—

Assets built (non-revenue, but real)

Asset	Count	Value Signal
Substack subscribers	600	Organic, zero ad spend
Email captures (site)	47	Warm leads, not converted
dev.to articles published	80+	SEO + referral backlinks
GitHub Pages site (pages)	50+ HTML pages	All indexed
Gumroad SKUs live	6	Awaiting traffic
iOS apps in review	4	Revenue-ready once approved

Section 4 — 5 Lessons Learned

The Apple 2.1(b) IAP Completeness trap is silent and invisible. Apple’s reviewer rejected all 4 apps because IAP metadata was incomplete — no screenshot, no review note, missing description. The API cannot set these fields; you must use App Store Connect web UI via CDP automation. Two-stage fix: create IAP via API, then complete fields via browser automation before submitting. Budget at least 1 day for this per app.
ASC API V1 vs V2 endpoint mismatch burns hours. App Store Connect V2 resources (IAP, bundle IDs, certificates) are documented under /v2/ but several route through /v1/ paths. The inAppPurchases relationship type changed between versions and is not clearly flagged in docs. Always probe the endpoint first with a GET before assuming your V2 payload is correct. One wrong path returns 404 with no diagnostic body.
dev.to drives 10–30x more cold readers than Substack for technical posts. Publishing the same article on both platforms: dev.to article gets 200–800 views within 48 hours from search and tags; Substack issue goes to existing list only. dev.to is the acquisition channel, Substack is retention. Both are needed, but don’t confuse them.
Gumroad NLP filter blocks long technical descriptions silently. A product with a 500-word description including words like “bypass,” “automate review,” or “rejection” gets flagged and fails to publish without error message. Workaround: publish with a minimal 2-sentence description, verify it’s live, then restore the full description. Affiliate links require the product to be in Published state first.
B2B funnel without inbound traffic converts at zero. 47 email captures sounds promising but zero of them were B2B decision-makers who saw a specific pain point addressed. The site lacked a clear “I have this exact problem” entry point. The fix is problem-first landing pages (like this one), not more product pages. Traffic without ICP targeting is noise.

Section 5 — 60-Day Verdict

Day 60. Revenue: $0. Cash spent: $199. Hours in: 225. That’s the spreadsheet. But it’s the wrong frame for where I actually am.

The four iOS apps exist. They compile, they pass TestFlight, they have valid IAP metadata. They are sitting in Apple’s review queue right now. The bottleneck is not technical — it’s a 5-14 day review SLA I cannot compress. The Gumroad products are live and searchable. The Substack list has 600 real subscribers who opened the first 3 issues. These are real, compounding assets. Zero revenue does not mean zero progress.

What I got badly wrong: I optimized for output volume (80 dev.to articles, 50 HTML pages) without building a single funnel that could close. The email capture form existed but the path from “I read your article” to “I paid $9.99” was never clear. I kept adding products before I had proof any one product could convert. That’s a classic indie dev trap: ship more, validate less.

The AI-assisted loop (Claude Code running 36-hour autonomous sessions) genuinely compresses build time by 5–10x. I have apps I could not have built this fast solo. But speed of building is irrelevant if the thing you’re building isn’t the thing people will pay for. Day 61 onwards: one funnel, one ICP, one conversion hypothesis, measured weekly. The 600 Substack subs are the asset. The apps are the proof point. The next 30 days are about connecting them.