community-building

What this skill does

# Community Building

Build and engage a community around your indie Apple app. Practical strategies for solo developers who have limited time but want meaningful growth through community.

## When This Skill Activates

Use this skill when the user:
- Wants to build a community around their app
- Asks about growing their social media presence
- Wants to start building in public
- Needs a content strategy for promoting their app
- Asks about developer marketing
- Wants to turn users into advocates

## Process

### Step 1: Gather Context

Ask the user via AskUserQuestion:

1. **Current presence**: Are you on any social platforms? How many followers?
2. **Time budget**: How many hours per week can you dedicate to community?
3. **Comfort level**: Are you comfortable sharing revenue, progress, struggles?
4. **App stage**: Pre-launch, just launched, growing, or established?
5. **Target audience**: Developers, general consumers, or a specific niche?

### Step 2: Platform Selection

Choose 1-2 platforms to focus on. Spreading across 5 platforms with weak presence is worse than owning 1-2 platforms.

#### Platform Comparison

**Twitter/X**
- Audience: Large Apple developer community, tech enthusiasts
- Strengths: Fast feedback loops, viral potential, networking with other devs
- Weaknesses: Noisy, algorithm-dependent, declining trust among some users
- Best for: Developer tools, productivity apps, building in public
- Time investment: 15-30 min/day
- Growth speed: Moderate (1-3 months to gain traction)

**Mastodon (mastodon.social / indieweb.social)**
- Audience: Growing indie dev community, privacy-conscious users
- Strengths: No algorithm (chronological), supportive community, less noise
- Weaknesses: Smaller audience, less viral potential, fragmented servers
- Best for: Privacy-focused apps, developer tools, indie community engagement
- Time investment: 10-20 min/day
- Growth speed: Slow but genuine (3-6 months)

**Reddit**
- Audience: Highly engaged niche communities
- Strengths: Targeted subreddits, long-form discussion, SEO value
- Weaknesses: Anti-self-promotion rules, can be hostile, requires genuine participation
- Best for: Category-specific apps (r/productivity, r/fitness, r/budgeting)
- Subreddits: r/iOSProgramming, r/apple, r/SwiftUI, r/macapps, plus your app's category
- Time investment: 15-20 min/day (mostly commenting, not posting)
- Growth speed: Moderate if you contribute genuinely

**Discord**
- Audience: Power users, beta testers, engaged community members
- Strengths: Real-time interaction, deep engagement, beta testing hub
- Weaknesses: Requires active moderation, conversations are ephemeral, onboarding friction
- Best for: Apps with power users who want to discuss features and help shape the roadmap
- Time investment: 20-30 min/day (or batch in dedicated hours)
- Growth speed: Slow (requires seeding initial members)

**Threads**
- Audience: Growing, overlaps with Instagram audience
- Strengths: Growing platform, casual tone, integrated with Instagram
- Weaknesses: Still maturing, less developer-focused, algorithm-driven
- Best for: Consumer apps, visual apps, casual updates
- Time investment: 10-15 min/day
- Growth speed: Moderate (riding platform growth)

**Blog / Newsletter (Owned Platform)**
- Audience: Subscribers who opted in — highest intent
- Strengths: You own the audience, SEO benefits, long-form depth, email is reliable
- Weaknesses: Slow to build, requires consistent writing, higher effort per post
- Best for: Every app (this should be your long-term play, even if secondary)
- Platforms: Ghost, Buttondown, Substack, WordPress, or static site
- Time investment: 2-4 hours/week (one post per week)
- Growth speed: Very slow but most durable (6-12 months to meaningful audience)

#### Recommended Combinations

| Audience | Primary | Secondary |
|----------|---------|-----------|
| Developers | Twitter/X | Blog/newsletter |
| General consumers | Threads or Twitter/X | Newsletter |
| Privacy-conscious | Mastodon | Blog |
| Niche category | Reddit | Newsletter |
| Power users | Discord | Twitter/X |

### Step 3: Building in Public Strategy

Building in public means sharing your development journey transparently. It builds trust, creates accountability, and attracts early users.

#### What to Share

**High engagement (share often):**
- Progress updates with screenshots or short videos
- Design decisions and iterations (before/after)
- Milestones: download counts, revenue milestones, ratings
- Polls asking community to choose between features/designs
- Bugs you found and how you fixed them (relatable and educational)
- Weekly/monthly progress summaries

**Medium engagement (share periodically):**
- Revenue numbers and growth metrics (if comfortable)
- Lessons learned from mistakes
- Tools and processes you use
- App Store optimization experiments and results
- User testimonials and reviews

**Use sparingly:**
- Technical deep-dives (save for blog posts)
- Long threads (1-3 per month maximum)
- Philosophical musings about indie development

#### What NOT to Share

- Proprietary algorithms or trade secrets
- Features too far in advance (competitors watching, user expectations)
- Negative commentary about competitors
- Customer complaints or private messages
- Anything that could create legal liability
- Personal drama unrelated to the app journey

#### Transparency Levels

Choose your comfort level:

| Level | What You Share | Example |
|-------|---------------|---------|
| Fully transparent | Revenue, downloads, expenses, decisions | "March: $3,200 MRR, 847 subscribers, $400 in expenses" |
| Mostly transparent | Growth trends, decisions, learnings | "Crossed 800 subscribers this month, up 15% from February" |
| Selectively transparent | Progress, design, features | "Shipped the new dashboard this week, here's how it looks" |
| Journey-focused | Process, challenges, milestones | "Working on search — here's my approach to full-text indexing" |

All levels work. Pick what you are genuinely comfortable with and stay consistent.

### Step 4: Content Calendar (Realistic for Solo Developers)

This calendar assumes 3-5 hours per week total for community building.

#### Weekly Rhythm

| Day | Content Type | Time | Example |
|-----|-------------|------|---------|
| Monday | What I'm working on this week | 10 min | "This week: finishing the share sheet extension and fixing 3 bugs from user reports" |
| Wednesday | Tip, tutorial, or behind-the-scenes | 15 min | Screenshot of a SwiftUI trick, design iteration, or tool recommendation |
| Friday | Progress update or shipped feature | 15 min | "Shipped! Here's what's new in v2.3" or "Week in review: here's what got done" |

#### Monthly Additions

| Cadence | Content Type | Time | Example |
|---------|-------------|------|---------|
| 1st of month | Revenue/growth update | 30 min | Monthly metrics recap with takeaways |
| Mid-month | Blog post or tutorial | 2-3 hours | Technical post, lesson learned, or app development guide |
| End of month | Retrospective | 30 min | "What worked, what didn't, what's next" |

#### Batching Strategy

Do not create content in real-time throughout the week. Instead:

1. **Capture constantly**: Screenshot interesting moments as they happen (design iterations, bugs, metrics). Takes 30 seconds each.
2. **Batch create**: Dedicate 2 hours on Sunday (or whenever) to write all posts for the week using your captured screenshots.
3. **Schedule posts**: Use a scheduling tool (Buffer, Typefully, or native scheduling) so posts go out on the right days.
4. **Engage daily**: Spend 10-15 minutes responding to replies and engaging with others. This is separate from content creation.

### Step 5: Community Engagement Without Full-Time Effort

#### Daily Habits (10-15 minutes)

- Respond to every mention, reply, and DM (brevity is fine)
- Like/boost 3-5 posts from other developers in your space
- Comment genuinely on 2-3 posts from people you follow
- Check for your app's name/keywords