replica-launch

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

replica-launch

Reads

replica/fixes.md

(the angle and the evidence),

replica/brand.md

, and

replica/brand.json

. Writes

replica/launch/

landing.md

pricing.md

listing.json

launch-plan.md

bash

python3 listing.py replica/launch/listing.json      # limits, claims, the original's name

Start from

listing.example.json

in this folder.

读取

replica/fixes.md

（定位角度和证据）、

replica/brand.md

和

replica/brand.json

。写入

replica/launch/

：

landing.md

、

pricing.md

、

listing.json

、

launch-plan.md

。

bash

python3 listing.py replica/launch/listing.json      # limits, claims, the original's name

从本目录中的

listing.example.json

开始。

The rules

规则

No fake proof. No invented testimonials, user counts, star ratings, press logos or "trusted by" rows. An empty proof section is better than a fake one. Real beta users, with permission, are fine.
No reviewer quotes as testimonials. The original's reviews are research.
The original's name stays out of your app name, store listing, keywords and ads. Apple and Google reject it, and it invites a takedown.

不得伪造背书。 不得编造用户证言、用户数量、星级评分、媒体 Logo 或“trusted by”展示栏。宁可让背书板块留空，也不要造假。获得许可的真实 Beta 用户可以使用。
不得将评论者的原话作为用户证言。 原应用的评论仅用于研究。
原应用的名称不得出现在你的应用名称、商店信息、关键词和广告中。Apple 和 Google 会拒绝此类内容，这也可能招致下架。

Step 1: landing page

第 1 步：落地页

landing.md

, section by section, then build it in the project:

Hero: the angle as a headline (what you do, for whom), one line under it, one button. Screenshot of the real product.
The problem: the top two "hate" themes, in plain words. Paraphrase, do not quote reviewers.
How it works: three steps, from the core flow.
Features: each tied to a fix from
```
fixes.md
```
. Lead with the fixes, not the parity features. Parity is the price of entry.
Pricing: the table from step 2.
FAQ: the real objections, including "can I import from {{category}} tools?" if you built an importer.
Final call to action.

Copy in the brand voice. Run replica-design's contrast check on the page.

先按章节编写

landing.md

，然后在项目中构建落地页：

首屏（Hero）：将定位角度写成标题（你做什么，面向谁），标题下放一行说明和一个按钮，并使用真实产品的截图。
问题：用直白语言说明用户最讨厌的两类问题。必须改写，不得直接引用评论者的话。
工作原理：根据核心流程列出三个步骤。
功能：每项功能都应对应
```
fixes.md
```
中的一项修复。优先突出修复项，而不是功能对等项。功能对等只是入场门槛。
定价：使用第 2 步中的价格表。
常见问题（FAQ）：回答用户真正关心的问题；如果实现了导入工具，还应包含“我可以从 {{category}} 工具导入数据吗？”这一问题。
最终行动号召（CTA）。

文案应符合品牌语气。对页面运行 replica-design 的对比度检查。

Step 2: pricing

第 2 步：定价

pricing.md

The original's public pricing page and 2 or 3 alternatives, in one table, with the URL and the date read. Prices change, so the date matters.
What reviewers said about price and billing, from
```
feedback.md
```
, with counts.
The model: free plan or trial, per seat or flat, monthly and annual (annual usually 2 months free).
Three tiers at most. Name them by who they are for.
Fix the billing complaints in the product: one-click cancel, clear renewal emails, no surprise per-seat jumps.
The Stripe products and prices to create (the user creates them).

pricing.md

：

将原应用的公开定价页面和另外 2 或 3 个替代方案整理到同一张表中，并记录 URL 和查询日期。价格会变化，因此日期很重要。
汇总
```
feedback.md
```
中评论者对价格和计费的看法，并附上数量。
定价模式：免费方案或试用、按席位计费或统一定价、按月和按年付费（年度方案通常相当于免费两个月）。
最多设置三个档位，并按照目标用户命名。
在产品中解决计费相关抱怨：支持一键取消、发送清晰的续订提醒，避免用户意外发现按席位费用上涨。
列出需要创建的 Stripe 产品和价格（由用户创建）。

Step 3: store listing

第 3 步：商店信息

Fill

listing.json

, then:

bash

python3 listing.py replica/launch/listing.json

It checks App Store limits (name 30, subtitle 30, promotional text 170, keywords 100, description 4000) and Google Play's (title 30, short description 80, full 4000), counts characters the way a person does, flags ranking and price claims in short fields, emoji, wasted keyword characters, and any name from
avoid
anywhere in the listing. Exit 1 on an error.

Apple's App Review Guideline 4.1 (Copycats) rejects apps that simply copy a popular app or make minor changes to another app's name or UI. Your fixes and your own brand are what get you through review, so make them visible in the screenshots and the first lines of the description.

Also prepare: screenshots at the current required sizes (check App Store Connect and Play Console when you upload, they change), privacy labels and the data safety form, privacy policy and support URLs, age rating, and review notes with a demo account the reviewer can use.

填写

listing.json

，然后运行：

bash

python3 listing.py replica/launch/listing.json

该脚本会检查 App Store 的限制（名称 30 个字符、副标题 30 个字符、推广文本 170 个字符、关键词 100 个字符、描述 4000 个字符）以及 Google Play 的限制（标题 30 个字符、短描述 80 个字符、完整描述 4000 个字符）。它会按照人的阅读方式统计字符数，标记短字段中的排名和价格声明、 emoji、无效关键词字符，并检测商店信息任意位置是否出现

avoid

中的名称。发生错误时退出码为 1。

Apple 的 App Review Guideline 4.1（Copycats）会拒绝简单复制热门应用，或对其他应用的名称或 UI 做出细微改动的应用。你的修复内容和自有品牌才是帮助应用通过审核的关键，因此应在截图和描述的前几行中突出展示。

还需准备：符合当前尺寸要求的截图（上传时请检查 App Store Connect 和 Play Console，因为要求可能变化）、隐私标签和数据安全表单、隐私政策及支持 URL、年龄分级，以及包含审核员可使用演示账号的审核备注。

Step 4: launch plan

第 4 步：发布计划

launch-plan.md

: a waitlist or beta list before launch, analytics and error tracking live, where the original's unhappy users talk (the Reddit threads and communities from the research), a Product Hunt or Hacker News post that leads with the fix, and the first 10 users to talk to by hand.

launch-plan.md

：发布前建立候补名单或 Beta 名单；上线分析工具和错误追踪；找出原应用不满用户讨论的渠道（研究中找到的 Reddit 帖子和社区）；撰写以修复内容为亮点的 Product Hunt 或 Hacker News 帖子；以及手动联系前 10 位用户进行沟通。

Output

输出

replica/launch/

complete, the landing page built,

listing.py

passing. Next:

/replica-deploy

完成

replica/launch/

目录，构建落地页，并确保

listing.py

检查通过。下一步：

/replica-deploy

。