Back to Details

aso-audit

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

ASO Audit

ASO审计

Analyze App Store and Google Play listings against ASO best practices. Fetches live listing data, scores metadata, visuals, and ratings, then produces a prioritized action plan.
依据ASO最佳实践分析App Store和Google Play应用列表。获取实时列表数据，对元数据、视觉素材和评分进行打分，然后生成优先级明确的行动计划。

When to Use

使用场景

  • User shares an App Store or Google Play URL
  • User asks to audit or optimize an app listing
  • User wants to compare their app against competitors
  • User asks about app store ranking, visibility, or download conversion
  • 用户分享App Store或Google Play链接
  • 用户要求审计或优化应用列表
  • 用户希望将自己的应用与竞品对比
  • 用户询问应用商店排名、曝光度或下载转化率相关问题

Before Auditing

审计前准备

Check for product marketing context first: If 
.agents/product-marketing-context.md
exists (or 
.claude/product-marketing-context.md
in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
首先检查产品营销背景信息： 如果存在
.agents/product-marketing-context.md
（旧版配置中为
.claude/product-marketing-context.md
），请在提问前阅读该文件。利用其中的背景信息，仅询问文件未涵盖或与本次任务相关的特定信息。

Phase 1 — Identify Store & Fetch

第一阶段 — 识别商店类型并获取数据

Detect store type from URL

通过URL识别商店类型

Apple:  apps.apple.com/{country}/app/{name}/id{digits}
Google: play.google.com/store/apps/details?id={package}
If the user gives an app name instead of a URL, search the web for: 
site:apps.apple.com "{app name}"
or 
site:play.google.com "{app name}"
Apple:  apps.apple.com/{country}/app/{name}/id{digits}
Google: play.google.com/store/apps/details?id={package}
如果用户仅提供应用名称而非URL，请通过以下关键词在网页搜索： 
site:apps.apple.com "{应用名称}"
或 
site:play.google.com "{应用名称}"

Fetch the listing

获取应用列表数据

Use WebFetch to retrieve the listing page. Extract every available field:
Apple App Store fields:
  • App name (title) — 30 char limit
  • Subtitle — 30 char limit
  • Description (long) — not indexed for search, but matters for conversion
  • Promotional text — 170 chars, updatable without new release
  • Category (primary + secondary)
  • Screenshots (count, order, caption text)
  • Preview video (presence, duration)
  • Rating (average + count)
  • Recent reviews (visible ones)
  • Price / in-app purchases
  • Developer name
  • Last updated date
  • Version history notes
  • Age rating
  • Size
  • Languages / localizations listed
  • In-app events (if any visible)
Google Play fields:
  • App name (title) — 30 char limit
  • Short description — 80 char limit
  • Full description — 4,000 char limit, IS indexed for search
  • Category + tags
  • Feature graphic (presence)
  • Screenshots (count, order)
  • Preview video (presence)
  • Rating (average + count)
  • Recent reviews (visible ones)
  • Price / in-app purchases
  • Developer name
  • Last updated date
  • What's new text
  • Downloads range
  • Content rating
  • Data safety section
  • Languages listed
If WebFetch returns incomplete data (stores render client-side), note gaps and work with what's available. Ask the user to paste missing fields if critical.
使用WebFetch工具获取列表页面，提取所有可用字段：
Apple App Store字段：
  • 应用名称（标题）—— 30字符限制
  • 副标题 —— 30字符限制
  • 详细描述 —— 不参与搜索索引，但影响转化率
  • 推广文本 —— 170字符，无需发布新版本即可更新
  • 品类（主品类+副品类）
  • 截图（数量、排序、说明文字）
  • 预览视频（是否存在、时长）
  • 评分（平均分+评分数量）
  • 近期评论（可见的评论）
  • 价格/内购项目
  • 开发者名称
  • 最后更新日期
  • 版本更新说明
  • 年龄分级
  • 应用大小
  • 支持的语言/本地化版本
  • 应用内活动（如有可见的）
Google Play字段：
  • 应用名称（标题）—— 30字符限制
  • 短描述 —— 80字符限制
  • 完整描述 —— 4000字符限制，参与搜索索引
  • 品类+标签
  • 首屏横幅图（是否存在）
  • 截图（数量、排序）
  • 预览视频（是否存在）
  • 评分（平均分+评分数量）
  • 近期评论（可见的评论）
  • 价格/内购项目
  • 开发者名称
  • 最后更新日期
  • 新版本说明
  • 下载量区间
  • 内容分级
  • 数据安全板块
  • 支持的语言
如果WebFetch返回的数据不完整（商店采用客户端渲染），请记录缺失的内容，并基于现有数据开展工作。若缺失内容至关重要，请请求用户提供相关字段信息。

Visual asset assessment

视觉素材评估

WebFetch cannot extract screenshot images or caption text. Take a screenshot of the listing page to get visual data:
  1. Navigate to the listing URL and capture a full-page screenshot
  2. Assess the screenshot for: icon quality, screenshot count, caption text, messaging quality, preview video presence, feature graphic (Google Play)
  3. If browser tools are unavailable, ask the user to share a screenshot of the listing page
Promotional text (Apple): This 170-char field appears above the description but is often indistinguishable from it in scraped HTML. If you cannot confirm its presence, note this and recommend the user check App Store Connect.
WebFetch无法提取截图图片或说明文字。请截取列表页面的截图以获取视觉数据：
  1. 访问列表URL并截取完整页面截图
  2. 评估截图内容：图标质量、截图数量、说明文字、信息传递质量、预览视频是否存在、首屏横幅图（Google Play）
  3. 若无法使用浏览器工具，请请求用户分享列表页面的截图
Apple推广文本： 这个170字符的字段显示在详细描述上方，但在抓取的HTML中通常难以与描述区分。如果无法确认其是否存在，请记录这一点并建议用户在App Store Connect中查看。

Phase 1.5 — Assess Brand Maturity

第一阶段补充 — 评估品牌成熟度

Before scoring, classify the app into one of three tiers. This determines how you interpret "textbook ASO" deviations — a deliberate brand choice by a household name is not the same as a missed opportunity by an unknown app.
在打分前，将应用分为三个层级。这将决定你如何看待与“标准ASO规范”的偏差——头部品牌的刻意品牌选择，与小众应用的优化疏漏性质完全不同。

Tier definitions

层级定义

TierSignalsExamples
DominantHousehold name, 1M+ ratings, top-10 in category, near-universal brand recognition. Users search by brand name, not generic keywords.Instagram, Uber, Spotify, WhatsApp, Netflix
EstablishedWell-known in their category, 100K+ ratings, strong organic installs, recognized brand but not universally known.Strava, Notion, Duolingo, Cash App, Calm
ChallengerBuilding awareness, <100K ratings, needs discovery through keywords and ASO tactics. Most apps fall here.Your app, most indie/startup apps
应用层级判断信号示例
头部应用家喻户晓的品牌，100万+评分，品类Top10，品牌认知度近乎普及。用户通过品牌名称搜索，而非通用关键词。Instagram、Uber、Spotify、WhatsApp、Netflix
腰部应用在所属品类中知名度较高，10万+评分，自然安装量稳定，品牌有一定认知度但未达到全民普及。Strava、Notion、Duolingo、Cash App、Calm
潜力型应用正在积累品牌知名度，评分少于10万，需要通过关键词和ASO策略获取曝光。大多数应用属于此类。你的应用、大多数独立/初创应用

How tier affects scoring

层级对打分的影响

Dominant apps get adjusted scoring in these areas:
  • Title: Brand-only or brand-first titles are valid (score 8+ if brand is the keyword). These apps don't need generic keyword discovery.
  • Description: Score purely on conversion quality, not keyword presence. If the app is a household name, a well-crafted brand description beats a keyword-stuffed one.
  • Visual Assets: Lifestyle/brand photography instead of UI demos is a legitimate conversion strategy. No video is acceptable if the product is hard to demo in 30s or brand awareness is near-universal.
  • What's New: Generic release notes at weekly+ cadence are acceptable (score 8+). At scale, detailed changelogs have minimal ROI and risk backlash.
  • In-app events: Missing events for utility apps with massive install bases (Uber, WhatsApp) is not a penalty. These apps don't need discovery help.
  • Localization: Score relative to actual market, not absolute count. A US-only fintech with 2 languages (English + Spanish) is appropriately localized.
Established apps get partial adjustment:
  • Brand-first titles are fine but should still include 1-2 keywords
  • Strategic description choices get benefit of the doubt
  • Other dimensions scored normally
Challenger apps are scored strictly against textbook ASO best practices — every character, screenshot, and keyword matters.
Key principle: Before docking points, ask: "Is this a mistake or a deliberate choice by a team that has data I don't?" If the app has 1M+ ratings and a dedicated ASO team, assume their choices are data-informed unless clearly wrong.
头部应用在以下领域的打分将进行调整：
  • 标题： 仅包含品牌名或品牌优先的标题是有效的（如果品牌本身就是核心关键词，得分8分以上）。这类应用无需依赖通用关键词获取曝光。
  • 描述： 仅基于转化质量打分，不考虑关键词是否存在。如果应用是家喻户晓的品牌，精心打造的品牌描述优于堆砌关键词的描述。
  • 视觉素材： 使用生活方式/品牌摄影而非UI演示是合理的转化策略。如果产品难以在30秒内演示，或品牌知名度近乎普及，没有预览视频也可接受。
  • 新版本说明： 每周或更频繁发布的通用版本说明是可接受的（得分8分以上）。在大规模用户体量下，详细的更新日志投资回报率极低，还可能引发用户不满。
  • 应用内活动： 头部工具类应用（如Uber、WhatsApp）没有应用内活动不会被扣分。这类应用无需借助活动获取曝光。
  • 本地化： 根据实际目标市场打分，而非绝对的语言数量。仅面向美国市场的金融科技应用支持英语+西班牙语两种语言，即属于合理的本地化配置。
腰部应用的打分进行部分调整：
  • 品牌优先的标题是可行的，但仍应包含1-2个关键词
  • 对于有策略的描述选择，给予容错空间
  • 其他维度按照标准打分
潜力型应用严格按照标准ASO最佳实践打分——每个字符、每张截图、每个关键词都至关重要。
核心原则： 在扣分前，请先思考：“这是失误，还是拥有我所不了解的数据的团队做出的刻意选择？” 如果应用拥有100万+评分，且有专门的ASO团队，请默认其选择是基于数据的，除非明显存在错误。

Phase 2 — Score Each Dimension

第二阶段 — 各维度打分

Score each dimension 0-10 using the criteria in 
references/scoring-criteria.md
. Apply the brand maturity tier adjustments from Phase 1.5.
Reference files for platform specs and benchmarks:
  • references/apple-specs.md
    — Official Apple character limits, screenshot/video specs, CPP/PPO rules, rejection triggers
  • references/google-play-specs.md
    — Official Google Play limits, screenshot specs, Android Vitals thresholds, policies
  • references/benchmarks.md
    — Conversion data, rating impact, video lift, screenshot behavior, CPP/event benchmarks
使用
references/scoring-criteria.md
中的标准，对每个维度进行0-10分的打分。同时结合第一阶段补充的品牌成熟度层级调整打分结果。
参考文件中的平台规范和基准数据：
  • references/apple-specs.md
    —— Apple官方字符限制、截图/视频规范、CPP/PPO规则、拒绝审核的触发因素
  • references/google-play-specs.md
    —— Google Play官方限制、截图规范、Android Vitals阈值、政策要求
  • references/benchmarks.md
    —— 转化率数据、评分影响、视频提升效果、截图表现、CPP/活动基准

Dimensions and Weights

维度与权重

#DimensionWeightWhat It Covers
1Title & Subtitle20%Character usage, keyword presence, clarity, brand + keyword balance
2Description15%First 3 lines, keyword density (Google), CTA, structure, promotional text
3Visual Assets25%Screenshot count/quality/messaging, video, icon, feature graphic
4Ratings & Reviews20%Average rating, volume, recency, developer responses
5Metadata & Freshness10%Category choice, update recency, localization count, data safety
6Conversion Signals10%Price positioning, IAP transparency, social proof, download range
Final score = weighted sum, out of 100.
序号维度权重涵盖内容
1标题与副标题20%字符利用率、关键词覆盖、清晰度、品牌与关键词的平衡
2描述内容15%前3行内容、关键词密度（Google）、行动号召、结构、推广文本
3视觉素材25%截图数量/质量/信息传递、视频、图标、首屏横幅图
4评分与评论20%平均评分、评分数量、时效性、开发者回复情况
5元数据与新鲜度10%品类选择、更新频率、本地化数量、数据安全
6转化信号10%价格定位、内购透明度、社交证明、下载量区间
最终得分 = 加权总和，满分100分。

Score interpretation

得分解读

ScoreGradeMeaning
85-100AWell-optimized; focus on A/B testing and iteration
70-84BGood foundation; clear opportunities to improve
50-69CSignificant gaps; prioritized fixes will have high impact
30-49DMajor optimization needed across multiple dimensions
0-29FListing needs a complete overhaul
得分范围评级含义
85-100A级优化完善；重点关注A/B测试和迭代优化
70-84B级基础良好；存在明确的优化空间
50-69C级存在显著差距；优先修复的问题将带来高回报
30-49D级多个维度需要重大优化
0-29F级应用列表需要全面改版

Phase 3 — Competitor Comparison (Optional)

第三阶段 — 竞品对比（可选）

If the user provides competitor URLs or asks for comparison:
  1. Fetch 2-3 top competitors in the same category
  2. Run the same scoring on each
  3. Build a comparison table highlighting where the user's app is weaker/stronger
  4. Identify keyword gaps — terms competitors rank for that the user's app doesn't target
If no competitors are specified, suggest the user provide 2-3 or offer to search for top apps in their category.
如果用户提供竞品URL或要求进行对比：
  1. 获取同一品类中的2-3个头部竞品
  2. 对每个竞品执行相同的打分流程
  3. 制作对比表格，突出用户应用的优势与不足
  4. 识别关键词差距——竞品排名靠前但用户应用未覆盖的关键词
如果用户未指定竞品，请建议用户提供2-3个竞品，或主动搜索该品类的头部应用。

Phase 4 — Generate Report

第四阶段 — 生成报告

Use the template in 
references/report-template.md
to structure the output.
The report must include:
  1. Score card — table with all 6 dimensions, scores, and grade
  2. Top 3 quick wins — changes that take <1 hour and have highest impact
  3. Detailed findings — per-dimension breakdown with specific issues and fixes
  4. Keyword suggestions — based on title/description analysis and competitor gaps
  5. Visual asset recommendations — specific screenshot/video improvements
  6. Priority action plan — ordered list of changes by impact vs effort
使用
references/report-template.md
中的模板构建输出内容。
报告必须包含：
  1. 得分卡片 —— 包含6个维度、得分和评级的表格
  2. 3个快速优化建议 —— 耗时少于1小时且影响最大的调整
  3. 详细发现 —— 按维度拆解的具体问题和修复方案
  4. 关键词建议 —— 基于标题/描述分析和竞品差距的推荐
  5. 视觉素材优化建议 —— 针对截图/视频的具体改进方向
  6. 优先级行动计划 —— 按影响与投入比排序的调整清单

Report rules

报告规则

  • Every recommendation must be specific and actionable ("Change subtitle from X to Y" not "Improve subtitle")
  • Include character counts for all text recommendations
  • Flag platform-specific differences (Apple vs Google) when relevant
  • Note what CANNOT be assessed without paid tools (search volume, exact rankings)
  • When suggesting keyword changes, explain WHY each keyword matters
  • 所有建议必须具体且可执行（例如：“将副标题从X修改为Y”，而非“优化副标题”）
  • 所有文本建议需包含字符数统计
  • 相关时需标注平台差异（Apple vs Google）
  • 注明哪些内容无法通过免费工具评估（搜索量、精确排名）
  • 建议关键词时，需解释每个关键词的重要性

Platform-Specific Rules

平台特定规则

Apple App Store — Key Facts

Apple App Store — 关键要点

  • Title (30 chars) + Subtitle (30 chars) + Keyword field (100 bytes, hidden) = indexed text
  • Keywords field is bytes not chars — Arabic/CJK use 2-3 bytes per char
  • Long description is NOT indexed for search — optimize for conversion only
  • Promotional text (170 chars) does NOT affect search (Apple confirmed)
  • Never repeat words across title/subtitle/keyword field (Apple indexes each word once)
  • Keyword field: commas, no spaces ("photo,editor,filter" not "photo, editor, filter")
  • Screenshots: up to 10 per device. First 3 visible in search — 90% never scroll past 3rd
  • Screenshot captions indexed since June 2025 (AI extraction)
  • In-app events: max 10 published at once, max 31 days each. Indexed and appear in search
  • Custom Product Pages (up to 70) in organic search since July 2025. +5.9% avg conversion lift
  • App preview video: up to 3, 15-30s each. Autoplays muted — +20-40% conversion lift
  • SKStoreReviewController: max 3 prompts per 365 days
  • Apple has human editorial curation — quality and design matter more
  • See 
    references/apple-specs.md
    for full specs, dimensions, and rejection triggers
  • 标题（30字符）+ 副标题（30字符）+ 关键词字段（100字节，隐藏）= 参与索引的文本
  • 关键词字段按字节计算，而非字符——阿拉伯语/中日韩字符占2-3字节
  • 详细描述不参与搜索索引——仅针对转化率优化
  • 推广文本（170字符）不影响搜索排名（Apple官方确认）
  • 请勿在标题/副标题/关键词字段中重复使用相同词汇（Apple仅对每个词汇索引一次）
  • 关键词字段：使用逗号分隔，无空格（例如"photo,editor,filter"而非"photo, editor, filter"）
  • 截图：每款设备最多10张。搜索结果中仅显示前3张——90%的用户不会滚动查看第3张之后的内容
  • 截图说明文字自2025年6月起参与索引（AI提取）
  • 应用内活动：最多同时发布10个，每个最长31天。参与索引并出现在搜索结果中
  • 自定义产品页面（最多70个）自2025年7月起参与自然搜索。平均提升5.9%的转化率
  • 应用预览视频：最多3个，每个15-30秒。自动静音播放——提升20-40%的转化率
  • SKStoreReviewController：每365天最多提示3次评分
  • Apple有人工审核——质量和设计更为重要
  • 完整规范、尺寸和审核拒绝触发因素请查看
    references/apple-specs.md

Google Play — Key Facts

Google Play — 关键要点

  • Title (30 chars) + Short description (80 chars) + Full description (4,000 chars) = indexed text
  • Full description IS indexed — target 2-3% keyword density naturally
  • No hidden keyword field — all keywords must be in visible text
  • Google NLP/semantic understanding — keyword stuffing detected and penalized
  • Prohibited in title: emojis, ALL CAPS, "best"/"#1"/"free", CTAs (enforced since 2021)
  • Screenshots: min 2, max 8 per device (not 10 like Apple)
  • Feature graphic (1024x500, exact) required for featured placements
  • Video does NOT autoplay — only ~6% of users tap play (low ROI vs iOS)
  • Android Vitals directly affect ranking: crash >1.09% or ANR >0.47% = reduced visibility
  • Promotional Content: submit 14 days early for featuring. Apps see 2x explore acquisitions
  • Custom Store Listings: up to 50 (can target churned users, specific countries, ad campaigns)
  • Store Listing Experiments: test up to 3 variants, run 7+ days, 1 experiment at a time
  • See 
    references/google-play-specs.md
    for full specs and policy details
  • 标题（30字符）+ 短描述（80字符）+ 完整描述（4000字符）= 参与索引的文本
  • 完整描述参与索引——自然地将关键词密度控制在2-3%
  • 无隐藏关键词字段——所有关键词必须出现在可见文本中
  • Google采用NLP/语义理解——关键词堆砌会被检测并处罚
  • 标题禁用内容：表情符号、全大写、“最佳”/“排名第一”/“免费”、行动号召（2021年起强制执行）
  • 截图：每款设备最少2张，最多8张（不同于Apple的10张）
  • 首屏横幅图（1024x500像素，精确尺寸）是获得推荐位的必要条件
  • 视频不会自动播放——仅约6%的用户会点击播放（与iOS相比投资回报率低）
  • Android Vitals直接影响排名：崩溃率>1.09%或ANR>0.47% = 曝光度降低
  • 推广内容：需提前14天提交以获得推荐。应用可获得2倍的探索页安装量
  • 自定义商店列表：最多50个（可针对流失用户、特定国家、广告活动设置）
  • 商店列表实验：最多测试3个变体，需运行7天以上，同一时间仅能进行1个实验
  • 完整规范和政策细节请查看
    references/google-play-specs.md

What Apple Indexes vs What Google Indexes

Apple与Google索引字段对比

FieldApple Indexed?Google Indexed?
TitleYesYes (strongest signal)
Subtitle / Short descYesYes
Keyword fieldYes (hidden)Does not exist
Long descriptionNoYes (heavily)
Screenshot captionsYes (since 2025)No
In-app eventsYesN/A (LiveOps instead)
Developer nameNoPartial
IAP namesYesYes
字段Apple是否索引Google是否索引
标题是是（最强信号）
副标题/短描述是是
关键词字段是（隐藏）无此字段
详细描述否是（权重高）
截图说明文字是（2025年起）否
应用内活动是不适用（对应LiveOps）
开发者名称否部分索引
内购项目名称是是

Common Issues Checklist

常见问题检查清单

Flag these if found. Items marked (tier-dependent) should be evaluated against the app's brand maturity tier — they may be deliberate choices for Dominant apps.
Always flag (all tiers):
  • Rating below 4.0
  • Last update > 3 months ago
  • Google Play description has no keyword strategy (under 1% density)
  • Google Play missing feature graphic
  • Apple keyword field likely has repeated words (inferred from title+subtitle)
  • Category mismatch — app would face less competition in a different category
  • Fewer than 5 screenshots
Flag for Challenger/Established only (not mistakes for Dominant apps):
  • Title wastes characters on brand name only (no keywords) (Dominant: brand IS the keyword)
  • Subtitle/short description duplicates title keywords
  • Description first 3 lines are generic (Dominant: may be brand-voice choice)
  • No preview video (Dominant: may be rational if product is hard to demo)
  • Screenshots are just UI dumps with no messaging/captions (Dominant: lifestyle/brand shots may convert better)
  • Only 1-2 localizations (score relative to actual market, not absolute count)
  • No in-app events or promotional content (Dominant utility apps may not need discovery help)
Flag for all tiers but note context:
  • No developer responses to negative reviews (note volume — responding at 10M+ reviews is a different challenge than at 1K)
  • Generic "What's New" text (acceptable at weekly+ release cadence for Established/Dominant)
如果发现以下问题，请标注。标注为_(层级相关)_的项目需结合应用的品牌成熟度层级评估——对于头部应用而言，这些可能是刻意的选择。
所有层级均需标注：
  • 评分低于4.0
  • 最后更新时间超过3个月
  • Google Play描述无关键词策略（密度低于1%）
  • Google Play缺失首屏横幅图
  • Apple关键词字段可能存在重复词汇（从标题+副标题推断）
  • 品类不匹配——应用在其他品类中面临的竞争更小
  • 截图数量少于5张
仅针对潜力型/腰部应用标注(头部应用不属于失误)
  • 标题仅使用品牌名，浪费字符空间（未包含关键词）(头部应用：品牌本身就是关键词)
  • 副标题/短描述重复标题中的关键词
  • 描述前3行内容通用化_(头部应用：可能是品牌风格选择)_
  • 无预览视频_(头部应用：如果产品难以演示，该选择合理)_
  • 截图仅为UI截图，无信息传递/说明文字_(头部应用：生活方式/品牌图片可能转化率更高)_
  • 仅支持1-2种语言本地化_(根据实际目标市场打分，而非绝对数量)_
  • 无应用内活动或推广内容_(头部工具类应用可能无需曝光支持)_
所有层级均需标注，但需说明背景：
  • 未对负面评论进行开发者回复_(需说明评论数量——处理1000万+评论与1000条评论的难度完全不同)_
  • 通用版本说明_(腰部/头部应用每周或更频繁发布时可接受)_

Task-Specific Questions

任务特定问题

  1. What is the App Store or Google Play URL?
  2. Is this your app or a competitor's?
  3. What category does the app compete in?
  4. Do you have competitor URLs to compare against?
  5. Are you focused on search visibility, conversion rate, or both?
  6. Do you have access to App Store Connect or Google Play Console data?
  1. 应用的App Store或Google Play链接是什么？
  2. 这是你的应用还是竞品的应用？
  3. 应用所属的品类是什么？
  4. 你是否能提供竞品的链接用于对比？
  5. 你更关注搜索曝光度、转化率，还是两者兼顾？
  6. 你是否能访问App Store Connect或Google Play Console的数据？

Related Skills

相关技能

  • page-cro: For optimizing the conversion of web-based landing pages that drive app installs
  • ad-creative: For creating App Store and Google Play ad creatives
  • analytics-tracking: For setting up install attribution and in-app event tracking
  • customer-research: For understanding user needs and language to inform listing copy
  • page-cro: 用于优化引导应用安装的网页落地页转化率
  • ad-creative: 用于制作App Store和Google Play广告素材
  • analytics-tracking: 用于设置安装归因和应用内事件追踪
  • customer-research: 用于了解用户需求和语言习惯，为列表文案提供依据