AlterU AlterU Part 7 · 工作流时间轴 Part 7 · Workflow Timeline
大纲Outline
Part 7 · 一个 AlterU 游戏的诞生

从立项
到玩家实玩反馈。

1

立项 · 30秒

Elevator pitch + 4 层判断：身份钩在哪？内容怎么 AI-native？社交动词？范式归类？

2

概念 · 1天

3 张 mockup（首屏 / 玩中 / 结束）+ reference video + 范式 + 风格

3

MVP · 3-5天

Fork 范式标杆 → wipe UUID → 跑通 golden path · 不做美术/音效/社交

4

Feel · 5-7天

撞击 4 件套 + 音效 4 件套 + 视觉 polish · 决定"留存"的关键阶段

5

社交化 · 2-3天

身份钩 ④ 落地：leaderboard + notify + cross-user wall · day-one 烤进设计，不要补

6

上线 · 半天

UUID 唯一性 + meta.json + 海报 + push + 部署验证

7

观察 · 持续

用户实玩反馈 → 同类反馈 ≥ 2 次 = 设计层 bug，不是 polish

⚠️ 不要

跳第 5 步 → 社交化补的成本是 5× · useGameSave 数据结构要改一遍 · 已栽过太多次

Part 7 · One AlterU game, beginning to end

From pitch
to first player feedback.

1

Pitch · 30s

Elevator + the 4-layer check: where's the identity hook? how's content AI-native? what's the social verb? which paradigm?

2

Concept · 1 day

3 mockups (open / play / end) + reference video + paradigm + style choice

3

MVP · 3-5 days

Fork the reference game → wipe UUID → get the golden path running. No art, no SFX, no social yet.

4

Feel · 5-7 days

Impact quartet + sound quartet + visual polish — the retention-defining phase.

5

Social · 2-3 days

Identity hook ④: leaderboard + notify + cross-user wall · bake in day one, do not retrofit

6

Ship · half day

UUID uniqueness + meta.json + poster + push + deploy verification

7

Watch · ongoing

Live player feedback → if the same complaint shows up ≥ 2x, it's a design bug not a polish issue

⚠️ Don't

Skip phase 5 → retrofitting social costs 5× · useGameSave schema has to be re-cut · we've shipped this mistake too many times

备忘 · 按 S 关闭Notes · S to close

讲这一张时，让设计师感受到立项的 30 秒比 PRD 50 页有用。 Elevator pitch 不通过 4 层判断（身份钩 + AI-native + 社交动词 + 范式归类），不要进 MVP。

Hammer the 30-second elevator. If the pitch can't clear the 4-layer check (identity hook + AI-native + social verb + paradigm), don't enter MVP.

38 / 41