返回提示词目录第 1415 页

跨平台功能同步发布计划

协调后端、移动端和网页端的发布顺序,形成含审核缓冲、功能开关与回滚安排的时间表。

完整提示词

<context>
Launching one feature on all platforms at once is mostly a sequencing problem. The backend API has to land first and stay backward compatible, because old app versions live for months. Mobile builds must be submitted days before launch to allow for store review and a phased rollout, so the code has to ship dark behind a remote flag and be switched on together on launch day; a mobile build cannot be "hotfixed" in an hour. Web can usually go last. Teams that miss this either launch on web weeks before mobile, block the launch on a rejected app review, or break old clients with an API change. Store review times vary and are not guaranteed; plan buffer and avoid depending on expedited review.
</context>

<task>
Feature: {{feature}}
{{#release_setup}}Release setup: {{release_setup}}{{/release_setup}}

1. Sequence: backend contract agreed first (schema or API spec shared so clients can build against mocks), backend deployed dark, mobile builds containing the feature behind a remote flag, web behind the same flag, then one coordinated switch-on. Explain the critical path.
2. Timeline: work back from the launch date with the mobile code cutoff for the right release train, submission date with buffer for review and possible rejection, phased rollout to enough users before launch, backend and web deploy dates, a full end-to-end test on production builds, and the go or no-go meeting.
3. API and compatibility: additive changes only, behaviour for old app versions that do not know the feature, and when a deprecated field can be removed.
4. Flags and launch switch: one flag or a set per platform, targeting (internal staff, beta, percentage), who flips it, and a kill switch per platform.
5. Old app versions: what users on versions without the feature see, whether a minimum version or update prompt is needed, and the effect on support.
6. Launch day and rollback: order of switch-on, metrics and crash dashboards per platform, who watches, rollback by flag (not by redeploying apps), and communication.
7. Open questions that could block the date.
</task>

<constraints>
- Do not state store review durations as guaranteed; treat them as variable and plan buffer.
- Do not suggest breaking API changes that old app versions would hit.
- Do not invent dates or tools; use placeholders where the input lacks them.
{{> output/uncertainty}}
</constraints>

<output_format>
## Sequence
## Timeline
Table: Date or days before launch | Platform | Milestone | Owner.
## API and compatibility
## Flags and launch switch
## Old app versions
## Launch day and rollback
## Open questions
</output_format>

可替换内容

  • {{feature}}
  • {{#release_setup}}
  • {{release_setup}}
  • {{/release_setup}}
  • {{> output/uncertainty}}

分类与标签

编程开发、跨端发布、应用商店审核、功能开关、接口兼容、上线回滚

前往 AI 图片创作