孫昊

Posted on May 6

10 dev.to Articles in 24 Hours: The Compound Effect of Indie Distribution

#indiehackers #devto #marketing #productivity

TL;DR: I published 10 dev.to articles in 24 hours via the dev.to API. Each ~1500 words, all derived from real Day 60 indie iOS dev work. Below: why this works, the API workflow, and the compound math.

The setup

I'm at Day 60 of an indie iOS dev experiment. Day 59 to Day 60: 24 hours where I shipped:

5 Gumroad SKUs ($572 catalog including new $499 ASC API Toolkit + $39 AutoApp Dashboard)
Affiliate program at 30% commission
7 new site/ pages (just-published, sales, faq, deals, press-kit, how-i-built-this, etc.)
ASC IAP $1.99 USD × 3 apps via CDP automation
10 dev.to articles (this is article #10 in that batch)

The "10 articles in 24h" stat is the meta angle. Let me show what made it possible.

The dev.to API workflow

dev.to's REST API supports article creation via POST:

import requests

API_KEY = "your_api_key"  # from dev.to settings → API key

payload = {
    "article": {
        "title": "Your title",
        "body_markdown": "Full markdown body",
        "published": True,  # set False for draft
        "tags": ["python", "automation"]  # max 4 tags
    }
}

r = requests.post(
    "https://dev.to/api/articles",
    headers={"api-key": API_KEY, "content-type": "application/json"},
    json=payload,
    timeout=30
)
print(r.json()["url"])  # the LIVE URL

This works. No CDP. No Playwright. No anti-bot fights. The API is the path.

What makes 10 articles in 24h sustainable

If you write each article from scratch in the editor, 10 in 24h = 144 minutes per article = 24 hours of writing. Not sustainable.

What makes it work:

1. Articles derive from real work, not invented topics

Every article maps to a thing I actually did in the past 60 days:

"How I Set Up an Affiliate Program in 5 Minutes" — I literally just set one up
"TestFlight to App Store: 60-Day Timeline" — that's my actual timeline
"Why I Stopped Trusting MRR-is-Everything Advice" — a position I actually formed

When the article maps to real work, the content writes itself. ~30 min per article instead of 2 hours.

2. Markdown frontmatter for tracking

Each article carries YAML frontmatter:

---
id: devto-30-asc-iap-cdp-7step
title: "dev.to #30 - Auto-Pricing iOS IAPs"
status: done
live_url: https://dev.to/snake_sun/...
published: 2026-05-07
---

This means I can track which articles are LIVE, which are drafts, what topics are covered. The dashboard auto-shows everything.

3. Cross-linking compound

Every article links to:

1-2 related articles I've already published
1 Gumroad SKU CTA at the bottom (UTM-tagged)
The main "How I Built This" story page

This compounds: each article drives traffic to 1-2 others, which drive to 1-2 more. 10 articles published interlocked = 30+ inbound links between them.

4. dev.to algorithm rewards consistent volume

dev.to's homepage prioritizes accounts with consistent posting cadence. 10 in 24h is a strong signal to their algorithm. The 11th article tomorrow benefits from that signal.

The compound math

What does 10 articles in 24h actually do?

Based on dev.to's typical engagement curve for indie accounts:

Metric	Per article (avg)	× 10 articles
Initial views (24h)	50-200	500-2000
7-day cumulative views	200-800	2000-8000
30-day cumulative views	500-2000	5000-20000
Reactions	2-15	20-150
Comments	0-3	0-30
Top article (algorithmic)	5% chance	1-2 articles likely break out

If 1-2 articles break out (algorithmic top in their tag), that's 2000-10000 additional views per outlier. That's the compounding lift.

Why this works for indie monetization (not just SEO)

dev.to articles aren't viral. They don't drive 1M views. But they:

Build dev-audience trust over months
Place your Gumroad SKUs in front of devs who buy dev tools
Create searchable evergreen content (Google indexes dev.to well)
Generate cold-outreach proof points ("here's what I've shipped")

For a 60-day indie iOS dev with 5 Gumroad SKUs at $0-499 price points, the compound math:

10 articles × 500 avg cumulative views = 5000 dev impressions
Each impression has ~0.5% click-through to Gumroad CTA = 25 click-throughs
Each click-through has ~1-3% conversion to sale = 0-1 sales

That looks small. But it compounds:

Month 2: another 10 articles → 10000 new + tail of existing
Month 6: 60+ articles total → trickle of evergreen traffic 24/7
Month 12: cumulative dev.to following → 1k+ followers, every new article hits 500+ views Day 1

This is slow, deliberate, compounding inbound. The opposite of viral.

What kills compound

1. Spammy filler articles

If your articles are obviously LLM-generated SEO bait, dev.to demotes them and the audience tunes out. Every article must teach something specific.

2. Sporadic schedule

Posting 10 articles then nothing for 60 days = the algorithm forgets you. Better to post 2 articles per week consistently than 10 once.

3. No cross-linking

If each article is an island, the inbound link graph stays flat. Every article should link to 2-3 others.

4. Generic CTAs

"Subscribe to my newsletter" converts 0.5%. "Get the 50pp playbook with the exact ASC checklist I used" converts 2-5%. Specific CTAs win.

My honest expectation

10 articles in 24 hours won't generate 100 customers tomorrow. The realistic projection:

Day 7: ~5000 cumulative views, 1-2 algorithm breakthrough, ~50 newsletter subscribers, ~$5-50 in Gumroad sales
Day 30: ~15000 cumulative views, ~150 subscribers, ~$50-300 in sales
Day 90: real signal, real revenue picture

If the funnel converts at industry rates, the Day 90 number gives a clear go/no-go on whether this distribution model works.

What I'm going to do tomorrow

Stop. The 10-article-in-24h was a one-off because of the Day 60 milestone + 4-hour focus block. Sustainable cadence is 2-3 articles per week, not 10/day.

Tomorrow: B2B outreach (cold emails to 5 ICPs), Substack #21 publish, Reddit/IH milestone post (paste-ready content already prepared).

Source

dev.to API docs: https://developers.forem.com/api
The Python script I used (~30 LOC): github.com/jiejuefuyou/autoapp-toolkit
All 10 articles indexed at: https://jiejuefuyou.github.io/just-published.html

If you want the 60-day playbook that produced this content (real numbers, real timeline, real Gumroad data): iOS Indie Launch Playbook ($19) — 50pp PDF with the dev.to distribution chapter.

DEV Community