MobileCLI Growth Playbook
Outlines a phased go-to-market strategy for a developer tool, prioritising Hacker News and Twitter over ProductHunt.
What this file does
Outlines a phased go-to-market strategy for a developer tool, prioritising Hacker News and Twitter over ProductHunt.
When to use it
- Launching a CLI or dev tool with a terminal-power-user audience
- Planning a Show HN as the primary launch event
- Building in public on Twitter before a product launch
- Prioritising low-effort directory submissions and newsletter pitches
Assumes this stack
MobileCLI Growth Playbook
Created: March 14, 2026 Current: 200 impressions/day on App Store, 3 blog posts, zero social presence
THE HONEST TAKE
ProductHunt is overrated for dev tools. The audience is founders, marketers, and tool collectors -- not the developers who actually use CLI tools. A "great" PH day gets you 2-5k site visits that evaporate in 48 hours.
Hacker News is your #1 launch event. HN readers ARE your users: terminal power users, Rust enthusiasts, AI coding agent users. A front page Show HN can drive 10-50k visits and the audience actually TRIES things.
Twitter building-in-public is your #1 ongoing channel. Not a one-time launch, but a sustained presence.
Here's the plan, reordered by actual impact:
PHASE 1: PRE-LAUNCH (Now β 2 Weeks)
1.1 Polish the GitHub README
Your README is already solid but make sure it has:
- 60-second demo GIF at the top (the magic moment: phone buzzes, approve, agent continues)
- Clear install command front and center
- "Star this repo" CTA
- Badges: stars, license, latest release
1.2 Start @mobilecli on Twitter (THIS WEEK)
Don't wait for launch. Build in public NOW.
Week 1 content:
- Day 1: Intro post + promo-v3-square.mp4 video "We built MobileCLI β approve Claude Code tool calls from your phone. Self-hosted Rust daemon. No cloud. No accounts. Your terminal, in your pocket. [video]"
- Day 2: Problem tweet (relatable pain) "The #1 productivity killer with AI coding agents: kick off a task, walk away, come back 20 min later... blocked on approval since minute 2. π"
- Day 3: Demo GIF of approval flow
- Day 4: Technical tweet (Rust angle) "MobileCLI is ~7000 lines of async Rust. Tokio, WebSocket streaming, PTY capture, push notifications. Here's how we detect agent wait states β"
- Day 5: Share a blog post
- Weekend: Engage in AI coding threads
Ongoing cadence: 3-5 tweets/week. Mix of:
- Product demos / GIFs
- AI coding agent commentary
- Technical deep dives (Rust, iOS, terminal)
- Blog post shares
- Reply/engage with devs frustrated by agent workflows
Accounts to engage with:
- @alexalbert__ (Claude Code creator)
- @swyx (AI engineering thought leader)
- @simonw (covers AI tools extensively -- if he amplifies, massive)
- @levelsio (indie maker community)
- @karpathy (long shot but massive signal)
- @theprimeagen (terminal/Rust enthusiast -- PERFECT fit)
- @indydevdan (specifically covers Claude Code workflows)
1.3 Write 2 More Blog Posts
Get to 5+ total before Show HN. Target these searches:
- "monitor AI coding agent remotely" (zero competition)
- "stream terminal to phone" (zero competition)
- "aider mobile monitoring" (target a popular agent you don't market to yet)
The weekly blog cron is already running but write 2 manually for speed.
1.4 Submit to Directories & Newsletters (Low Effort, Do Now)
- console.dev/submit (curated dev tools newsletter)
- theresanaiforthat.com (AI tool directory)
- futurepedia.io (AI tool directory)
- GitHub Marketplace listing
PHASE 2: LAUNCH WEEK (Week 3)
2.1 Show HN (THE BIG ONE) β Tuesday or Wednesday, 9am ET
Title options (pick one):
- "Show HN: MobileCLI β Stream AI coding agents to your phone (Rust, open source)"
- "Show HN: I built a terminal mirror for AI coding agents so I can approve from my couch"
What to include in the post:
- What it does (2 sentences)
- Why you built it (the babysitting problem)
- How it works (Rust daemon β WebSocket β iOS app)
- Link to GitHub repo
- Link to demo video
Rules:
- DO NOT ask anyone to upvote. HN detects and penalizes vote rings.
- Be in the comments immediately, answer everything honestly.
- Share technical details -- HN devs love architecture discussions.
- Self-hosted + Rust + open source = HN catnip.
Expected outcome if it hits front page:
- 10,000-50,000 site visits
- 200-500+ GitHub stars
- Cascade to newsletters, Twitter, blogs covering it
- App Store downloads spike
2.2 Reddit (Same Day or Day After HN)
Space these out, 1 per day:
Day 1 β r/rust (~150k members) "I built a terminal streaming daemon in Rust β MobileCLI" Lead with the Rust technical angle.
Day 2 β r/ClaudeAI (~50k members) "I built a tool to approve Claude Code from your phone" Lead with the problem.
Day 3 β r/commandline "Stream any terminal session to your phone with MobileCLI"
Day 4 β r/ChatGPTCoding "How I stopped babysitting my AI coding agent"
Day 5 β r/SideProject Maker story angle.
2.3 Newsletter Pitches (Send Day Of or Day After HN)
Tier 1 (biggest impact):
- TLDR (tldr.tech) β massive dev audience
- Changelog Weekly (changelog.com/weekly) β dev/OSS focus
- Hacker Newsletter β curates top HN posts (auto if you hit front page)
Tier 2:
- Ben's Bites (bensbites.com) β AI tools
- Console.dev (already submitted in Phase 1)
- Rust Weekly β Rust community
- Alpha Signal β AI/ML newsletter
- The Neuron β daily AI newsletter
2.4 Tweet the Launch
Thread format:
- "We just launched MobileCLI on Hacker News. [link]"
- What it does (with video)
- Why we built it
- Technical stack
- What's next
- "Star us on GitHub: [link]"
PHASE 3: POST-LAUNCH (Ongoing)
3.1 ProductHunt (When Convenient, Low Priority)
Do it, but don't lead with it. Spend max 1 day prepping.
Checklist:
- Create "upcoming" page to collect followers
- Tagline: "Your desktop terminal, in your pocket"
- Gallery: 5 screenshots + demo video
- First comment draft (your story as the maker)
- Self-hunt is fine for indie tools
- Launch any Tuesday-Thursday, 12:01am PT
Realistic expectations: 2,000-5,000 site visits, ~100-300 App Store clicks. The REAL value: backlink for SEO + social proof badge for your site.
3.2 YouTube
- Upload promo-v3-wide.mp4
- Title: "MobileCLI β Control AI Coding Agents From Your Phone"
- But focus on getting FEATURED by creators, not building a channel:
YouTubers to pitch (with your demo video):
- IndyDevDan β specifically covers Claude Code workflows (BEST FIT)
- ThePrimeagen β terminal/Rust content, perfect audience
- Fireship β if he does a "100 seconds" it's massive
- Cole Medin β AI coding agent content
- AI Jason β AI tools and workflows
- Matthew Berman β AI tool reviews
3.3 Podcast Pitches
- DevTools FM (devtools.fm) β literally a podcast about dev tools
- The Changelog β major dev/OSS podcast
- Latent Space (latent.space) β AI engineering, hosts: Swyx + Alessio
- Software Engineering Daily
3.4 New Agent Integrations
MobileCLI works with ANY terminal but marketing specific agents = SEO:
- Aider (github.com/paul-gauthier/aider) β huge community, reach out to Paul Gauthier
- Goose by Block (github.com/block/goose) β newer, would welcome ecosystem
- Amazon Q Developer CLI β AWS's coding agent
- Cline β popular VS Code agent with CLI interactions
- OpenHands/SWE-Agent β autonomous coding agents
For each: write a blog post ("How to use [Agent] with MobileCLI"), create an integration page, and add to the website.
3.5 Community Presence
- Anthropic Community Forum (community.anthropic.com) β be helpful there
- Rust Discord β share the project
- AI coding Discords (Cursor, Continue, etc.) β MobileCLI is relevant
3.6 Content Flywheel (Automated)
Weekly blog cron is running. Each post:
- Auto-publishes to website (Vercel deploy)
- Share on Twitter
- Share on relevant Reddit threads
- SEO compounds over time
METRICS TO TRACK
| Metric | Current | Target (30 days) | Target (90 days) |
|---|---|---|---|
| App Store impressions/day | 200 | 500 | 1,000+ |
| App Store downloads | ??? | Track this! | Growing MoM |
| GitHub stars | ??? | 500 | 1,000+ |
| Twitter followers | 0 | 500 | 2,000+ |
| Blog posts | 3 | 8 | 15+ |
| Blog organic traffic/mo | ??? | Set up analytics | Track growth |
THINGS NOT TO DO
- Don't pay for PH launch services (gaming upvotes)
- Don't spam Reddit (space posts out, be genuine)
- Don't ask people to upvote on HN (they detect this)
- Don't build a YouTube channel right now (get featured instead)
- Don't over-invest in PH at the expense of HN + Reddit
- Don't launch on HN until README is polished + demo video exists
What's inside
3 phases, 6 sections, 1 metrics table, 1 anti-patterns list, 0 code examples
Change this for your project
- Replace
@mobilecliwith your own Twitter handle - Replace
promo-v3-square.mp4with your own demo video filename - Replace
MobileCLIwith your product name throughout - Replace
200 impressions/day on App Storewith your own current metrics
Where it goes
Keep it in your repository where the agent or team that needs it will read it.
Worth borrowing
- Prioritise channels where your actual users hang out, not the biggest general audience
- Build a content flywheel with automated blog posts that compound SEO over time
- Pitch YouTubers and podcasters for features instead of building your own channel from scratch
Related Documents
Media Handling Playbook - ZyeutΓ© v3
Documents upload, storage, optimization, delivery, and edge-case handling for images, videos, and audio in a social app.
Visual Truth Engine: Product-Market Fit & Go-to-Market Strategy
Outlines a product-market fit strategy and go-to-market plan for a B2B SaaS tool that automates proof asset creation for video creators.
Trader ROI Playbook (Codex + CI)
Defines weekly ROI targets, task prioritization lanes, guardrails, and a scorecard template for measuring engineering output per hour.
Devin Triage Playbook
Defines a 7-phase automated triage playbook for Devin to analyze alerts, find root causes, implement fixes, and notify teams.