Build-in-Public Week 3 — What's Converting on Google Play, and What Claude Code's May Release Did to My 75-Session Workflow

This is the Friday field report for Week 3 of public marketing on Background Camera RemoteStream — the privacy-first Android camera app that records with the screen off, streams to YouTube Live from your phone, and never phones home. If you missed the earlier installments: Week 1 was the 35-article Pareto, and Part 2 of the 75-session retrospective is the philosophical sibling to all the tactical posts.

Two things broke open this week. The first is that the dev.to throttle that has been crushing every new submission for three weeks turned out to be a routing problem on my end, not a platform punishment — and rerouting the pillar content fixed it inside 72 hours. The second is that Anthropic shipped the largest Claude Code release of the year on the same week I was redesigning my own publishing pipeline, and the timing was, frankly, a little surreal. This post is the data, the verdicts, and what changed inside my 75-session workflow as a result.

The Friday scoreboard

Cumulative numbers pulled from the actual dashboards this morning (no rounding, no projection):

Channel	Volume	Engagement
dev.to	44 articles	315 cumulative views, 3 reactions, 1 bookmark, ~6 followers
Quora	~30 answers	First-position SERP slot on three questions; one 135-view/15-hour breakout this week
X / Twitter	~80 tweets / long-posts	Blue-check active; reply-boost engine running 2/day across 5 niches
Bluesky	~50 posts	Single-digit likes, 1 follower, automated empty-post sweeper now installed
LinkedIn	~12 native posts	0 followers added this week (consistent — LinkedIn is downstream of everything else)
Hacker News	1 submission shipped	id 48150619, did not catch fire, but the audit on the way there mattered more
Reddit	API request pending	Cannot post until credentials land
Google Play	UTM-tagged links live	Click data visible per platform/medium; install conversion not exposed in Console UTM view

The headline number: the catalog added +32 views in the 24 hours between Thursday and Friday morning, breaking a five-day stretch of total flatness across the entire dev.to footprint. That delta is concentrated in pieces I did not publish this week. More on why in a moment.

The Week 3 ship log — and why the dev.to column is mostly empty

Date	Day	Archetype	Pillar	Where it actually went
May 18	Sun	G	"Best Free Security Camera Apps" + "Best Baby Monitor Apps" refresh	dev.to PUT (throttle-immune); cross-linked to two Texas-AG newsjacks
May 19	Mon	A + C	Camera2 screen-off + AlfredCamera price-hike replacement	Quora-first; LinkedIn native; dev.to canonical deferred 7 days
May 20	Tue	Quora pillar	"Is my baby monitor app watching me too?"	Quora; Bluesky drip; YouTube multi-format newsjack published natively as dev.to id 3710458
May 21	Wed	C	"Why does my Android camera stop recording when the screen turns off?" (Doze / WorkManager)	Quora-first; LinkedIn; dev.to canonical deferred
May 22	Thu	Quora pillar	"The most privacy-respecting way to use an old Android phone as a home security camera"	Quora; X long-post for Monday's C-pillar (+72h); Texas-AG-vs-Meta-AI-Glasses newsjack published natively as dev.to id 3723597
May 23	Fri	E	This post. Build-in-Public Week 3.	dev.to + LinkedIn native (E owns its weekly Friday cadence)

The two dev.to entries on that table are newsjacks. Everything else routed through Quora first. That is the calendar working as designed, not as a freeze. The Strategy Helm rewrite on May 17 committed the new rule explicitly: net-new pillar content flows Quora long-form first, then X long-post at T+48–72h, then dev.to canonical at T+7d. The dev.to canonical write retains its slot for SEO and URL value, but it is no longer the discovery-surface bet for the week's pillar piece.

That sounds like a small operational change. It is not. It inverts the entire question of "where do I publish?"

The verdict on the channel-pivot pilot

The rule was written because the dev.to throttle — first identified on Day 4 of the project — had failed to clear after five consecutive evaluation days of zero-view post-throttle publishes. Eight new dev.to pieces sitting at 0 views for over a week is not a publishing strategy. It is a publishing punishment.

