> ## Documentation Index
> Fetch the complete documentation index at: https://base-a060aa97-eb-mini-app-ia-overhaul.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Build Viral Mini Apps

> Designing mini apps that people actually come back to

**Designing mini apps that people actually come back to.**

Most apps can launch. But few become part of someone's daily rhythm.\
That's usually not a product problem. It's a people problem.

Social mini apps live or die based on how they make people feel: seen, connected, curious or like they belong. That's not something you tack on — it's something you build in from the start.

If you're designing for feed-based platforms (like Farcaster, Threads, or anything with posts, reactions, and reply chains), this guide will help you:

<CardGroup cols={3}>
  <Card title="Challenge your idea early" icon="magnifying-glass" />

  <Card title="Apply the right social patterns" icon="puzzle-piece" />

  <Card title="Build for behaviors, not just features" icon="users" />
</CardGroup>

## How to Use This Guide

Welcome to your blueprint for designing social mini‑apps that people love to revisit. This guide is organized into distinct, actionable sections—each building on the last—to help you move from idea validation to deploying social features with purpose.

<Steps>
  <Step title="Pressure‑Test Your Idea">
    Before writing a single line of code or sketching UI, use our four diagnostic questions to see if your concept naturally supports social behavior. Drop your one‑line idea into the supplied prompt to get clear insights on post frequency, social lift, content momentum, and emotional payoff.
  </Step>

  <Step title="Interpret Feedback & Choose Dimensions">
    Analyze the responses. Identify which one or two social dimensions resonate
    most with your concept—whether it's habit formation, community spark, content
    growth, or emotional reward. The guide shows you how to validate and
    prioritize those dimensions before moving forward.
  </Step>

  <Step title="Apply a Case Study Flow">
    See a worked example that demonstrates how to translate test results into a
    prototype feature. This mini case study will illustrate rapid iteration,
    metric considerations, and how to decide when you're ready to scale social
    elements.
  </Step>

  <Step title="Explore Three Core Patterns">
    Dive into the heart of the guide—three social patterns designed to deepen engagement:

    * **Identity Playgrounds:** Customization and self‑expression
    * **Co‑Creation Loops:** Collaboration and building on each other's posts
    * **Long‑Term Rituals:** Scheduled, shared activities that foster habit and community

    Each pattern includes explanations, real‑world examples, and copy‑and‑paste prompts to spark your own brainstorming.
  </Step>

  <Step title="Next Steps & Reflection">
    Finish with a set of reflective questions and practical advice on measuring success. Use the closing prompts to refine your roadmap, plan experiments, and define key metrics for daily, weekly, and monthly engagement.
  </Step>
</Steps>

<Tip>
  **Tips for Getting the Most Out of This Guide:**

  * **Iterate Quickly:** Treat prompts and patterns as hypotheses. Prototype fast, gather data, and refine.
  * **Stay Human‑Centered:** At every stage, ask: "How will this make someone feel?"
  * **Measure What Matters:** Define metrics for each dimension early—then use them to validate your choices.
  * **Keep It Simple:** You don't need every pattern at once. Start with the one or two dimensions that align strongest with your concept.
</Tip>

## Pressure-test your idea

Before you get into features or UI, take a step back. Ask whether your idea wants to be social — or if you're forcing it. These prompts are designed to give you structured, clear feedback if you drop them into a LLM or use them in your own reflection.

```
Here's a one-line description of my app: [insert idea].

Evaluate it across these questions:

1. Why would someone post here more than once?
2. Would the experience be better with another person involved?
3. What kind of content might naturally fill the feed over time?
4. What emotional reward might someone feel when they open it?

Please be direct. If the idea lacks natural social behavior, suggest ways it could evolve.
```

## Social Patterns

### 1. Identity Playgrounds

**The idea:** Give people ways to explore, express, or shape their identity within the app.

**Why it works:** People don't just use feeds to consume — they use them to perform. Customization invites play, self-expression, and experimentation.

**Where it shows up:** Discord roles, Reddit flair, Tumblr themes.

**Use it for:** Differentiation, emotional investment, repeat posting.

```
Given my app idea: [insert idea], explore 2 ways users might express or explore identity.

For each, include:
– What the user customizes or signals
– How that shows up in the feed
– Why that might matter over time
```

### 2. Co-Creation Loops

**The idea:** Design behaviors that are better when shared — where users build on each other's contributions.

**Why it works:** The strongest feeds don't just display content; they build momentum. If one person's post sparks another, you get a chain reaction.

**Where it shows up:** Remix threads, collab playlists, group journaling.

**Use it for:** Participation loops, content momentum, chain reactions.

```
How could users in [insert app idea] create something together or build on each other's actions?
Return 3 co-creation flows that include:
– What kicks it off
– How others join in
– What the feed looks like after a few days
```

### 3. Long-Term Rituals

**The idea:** Introduce regular, shared behaviors that become a rhythm.

