docs: add GROWTH.md — community visibility playbook

[Gingiris]

Hey mobile-use team! 👋

I'm a fan of what you're building — being the first to hit 100% on AndroidWorld is genuinely impressive.

I put together a GROWTH.md to help with community visibility and contributor growth. It's not a marketing doc; it's a practical playbook based on what I've seen work for similar open-source projects.

What's included:

• Awesome-list submission templates — Ready-to-use PRs for relevant curated lists (awesome-agents, Awesome-GUI-Agents, etc.)
• Content strategy — Where and what to post based on your audience
• Community building checklist — Contributor experience, Discord growth
• Metrics tracking — Simple framework to measure progress

Why I'm contributing:

mobile-use solves a real problem and has strong technical foundations. The benchmark results are compelling, but more people should know about this project.

Feel free to modify, expand, or completely rewrite this — it's just a starting point. Happy to discuss any suggestions!

---

This is a community contribution. No strings attached.

Summary by CodeRabbit

• Documentation
  • Added a comprehensive community visibility playbook with strategic guidance, high-impact visibility strategies, platform-specific content recommendations, community-building workflows, contributor onboarding steps, measurable metrics with target goals, communication rhythm suggestions, and reference resources for maintainers.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new GROWTH.md file has been added containing a comprehensive community visibility playbook. The document outlines strategic guidelines for mobile-use, including visibility checklists, content strategies, community-building workflows, metrics targets, communication rhythms, and reference resources for maintainers.

Changes

Cohort / File(s)	Summary
Documentation GROWTH.md	New community visibility playbook document with strategic guides, checklists, content strategies, community workflows, metrics, communication schedules, and reusable templates for maintainers.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A growth guide hops into view,
With checklists and strategies tried and true,
Community seeds we plant with care,
Visibility blooms everywhere,
Let's nurture and watch our garden grow! 🌱✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: add GROWTH.md — community visibility playbook' is clear, concise, and directly describes the main change: adding a documentation file for community growth strategy.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can scan for known vulnerabilities in your dependencies using OSV Scanner.

OSV Scanner will automatically detect and report security vulnerabilities in your project's dependencies. No additional configuration is required.

[coderabbitai]

🧹 Nitpick comments (1)

GROWTH.md (1)

79-81: Consider completing the baseline metrics before publishing.

Three metrics are marked "TBD" which limits the ability to track progress against goals. While it's fine to have this as a draft, completing these baselines would make the framework immediately actionable.

The following can be easily filled:

• PyPI weekly downloads: Check PyPI stats or use pip download counts
• Discord members: Check the Discord server member count
• Contributors: Run git shortlog -sn --all | wc -l to get current contributor count

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@GROWTH.md` around lines 79 - 81, Fill in the "TBD" baseline values in the
GROWTH.md metrics table for the rows "PyPI weekly downloads", "Discord members",
and "Contributors": fetch current PyPI weekly downloads (via pypistats.org or
pip/download counts) and place that number in the "Baseline" column for "PyPI
weekly downloads"; check the current Discord server member count and put it in
the "Baseline" for "Discord members"; compute current contributor count (e.g.,
run git shortlog -sn --all | wc -l) and insert that number as the "Baseline" for
"Contributors", then commit the updated table so progress targets become
actionable.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@GROWTH.md`:
- Around line 79-81: Fill in the "TBD" baseline values in the GROWTH.md metrics
table for the rows "PyPI weekly downloads", "Discord members", and
"Contributors": fetch current PyPI weekly downloads (via pypistats.org or
pip/download counts) and place that number in the "Baseline" column for "PyPI
weekly downloads"; check the current Discord server member count and put it in
the "Baseline" for "Discord members"; compute current contributor count (e.g.,
run git shortlog -sn --all | wc -l) and insert that number as the "Baseline" for
"Contributors", then commit the updated table so progress targets become
actionable.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 10936243-e73d-4a59-b4c4-858b9f4c48f5

📥 Commits

Reviewing files that changed from the base of the PR and between 1fd5723 and f55c652.

📒 Files selected for processing (1)

• GROWTH.md

[Gingiris]

Thanks for the review @coderabbitai! Good catch on the TBD metrics. Here are the actual baseline numbers:

• PyPI weekly downloads: ~14/week (last 7 days), ~43/month
• Discord members: checking with the team
• Contributors: will pull from GitHub insights

Will update the GROWTH.md with real numbers shortly.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@Gingiris Thanks for following up with the real baseline numbers! Those are useful starting points for the metrics section.

A couple of suggestions when you update GROWTH.md:

1. Format the baseline clearly so targets feel meaningful in context, e.g.:

   Metric	Baseline (Mar 2026)	30-day Target	90-day Target
   PyPI weekly downloads	~14/week	50/week	200/week
   PyPI monthly downloads	~43/month	200/month	800/month
   GitHub contributors	TBD	+3	+10
   Discord members	TBD	+25	+100

2. Consider linking to a live stats badge — services like pepy.tech or pypistats.org let you embed a live download badge in README.md, which also reinforces the community growth narrative directly on the project's landing page.

3. Once the Discord and contributors numbers are in, the metrics section will be fully grounded — looking forward to the update! 🐇

ʕ •ᴥ•ʔ