Build-in-Public Week 1 — 35 Articles, 185 Views, First Bookmark, First Bluesky Follower, and the Pareto in a Flat Chart
This is the Friday field report for Week 1 of public marketing on Background Camera RemoteStream — a privacy-first Android camera app that records with the screen off, streams to YouTube Live, and never phones home. Three days ago I posted Part 2 of the build-in-public series — the philosophical month-one retrospective. This post is the boring tactical sibling. The data, the experiments, what is queued for Week 2, and what I am no longer doing.
If you are an indie hacker keeping a public scoreboard, this is the format I have settled on.
The Friday-of-Friday scoreboard
The cumulative numbers as of this morning, sourced from the actual dashboards (no rounding, no projection):
| Channel | Volume | Engagement |
|---|---|---|
| dev.to | 35 articles | 185 cumulative views, 2 reactions, first ever bookmark today, 4 followers |
| X / Twitter | ~59 tweets | 0 followers, blue-check active, first verified-account reply chain today |
| Bluesky | 33 posts | 4 cumulative likes, first ever follower today (mutual) |
| Quora | 15 answers | First-position SERP slot today, 1 organic follower captured this week |
| Profile only | 0 posts shipped | |
| Account only | API approval still pending |
The headline reading: the flow is moving in the right direction even when the flat numbers look like nothing. Three "first ever" milestones landed in a single day this week. None of them showed up in the article-view chart, because they happened on platforms that are not dev.to.
The Week 1 ship log
Every dev.to article published this week, in order, with archetype and the day's gate:
| Date | Archetype | Title (abbrev) | id | Gate / fate |
|---|---|---|---|---|
| May 2 (Sat) | A | Best Free Nanny Cam Apps for Android in 2026 | 3598582 | +20 views in the 24h after publish — caught a feed wave |
| May 2 (Sat) | NJ | ClayRat Trojan — Privacy-First Camera Architecture | 3599501 | Day-1: 0 — first newsjack to hit the ceiling |
| May 2 (Sat) | C | Why Your Old Phone Security Camera Dies After 4 Hours | 3601469 | Day-1: 1 — confirmed C archetype is structurally weak |
| May 2 (Sat) | NJ | NoVoice Rootkit Hit 2.3M Android Devices | 3601479 | Day-1: 0 — second newsjack ceiling |
| May 3 (Sun) | D | Monitor Your Dog While You Are at Work for Free | 3602874 | Day-1: 6 — D archetype average held |
| May 3 (Sun) | NJ | When the Camera Cloud Becomes the Attack Surface — Be Prime | 3603034 | Day-1: 1 — third newsjack ceiling, throttle confirmed |
| May 4–5 (Mon/Tue) | — | DEV.TO PUBLISHING THROTTLE | — | Hard pause — no new posts |
| May 6 (Wed) | E | How I Built a Production Android App — Part 2 | 3619147 | Day-2 verdict: still throttled (0 views @ 48h) |
| May 6 (Wed) | C | The Architecture Behind a $0 Security Camera | 3619879 | Day-2 verdict: still throttled (0 views @ 48h) |
| May 7 (Thu) | aux | Weekly clip post (Digital Nomad Media) | 3623990 | Out of main publish cadence |
The most important entry on the ship log is the row that says DEV.TO PUBLISHING THROTTLE. I will get to it.
Cumulative dev.to footprint as of this morning: 35 articles, 185 cumulative views, 2 reactions, 1 bookmark (the first one ever, landed today), 4 followers. The first reaction landed on id 3590177, a build-in-public sibling post from late April. The first bookmark landed today, on the same archetype family. Both signal-bearing engagements in the catalog have come from build-in-public posts. That is not random.
The 24-hour doubling — and the flat 48 that followed
The single most counterintuitive number from this week: dev.to total views went from 67 → 133 in a 24-hour window between May 2 and May 3, then climbed steadily to 185 by May 7, then went flat for the next 48 hours. The catalog roughly tripled its lifetime view count in five days, then stalled.
Crucially, the May 2–3 growth did not come from new posts. The pieces published in that window (the two newsjacks and the use-case sequel) added roughly 0–6 views each. The growth came from the existing catalog:
- id 3592937 ("Best Apps to Stream YouTube Live") +20 views in 24h
- id 3598582 ("Best Free Nanny Cam Apps for Android") +20 views in 24h
- id 3590206 ("Turn Your Old Android Phone Into a Free Security Camera") +22 views over the week, +10 more in a single 24h window mid-week
- id 3592840 (a comparison-list piece) +10 views in a single 24h window
These are 4–7 day old pieces finally getting feed pickup or organic search hits. They are working precisely because they are no longer new. The lesson: dev.to view curves on this account are bimodal — a small day-1 burst, then a 4–7 day gap, then a second wave. If I had judged any of these pieces by day-1 views I would have killed all of them.
The pattern is now baked into the calendar: every archetype gets at least 72 hours before being judged, and 7 days before being demoted.
The archetype Pareto, after a full week
Tagging every piece with its archetype turned out to be the highest-leverage thing I started doing in week one. The averages have stabilized enough to publish:
| Archetype | Pieces | Cumulative views | Avg / piece |
|---|---|---|---|
| Build-in-Public (E) | 2 | ~35 | 17.5 |
| Use Case Showcase (D) | 6 | 33 | 5.5 |
| Comparison List (A) | 13 | 60 | 4.62 |
| Newsjack (NJ) | 4 | 1 | 0.25 |
| Technical Deep-Dive (C) | 8 | 4 | 0.5 |
| Dramatic Story (B) | 1 | n/a | n/a (not validated) |
Build-in-Public is averaging 35× the views of Technical Deep-Dive despite being the cheaper format to write. Comparison Lists looked like the worst-performing archetype 24 hours after publish (1.6 avg) and tripled to 4.62 by day three — saved from being demoted by the bimodal-distribution rule above. Build-in-Public is also the only archetype that has produced both reactions in the catalog and the first bookmark.
The operational consequence: the Week 2 calendar adds +1 E and +1 D in weekday slots, keeps Comparison Lists on weekend slots for the 72-hour SERP runway, and quietly drops Technical Deep-Dive from any standalone slot until it earns its way back. Newsjacks are paused until Monday May 11.
The newsjack throttle — and why it has not lifted
Three consecutive newsjacks (ClayRat, NoVoice, Be Prime) hit identical 0–2 view ceilings inside 48 hours, while four-day-old articles continued to rack up views. The most parsimonious explanation: dev.to has a per-account feed-volume throttle, and I tripped it by publishing 30+ articles in under 96 hours.
Diagnostic test: existing catalog still surfaces (proof: the +20s above), but new pieces don't get feed pickup. Conclusion: this is a velocity problem, not a quality problem.
The remediation, as planned:
- Stop publishing for 48–72 hours. Mon and Tue (May 4–5) went dark on dev.to.
- Resume with a single high-value sequel to one of the top performers, not another newsjack. (The Wednesday May 6 build-in-public Part 2.)
- Re-evaluate feed pickup on the resumed piece before reintroducing daily volume.
What actually happened: the Wednesday resume piece (id 3619147, Part 2) and the architectural sibling piece (id 3619879) both hit 0 views at the 48-hour mark, just like the newsjacks before them. That is the May 7 verdict, and it is the May 8 verdict, and as of this morning it is the May 9 verdict. The throttle has not lifted on a five-day pause. The Thursday May 8 D-sequel I had drafted was therefore deferred to Monday May 12, after the planned Hacker News submission window — better to land a sequel into a fresh discovery surface than dump it onto a still-throttled feed.
If you publish for a living on dev.to and you are pushing more than five posts per week, watch your day-1 numbers across multiple posts. If three in a row hit a 0-view ceiling while older pieces continue to gain, you are throttled, not unlucky. And if your "resume" post is also throttled, the cooldown is longer than 48–72 hours — you may be looking at a full week or more, depending on the size of the burst that triggered it.
The newsjack archetype is hard-capped at 2/week going forward, regardless of how good the news is. Next newsjack window opens Monday May 11.
Off-dev.to: where the surprising data lives
The dev.to view chart is the headline, but the most informative single data points this week — and the three "first ever" milestones — were all elsewhere.
Quora. Monthly content views nearly doubled — 34 → 66 (+94%) in the first half of the week. The answer count climbed from 11 to 15 published answers by Friday morning, a +36% week-over-week increase. The 14th answer (a SimpliSafe-comparison piece) was algorithmically surfaced into a first-position SERP slot. The 15th (a dashcam GEO-targeted answer) was published this morning and is also pulling SERP rank. The first organic Quora follower captured this account has ever recorded landed early in the week. Quora is the closest thing to a working channel this account has, and it costs me ~10 minutes per answer.
Bluesky. Two milestones today, both first-evers: a third-party like landed earlier in the week from @zip358com, and the first ever follower landed this morning — Liv Well (@olivination.bsky.social, 2.1K followers, vegan/wellness audience). The follow came in via a #dogs hashtag overlap on a pet-monitoring post, and the follow-back established a mutual. One follower in 33 posts is a 3% follower-conversion-per-post on a cold-start graph — not zero, but not enough to call Bluesky a working channel. The conclusion I am drawing: Bluesky's cold-start tax is brutal, and audience overlap on hashtags can produce a follower out of a community you did not target. The next Bluesky experiment is intentional follower acquisition through neighbor topics (privacy, dogs, indie dev), not more posts into a 0-graph.
X / Twitter. ~59 tweets, 0 followers, but two structural wins this week: (1) the @superfunicular blue-check verification went live, which raises baseline reply-boost weight on the algorithm; (2) the first verified-account reply chain landed this morning, a back-and-forth with Mahere (@Mahere_Fluxera, founder of appxpose.app Privacy Scanner — a privacy-adjacent founder, the right kind of audience overlap). The reply chain extended past the first exchange, which is the actual signal — verified founders rarely engage on cold accounts unless the content is being read.
The single most useful artifact of last week was a reply on a 51,500-view tweet that was actively recommending a competitor (AlfredCamera). The reply named three concrete differentiators in 280 characters and linked the Play Store. I cannot prove it produced installs, but I would not trade it for the 58 standalone tweets that preceded it. The new operational rule: one reply per day on a saved search, logged with parent-tweet view count, capped to avoid rate limits.
LinkedIn. Profile is up. Nothing has shipped yet beyond the bio. Week 2 will change this — the first long-form post is queued (this article's contrarian "deep-dive is the worst archetype" angle, adapted).
Reddit. Account created, API access pending approval. Week 1 was blocked on this. r/AlfredCamera surfaced three active pain threads this week (hardware burnout, notification delay, doxx incident) that map cleanly to our differentiators. The moment API access lands, the queue is full.
What is queued for Week 2
The decisions made this week, all of them justified by the data above:
- Hacker News Show HN submission of id 3589467 on Tuesday May 12 at ~08:00 PT. It is the highest per-piece efficiency archetype I have, the family that produced both reactions and the only bookmark, and the parent piece is now four weeks old — old enough to look real. Submission window is locked.
- Comparison List re-promoted from HOLD to SCALE. Day-one views had us pointing at the exit; the 72-hour indexation pattern saved it. Week 2 carries an A piece on Mon May 12 (al
Top comments (0)