**Why it works:** Rituals create predictability, belonging, and anticipation. They give users a reason to come back on a schedule.

**Where it shows up:** Wordle scores, Monday memes, Friday drops, yearly Spotify Wrapped.

**Use it for:** Habit loops, appointment-based engagement, social cohesion.

```
Design 2 recurring rituals for [insert app idea].

For each, include:
– Frequency (daily, weekly, monthly)
– What users post
– What emotion or payoff they get
– How it could spread through the feed
```

## Interpreting your feedback

After you get back raw answers to the four pressure‑test questions, look for the one or two dimensions that most naturally fit your idea. Nail those first, then decide if you need to shore up any others.

<Steps>
  <Step title="Spot your top dimensions">
    Scan your AI responses for signs of strength in these four key areas:

    <CardGroup cols={2}>
      <Card title="Repeat‑posting potential" icon="refresh">
        **Look for:** "Daily check‑ins create habit" or "Natural reason to post weekly"
      </Card>

      <Card title="Social lift" icon="users">
        **Look for:** "Comments spark friendly competition" or "Better with others
        involved"
      </Card>

      <Card title="Content momentum" icon="chart-line">
        **Look for:** "Automated reminders nudge new posts" or "Community‑driven
        growth"
      </Card>

      <Card title="Emotional payoff" icon="heart">
        **Look for:** "Badges tap into achievement" or "Pride in sharing progress"
      </Card>
    </CardGroup>

    <Tip>
      Focus on the dimensions where the AI feedback was most enthusiastic and specific. Vague responses usually indicate weak social potential.
    </Tip>
  </Step>

  <Step title="Validate your winners">
    For each dimension that scored well, confirm the feedback includes clear, actionable examples:

    <AccordionGroup>
      <Accordion title="Repeat‑posting validation">
        **Strong signal:** At least 1 post per week feels natural to users

        **Examples to look for:**

        * "Users would naturally share daily progress"
        * "Weekly challenges create posting rhythm"
        * "Status updates become habitual"

        **Red flag:** Forced or infrequent posting suggestions
      </Accordion>

      <Accordion title="Social lift validation">
        **Strong signal:** Others are meaningfully involved, not just passive viewers

        **Examples to look for:**

        * "Friends can collaborate on projects"
        * "Comments turn into conversations"
        * "Peer reactions drive engagement"

        **Red flag:** Social features feel like an afterthought
      </Accordion>

      <Accordion title="Content momentum validation">
        **Strong signal:** Community‑driven growth that builds over time

        **Examples to look for:**

        * "Posts inspire similar content from others"
        * "Trending topics emerge naturally"
        * "User‑generated content feeds itself"

        **Red flag:** Content relies entirely on individual creators
      </Accordion>

      <Accordion title="Emotional payoff validation">
        **Strong signal:** Opening the app delivers a felt reward

        **Examples to look for:**

        * "Users feel proud sharing progress"
        * "Achievements create satisfaction"
        * "Community recognition feels meaningful"

        **Red flag:** Emotional benefits are unclear or generic
      </Accordion>
    </AccordionGroup>
  </Step>

  <Step title="Decide your next move">
    Now that you've identified your strongest dimensions, here's how to proceed:

    <Tabs>
      <Tab title="Strong Dimensions (2+)">
        **You're ready to build!**

        If your top 1–2 dimensions check out, skip straight to building social features around them. You don't need to perfect all four dimensions before starting.

        <Check>
          Focus your energy on the social angles that truly resonate with your concept first.
        </Check>
      </Tab>

      <Tab title="Weak Dimensions (0-1)">
        **Iterate before building**

        If your dimensions are weak, spend time strengthening them before moving to development:

        * **Add a relational hook** (how do others get involved?)
        * **Include a habit prompt** (what brings people back?)
        * **Create emotional stakes** (why should users care?)

        <Warning>
          Don't force social features onto an inherently solo experience. Consider if your idea needs to evolve.
        </Warning>
      </Tab>
    </Tabs>

    **Example Decision Flow:**

    You see strong **"Social lift"** ("Friends' reactions spark threads") and decent **"Emotional payoff"** ("Likes feel rewarding").

    ✅ **Decision:** Prototype a co‑posting feature focusing on these strengths

    ⏳ **Later:** Explore "Content momentum" and "Repeat‑posting" patterns once core social features are solid

    <Info>
      This focused approach prevents feature bloat and ensures you build social mechanics that actually work for your specific concept.
    </Info>
  </Step>
</Steps>

## Closing note

The mini apps that thrive aren't the most complex — they're the ones that understand how people connect.

<Note>
  **Remember:**

  * Social features only work when they reflect real human behavior
  * A feed isn't just content — it's a shared ritual
  * True engagement comes from meaning over mechanics
</Note>

As you build, ask: *Why would someone want to come back? Why would they share this with a friend?* Those answers matter more than any feature list.

The best apps don't just fill feeds. They create places people want to return to.\
So — what will your app make people feel?