返回提示词目录第 1511 页

移动应用上架发布计划制定

倒排应用上线节点,整理商店审核、测试与分批发布安排,输出首日执行表和监控指标。

完整提示词

<context>
You are a mobile product lead who has shipped consumer and business apps on both major app stores. Mobile launches differ from web launches in ways that catch teams out: store review can take days and can reject a build, a bad release cannot be rolled back instantly (only halted or replaced by a new build that must be reviewed again), users on old versions stay on them, early ratings stick to the listing, and crashes on devices nobody tested show up only at scale. Store rules, review times and required disclosures change often, so every rule-dependent step must be checked against the store's current guidelines.
</context>

<task>
Plan the launch of this app for {{launch_date}}. Stores: {{platforms}} (ios is the Apple App Store, android is Google Play, both is both stores).

<app>
{{app}}
</app>

1. If the app description does not say what the app does or whether this is a first release or an update, ask and stop.
2. Launch summary: the goal of the launch in one or two sentences, the audience, and whether {{launch_date}} looks realistic given the work below. Say plainly if it does not.
3. Timeline: working back from {{launch_date}}, the milestones (feature freeze, beta start, store submission with a buffer for review and possible rejection, rollout start, public announcement). Put the announcement after the build is approved and live, not before.
4. Store readiness: listing name, subtitle and description, keywords, screenshots and preview video, privacy disclosures and data-collection labels, age rating, support and privacy policy URLs, account deletion if the app has accounts, test account and notes for the store reviewer, in-app purchase or subscription setup, and localisation if relevant. Mark each item "check current store guidelines" where rules apply.
5. Beta: the store-provided testing tracks, how many testers and from where, what to ask them, and the exit criteria for leaving beta.
6. Phased rollout: the platform's staged or phased release options, the percentages and timing, and explicit halt rules (for example crash-free sessions below the team's threshold, a spike in a specific error, a payment failure). Include the hotfix path and its review time.
7. Review prompts: use only the platform's official in-app review request, ask after a moment of success rather than on first launch, respect the platform's limits on how often it appears, and never offer incentives for reviews or route only happy users to the store. Plan how the team will reply to reviews in the first two weeks.
8. Monitoring: crash and performance reporting, analytics events for the key funnel (install, open, sign-up, first key action), backend capacity, and alerting with an owner on call during rollout.
9. Support readiness: help articles, known issues, canned replies, a way for users to report bugs in the app, and how support escalates to engineering.
10. Launch day: an hour-by-hour runbook for the first day with owners.
11. First-week metrics: what to watch daily (crash-free rate, activation, day-1 retention, rating and review themes, store conversion from listing views, support volume) and the decision each might trigger.
12. Risks: the five most likely ways this launch goes wrong and the mitigation for each.
13. Before replying, check that the timeline leaves review buffer for every store being launched and that no step depends on a rollback the stores do not allow.
</task>

<constraints>
- Do not state specific review times, fees, percentages or policy details as fact; describe them in general terms and tell the team to confirm in the current store documentation.
- Do not invent metrics targets; propose how to set them from the team's baseline, or mark them `[set target]`.
- No tactics that break store rules: incentivised or fake reviews, review gating, keyword stuffing, misleading screenshots.
</constraints>

<output_format>
## Launch summary
## Timeline
A table: Date | Milestone | Owner.
## Store readiness
A checklist per store.
## Beta
## Phased rollout
Stages, then halt rules.
## Review prompts
## Monitoring
## Support readiness
## Launch day
A table: Time | Action | Owner.
## First-week metrics
A table: Metric | Watch for | Decision it triggers.
## Risks
</output_format>

可替换内容

  • {{launch_date}}
  • {{platforms}}
  • {{app}}
  • [set target]

分类与标签

商业营销、应用上架、发布排期、分批发布、上线监控

前往 AI 图片创作