Skip to content

SHOW_HN_FOLLOWUP_DRAFT.md

Latest commit

 

History

History
110 lines (79 loc) · 3.92 KB

SHOW_HN_FOLLOWUP_DRAFT.md

File metadata and controls

110 lines (79 loc) · 3.92 KB

Dev.to Post Draft: Show HN Follow-Up

결과 데이터만 채우면 5분 내 발행 가능한 템플릿

메타데이터

  • title: "I Posted My Finance App on Show HN — Here's What Happened"
  • tags: webdev, showdev, javascript, beginners
  • cover_image: (Pillow 생성 — 오렌지 HN 색상 그라데이션)
  • canonical_url: (없음)

본문 드래프트

---
title: I Posted My Finance App on Show HN — Here's What Happened
published: true
tags: webdev, showdev, javascript, beginners
cover_image: [COVER_URL]
---

Two weeks ago, I built [DonFlow](https://maxmini0214.github.io/donflow/) — a budget planning tool that runs entirely in your browser. No backend, no account, no AI. Just you and your money.

Last night, I posted it on Hacker News. Here's what happened.

## The Numbers

| Metric | Result |
|--------|--------|
| HN Points | [X] |
| Comments | [X] |
| Time on front page | [X hours] |
| Peak concurrent users | [GoatCounter] |
| Total unique visitors (24h) | [GoatCounter] |
| Gumroad store visits | [X] |
| GitHub stars | [X → X] |

## What I Posted

Title: `Show HN: DonFlow – Budget planning tool, no backend, browser-only`

I chose Tuesday 10 AM ET (the supposed sweet spot). The finance category had zero competing posts — a completely clear field.

## What Resonated

[FILL: Top 2-3 positive comments/themes. E.g.:]
- "No backend" approach — people liked the privacy angle
- IndexedDB as a real database alternative
- The anti-AI positioning during peak "AI fatigue" on HN

## What Got Criticized

[FILL: Top 2-3 criticisms. Be honest. E.g.:]
- "Why not just use a spreadsheet?"
- "No sync between devices"
- [Other feedback]

## Lessons for Indie Builders

### 1. Timing matters less than you think
[FILL based on actual experience]

### 2. The maker comment is your real pitch
My first comment was 150+ commits of context — what I built, why, and the honest trade-offs. HN rewards honesty about limitations more than feature lists.

### 3. Preparation > Luck
I spent [X hours] preparing:
- FAQ responses for 10 predicted questions
- Cross-linked Dev.to articles for deep dives
- Every external link verified (caught [X] broken links the day before)

### 4. [FILL: Unexpected lesson]

## The Honest Takeaway

[FILL: Was it worth it? What would you do differently?]

Building in public means showing the real numbers — even when they're not impressive. DonFlow is [still early / getting traction / teaching me]. The code is open, the app is free, and I learned more from HN comments in 2 hours than from 2 weeks of solo building.

---

**Try DonFlow:** [Live Demo](https://maxmini0214.github.io/donflow/?demo) | [GitHub](https://github.com/maxmini0214/donflow)

**More build-in-public:**
- [I Built a Finance App With Zero Backend](https://dev.to/maxxmini/how-i-built-a-personal-finance-app-with-zero-backend-costs-17m2)
- [Why I Chose IndexedDB Over a Backend](https://dev.to/maxxmini/why-i-chose-indexeddb-over-a-backend-for-my-finance-app-45in)
- [I Built 23 Free Developer Tools in 2 Weeks](https://dev.to/maxxmini/i-built-23-free-developer-tools-in-2-weeks-heres-what-actually-worked-5apa)

발행 체크리스트

  • [X] 자리에 실제 숫자 채우기 (GoatCounter + HN API)
  • 긍정/비판 댓글 2-3개씩 인용 (원문 포함, 감사 톤)
  • Lessons 섹션 실제 경험으로 채우기
  • Pillow 커버 이미지 생성 (오렌지+다크 그라데이션, "Show HN Results" 텍스트)
  • 기존 6글 풀메시 네트워크에 이 글 추가 (7글 풀메시)
  • Dev.to API POST → 발행
  • BUSINESSES.md Dev.to 글 수 업데이트

발행 타이밍

  • Show HN 후 24~48시간 내 (관심 유지)
  • 최적: 결과 확정 후 즉시 (2/25 오후~저녁)

톤 가이드

  • 솔직 (나쁜 숫자도 그대로)
  • 구체적 (vague한 "많은 관심" X → 정확한 숫자)
  • 교훈 중심 (결과 자랑 X → 다른 빌더에게 유용한 인사이트)
  • HN 커뮤니티 감사 (비판도 고맙다)