Setup
On first use, read setup.md for integration guidelines. Create ~/mobile-app-analytics/ if it doesn't exist.
When to Use
User needs to track, analyze, or optimize mobile app performance metrics. Agent handles Firebase Analytics queries, App Store Connect data, Play Console reports, retention analysis, funnel debugging, and cohort comparisons.
Architecture
Memory lives in ~/mobile-app-analytics/. See memory-template.md for setup.
CODEBLOCK0
Quick Reference
| Topic | File |
|---|
| Setup process | INLINECODE4 |
| Memory template |
memory-template.md |
| Firebase Analytics |
firebase.md |
| App Store Connect |
app-store.md |
| Play Console |
play-console.md |
| Core metrics |
metrics.md |
Core Rules
1. Platform Detection
Detect from context which platform(s) the app targets:
- - iOS only → focus on App Store Connect + Firebase
- Android only → focus on Play Console + Firebase
- Cross-platform → cover both stores + unified Firebase
2. Metric Hierarchy
Always prioritize metrics in this order:
- 1. Revenue metrics (LTV, ARPU, conversion) — what pays the bills
- Retention metrics (D1, D7, D30) — determines long-term success
- Engagement metrics (DAU/MAU, session length) — leading indicators
- Acquisition metrics (installs, sources) — growth levers
3. Cohort-First Analysis
Never report aggregate numbers alone. Always segment by:
- - Install cohort (when users joined)
- Acquisition source (organic, paid, referral)
- User tier (free, trial, paid)
- Platform (iOS vs Android)
4. Alert Thresholds
Proactively flag anomalies:
| Metric | Alert if |
|---|
| D1 retention | < 25% (below industry floor) |
| Crash-free rate |
< 99% |
| DAU/MAU ratio | Drops > 10% week-over-week |
| LTV:CAC ratio | < 3:1 |
5. Data Freshness
Know platform data delays:
| Source | Typical Delay |
|---|
| Firebase real-time | Minutes |
| Firebase daily reports |
24-48h for full data |
| App Store Connect | 24-48h |
| Play Console | 24-48h |
6. Privacy Compliance
- - Never track PII in custom events
- Respect ATT (iOS) and consent requirements
- User properties: demographics OK, personal identifiers NOT OK
- GDPR: support data deletion requests
7. Event Naming Conventions
Enforce consistent naming across platforms:
CODEBLOCK1
Common Traps
- - Vanity metrics obsession → Total downloads means nothing; track active users and retention instead
- Ignoring platform differences → iOS users often have 20-30% higher LTV; don't merge data blindly
- Wrong attribution window → 7-day attribution misses subscription conversions; use 30-day for subscriptions
- Survivorship bias → Analyzing only current users ignores why churned users left
- Timezone mismatches → Firebase uses UTC by default; App Store uses your configured timezone
External Endpoints
| Endpoint | Data Sent | Purpose |
|---|
| Firebase Analytics API | App ID, date range | Fetch metrics |
| App Store Connect API |
App ID, credentials | iOS analytics |
| Play Console API | App ID, credentials | Android analytics |
No other data is sent externally.
Security & Privacy
Data that leaves your machine:
- - Analytics queries to Firebase/Apple/Google APIs when you provide credentials
Data that stays local:
- - Your tracked apps and goals in INLINECODE10
- Benchmark comparisons and notes
This skill does NOT:
- - Store credentials (use your platform's standard credential methods)
- Access files outside INLINECODE11
- Make requests to undeclared endpoints
Scope
This skill ONLY:
- - Provides guidance on mobile app analytics platforms
- Stores your app configurations in INLINECODE12
- Queries Firebase, App Store Connect, and Play Console when you provide credentials
This skill NEVER:
- - Stores credentials in files (use environment variables)
- Accesses files outside INLINECODE13
- Makes requests to undeclared endpoints
- Modifies global agent memory or other skills
Related Skills
Install with
clawhub install <slug> if user confirms:
- -
app-store-connect — iOS App Store management - INLINECODE16 — Cross-platform app development
- INLINECODE17 — SaaS business metrics and growth
Feedback
- - If useful: INLINECODE18
- Stay updated: INLINECODE19
技能名称:移动应用分析
详细描述:
设置
首次使用时,请阅读 setup.md 了解集成指南。如果 ~/mobile-app-analytics/ 目录不存在,请手动创建。
使用场景
当用户需要追踪、分析或优化移动应用性能指标时使用。本技能可处理 Firebase Analytics 查询、App Store Connect 数据、Play Console 报告、留存分析、漏斗调试以及同期群对比。
架构
数据存储在 ~/mobile-app-analytics/ 目录中。请参阅 memory-template.md 了解设置方法。
~/mobile-app-analytics/
├── memory.md # 追踪的应用、目标、告警
├── apps/ # 每个应用的分析配置
│ └── {app-name}.md # 每个应用的事件、漏斗、KPI
└── benchmarks.md # 行业基准参考
快速参考
memory-template.md |
| Firebase Analytics | firebase.md |
| App Store Connect | app-store.md |
| Play Console | play-console.md |
| 核心指标 | metrics.md |
核心规则
1. 平台检测
根据上下文检测应用的目标平台:
- - 仅 iOS → 重点关注 App Store Connect + Firebase
- 仅 Android → 重点关注 Play Console + Firebase
- 跨平台 → 覆盖两个商店 + 统一 Firebase
2. 指标优先级
始终按以下顺序优先处理指标:
- 1. 收入指标(LTV、ARPU、转化率)—— 决定收入来源
- 留存指标(D1、D7、D30)—— 决定长期成功
- 参与度指标(DAU/MAU、会话时长)—— 领先指标
- 获客指标(安装量、来源)—— 增长杠杆
3. 同期群优先分析
切勿仅报告汇总数据。始终按以下维度进行细分:
- - 安装同期群(用户加入时间)
- 获客来源(自然流量、付费、推荐)
- 用户层级(免费、试用、付费)
- 平台(iOS vs Android)
4. 告警阈值
主动标记异常情况:
| 指标 | 告警条件 |
|---|
| D1 留存率 | < 25%(低于行业底线) |
| 无崩溃率 |
< 99% |
| DAU/MAU 比率 | 周环比下降 > 10% |
| LTV:CAC 比率 | < 3:1 |
5. 数据时效性
了解平台数据延迟情况:
| 来源 | 典型延迟 |
|---|
| Firebase 实时数据 | 分钟级 |
| Firebase 每日报告 |
完整数据需 24-48 小时 |
| App Store Connect | 24-48 小时 |
| Play Console | 24-48 小时 |
6. 隐私合规
- - 切勿在自定义事件中追踪个人身份信息(PII)
- 遵守 ATT(iOS)和用户同意要求
- 用户属性:允许人口统计信息,禁止个人标识符
- GDPR:支持数据删除请求
7. 事件命名规范
确保跨平台命名一致:
{动词}{名词}[{限定词}]
示例:
- - viewscreenhome
- tapbuttonsubscribe
- completepurchaseannual
- startonboardingstep1
常见陷阱
- - 沉迷虚荣指标 → 总下载量毫无意义;应追踪活跃用户和留存率
- 忽视平台差异 → iOS 用户的 LTV 通常高出 20-30%;切勿盲目合并数据
- 错误的归因窗口 → 7 天归因会遗漏订阅转化;订阅类应使用 30 天窗口
- 幸存者偏差 → 仅分析当前用户会忽略流失用户的离开原因
- 时区不匹配 → Firebase 默认使用 UTC;App Store 使用你配置的时区
外部端点
| 端点 | 发送数据 | 用途 |
|---|
| Firebase Analytics API | 应用 ID、日期范围 | 获取指标 |
| App Store Connect API |
应用 ID、凭据 | iOS 分析 |
| Play Console API | 应用 ID、凭据 | Android 分析 |
不向外部发送其他数据。
安全与隐私
离开你设备的数据:
- - 当你提供凭据时,向 Firebase/Apple/Google API 发送的分析查询
保留在本地的数据:
- - ~/mobile-app-analytics/ 中你追踪的应用和目标
- 基准比较和笔记
本技能不会:
- - 存储凭据(请使用你平台的标准凭据方法)
- 访问 ~/mobile-app-analytics/ 之外的文件
- 向未声明的端点发送请求
范围
本技能仅:
- - 提供移动应用分析平台的指导
- 在 ~/mobile-app-analytics/ 中存储你的应用配置
- 在你提供凭据时查询 Firebase、App Store Connect 和 Play Console
本技能绝不:
- - 在文件中存储凭据(请使用环境变量)
- 访问 ~/mobile-app-analytics/ 之外的文件
- 向未声明的端点发送请求
- 修改全局代理记忆或其他技能
相关技能
如果用户确认,使用 clawhub install
安装:
- - app-store-connect — iOS App Store 管理
- flutter — 跨平台应用开发
- saas — SaaS 业务指标与增长
反馈
- - 如果觉得有用:clawhub star mobile-app-analytics
- 保持更新:clawhub sync