So we tested an inversion. The pillar long-form goes to Quora first (where I had a confirmed 135-view breakout on a "Is X happening to my phone?" privacy-anxiety question shape), then to X as a long-post 48–72 hours later (X Premium's 25k-char long-post format makes the full pillar copy-pasteable), then to dev.to as the canonical archive at T+7d when SEO indexation matters more than discovery feed pickup.

After four pilot days, here is what the data is telling me:

The +32-view 24-hour move that broke the five-day flat happened on pieces I did not publish this week. The recipients were existing catalog pieces — the doorbell comparison, the dashcam list, the refreshed nanny-cam piece — that I had been cross-linking from the daily Quora answers for the last 96 hours. That is exactly the predicted shape of the new rule. External traffic lands on Quora, follows internal cross-links into the dev.to catalog, and pieces that were sitting at 0–5 views for two weeks finally moved.

I will not call this validated yet. One non-flat 24h after five flat days is a single data point. But it is the first data point that argues for the channel pivot rather than against it, and it landed on the exact day the model predicted.

The newsjack archetype broke its own ceiling. I have published four general-audience-breach newsjacks since launch (NoVoice rootkit, ClayRat trojan, Be Prime, Meari). All four sat at 0–4 views forever. The fifth, Google's binary-transparency rollout on May 10, was the first to crack the ceiling at 4v + 1 reaction — and it was the only one with an Android-developer-specific angle. That informed a criteria narrowing in the May 17 scorecard: NJ engine fires only on Android-developer-specific announcements going forward.

Two pieces this week tested the rule. The YouTube Live multi-format newsjack (May 20) is still warming up at 0v. The Texas-AG-vs-Meta-AI-Glasses architectural critique (May 22) is sitting at 22 views in under 24 hours — the first time a newsjack on this account has broken double digits on Day 1. The thematic match with the Quora "Spying" answer batch running concurrently is probably what pulled it. I have a template now.

The Quora "Question for You" surface is the highest-leverage discovery channel I have found. Algorithmically-surfaced Q4U entries (visible from the notifications page) are landing at 5–10× the view trajectory of search-discovered questions. The privacy-anxiety question shape ("Is X happening to my phone?") consistently outperforms comparison-list shapes ("What are the best X for Y?") on Quora — which is the inverse of the dev.to ranking. Same content, different platform, different ranking. Worth knowing.

What's converting on Google Play

I have to be careful here. The dev.to API surfaces every view, reaction, and bookmark; the Quora editor surfaces per-answer "X content views this month" footer counts; X's analytics tab shows impressions and reply CTRs. The Google Play Console does not surface UTM source breakdown in a way I can pull programmatically from this side of the stack. So when I talk about "what's converting on Google Play," I am talking about upstream signal — what link clicks I see, where they originate from, and what kinds of content move the click curve.

Three honest observations from three weeks of UTM-tagged outbound links:

Privacy-anxiety questions outclick comparison lists on Quora. The single Quora answer with the 135-view / 15-hour breakout used the "Is X happening to my phone?" question shape. None of the comparison-list-shaped Quora answers have come close. On dev.to, the inverse is true: the comparison list at id 3590206 is at 45v, the comparison list at id 3592937 is at 50v, the privacy-anxiety equivalents are at 0–4v. The same content has to be reshaped for the platform it lands on. I have stopped trying to ship one body across all surfaces.

Author-dialogue compounds on third-party dev.to posts faster than our own catalog indexes. A comment I posted on a peer's privacy-focused article hit AI snippets and surfaced engagement inside 24 hours — faster than my own articles took to surface anywhere. Two days later a third privacy-tooling author joined the thread. That is dialogue compounding I cannot manufacture in my own comment section because nobody is reading yet. I am leaning into peer-thread engagement more deliberately as a result.

The newsjack-to-architecture-essay funnel may be the only paid-acquisition substitute I can run. Newsjacks bring in topical search traffic for 48–96 hours; well-cross-linked architecture essays on the same theme catch the runoff. The Texas-AG-vs-Meta-AI-Glasses piece is a clean test of this — it cross-links to my own architectural Netflix-spying critique from May 15, and the Netflix piece moved from 0v (Day 7) to 10v (Day 8) when the Meta piece started catching traffic. The catalog is starting to behave like a graph instead of a list.

What Claude Code's May release did to my 75-session workflow

Anthropic's May release landed in the same week I was redesigning the publishing pipeline. The timing is doing some heavy lifting in this post, but the changes are real and they touched parts of the workflow I had not expected.

A few notes from a solo indie who has shipped the entire app and the entire marketing engine across 75+ Claude Code sessions:

Opus 4.7 GA changed how often I let the model write a full file from scratch. With 4.6 I was scaffolding with the model and then hand-editing inside the editor. With 4.7 the first-pass output on architectural specs (Camera2 capture-session lifecycle, Ktor route handlers, the foreground-service permission map for Android 14/15/16) has been good enough to commit and iterate on. The session count has stayed flat at 75-plus across the month, but the per-session output is meaningfully higher.

The Code Review beta is the feature I most underestimated. I assumed it would surface trivial nits. It surfaced two genuine concurrency bugs in the foreground-service teardown path that I had been routing around with reboot fixes for weeks. It also told me, accurately, that I was over-using try/catch where Kotlin's Result type would have read better — which is the kind of taste-level feedback I would normally pay a senior Android engineer to give me.

The /ultrareview slash command is the better pre-submission audit I needed. The HN submission for the Camera2 + Ktor architecture piece on May 15 (HN item 48150619) involved a brutal pre-flight that caught a "7000 sessions" vs. "75 sessions" inconsistency between the title and the body — a drift caused by an earlier title edit that didn't propagate. The audit shape (title → opening → bullets → URL slug, all referencing the same number) is now codified in my marketing memory and would have been faster with /ultrareview reading the canonical article object end-to-end before I shipped.

The plugin marketplace changes the calculus on whether I publish my own tooling. I have a Bluesky empty-post sweeper script that auto-deletes the empty/emoji-only posts the Distribution daemon occasionally emits when the X compose editor stalls. It is 80 lines of Python. Before the marketplace, the right place for it was a private gist. After the marketplace, the right place might be a shipped plugin that other indie marketers can install. I have not decided. But the question is now askable.

The Agent SDK / claude -p subscription-billing split announced for June 15 is the one that materially affects me. I run the entire daily marketing engine — the daily-content-forge that is generating this article, the platform-blast distributor, the newsjacking-radar, the hacker-news-engine, plus the ten Shadow Viral Engine tasks installed on May 19 — as scheduled tasks behind claude -p-style headless invocations. Today they all bill against my Max subscription. On June 15 the headless paths move to API billing. That is a real cost shift and I need to either (a) collapse some of the lower-yield daemons, (b) move the agents to my own keys with rate caps, or (c) measure whether the marketing engine pays for itself yet.

My honest read is that (c) is not yet true and (a) is the right next move. The Shadow Viral Engine has 364 bandit arms running across 47 hook templates and I do not yet know which lanes are paying for themselves. The June 15 cutover is forcing the kind of pruning conversation I should have been having anyway.

What I am no longer doing

• Daily scanning of r/SecurityCamera. That sub surfaces hardware shoppers, not phone-repurposers. The audience does not match. I have moved Reddit scanning to r/selfhosted and r/degoogle pending API approval for actual posting.
• Treating the dev.to throttle as adversarial. It is not. It is a feed-pickup constraint shaped by my publishing velocity, and the channel pivot rule routes around it cleanly.
• Replying to @levelsio. Post-level reply restrictions confirmed; reply boosts on that account never publish. Time wasted. Moved on.
• Trying to publish empty Bluesky posts. The sweeper handles them now. Eight deletions logged this week.
• Worrying about Forge "silent gaps." The 5/22 "gap" was a Blast-before-Forge schedule artifact — Platform Blast was running an hour before Content Forge, then misattributing the empty content folder to a Forge miss. Fixed today by shifting Blast to 09:00 UTC. Forge has not actually been silent.

What's queued for Week 4

• Mon May 26: A-archetype "Best Apps for Hands-Free YouTube Live Streaming From Android in 2026" — keeps the YouTube cluster alive after this week's multi-format newsjack and pairs with the all-time #1 evergreen (id 3592937, currently at 50v).
• Mon May 26: Show HN of Part 1 (id 3589467, "How I Built a Production Android App in 75+ AI Sessions") — fresh title/body alignment is finally clean post-audit, account is one week older, eligible to retry.
• Wed–Thu: C-archetype technical pillar and D-archetype use-case pillar both routed Quora-first under the new rule; dev.to canonicals deferred to Week 5.
• Fri: Build-in-Public Week 4 — with the first multi-data-point read on the channel pivot rule, the first paid-traffic experiment if the engine starts paying for itself, and the first post-June-15-cutover billing read once Anthropic publishes the migration details.
• Decision required by June 15: Which scheduled tasks survive the Agent SDK billing change. Probable cuts: shadow-villain-pulse (off-archetype), shadow-canonical-syndicator (overlap with platform-blast), one of the two threads-blast time slots. Confirmed keeps: daily-content-forge, daily-platform-blast, newsjacking-radar, hacker-news-engine.

If you are an indie hacker watching a flat chart

Three things that helped this week and might generalize.

One: archetype-level Pareto matters more than per-piece view counts. Build-in-Public, the archetype you are reading right now, is averaging an order of magnitude more views per piece than my Technical Deep-Dive archetype, even though the technical pieces are harder to write. Tagging every published asset with an archetype the day it ships, and reviewing the Pareto weekly, is the cheapest analytics layer I run.

Two: route around the platform you are publishing on if it stops returning signal. I sat on a dead dev.to throttle for ten days before someone — actually Anthropic's scorecard subagent — wrote me a binary publish-gate rule that read the cohort, returned a verdict, and surfaced the channel-pivot recommendation. If you are publishing into a feed-ranked surface and your last eight pieces are all at zero, the platform is telling you something. Believe it earlier than I did.

Three: the audit you do before submitting to a high-stakes channel matters more than the submission itself. The HN submission this week did not catch fire, but the audit that prevented me from submitting an article with a "7000 sessions" / "75 sessions" inconsistency in the title — that audit is the durable artifact. It is now memory, and it will save the next submission from a top-comment kill.

Back next Friday with Week 4 numbers. If you want to follow the experiment in real time, the project is Background Camera RemoteStream on Google Play, and the site is superfunicular.com.

— Tommy