本页为理解用快照,权威源是飞书 wiki《Sleep Assist 迁移通知方案》;7/27 之后日期均为暂定。This page is a working snapshot; the source of truth is the internal plan wiki. All dates after Jul 27 are tentative.
1概览Overview
Dawnhouse OLD 角标OLD badge
Ergosportive OLD 角标OLD badge
Sleep Assist | Old Version 改名 + OLD 角标renamed + OLD badge
→
Sleep Assist 新 Appnew app
维度Item
说明Summary
范围Scope
Dawnhouse / Sleep Assist / Ergosportive 三个老 App → 新 Sleep AssistThree legacy apps — Dawnhouse, Sleep Assist, Ergosportive — migrate to the new Sleep Assist.
改名范围Rename
仅 Sleep Assist 改名 Sleep Assist | Old Version + 换 icon;另两个不改名,只改 icon(OLD 角标黑白化)Only the legacy Sleep Assist is renamed to Sleep Assist | Old Version with a new icon. Dawnhouse and Ergosportive keep their names; icon change only (OLD badge, grayscale).
触达Touchpoints
升级告知弹窗(每用户最多 2 次,唯一迁移通知)+ Ergo 三阶卡片(上架后 3 个阶段、每阶段 1 次)+ 邮件 4 封 + SSO 迁移成功回执Upgrade notice popup (max 2 impressions per user, the formal migration notice) + three-phase in-app cards after launch (one per phase) + 4 emails + an SSO completion receipt.
💡一句话方案:6 月底老 App 弹一次升级告知(满足法务「显示满 1 个月」)→ 7/27 新 App 上线,老 App 切三阶上线提醒卡片引导下载 → 9 月底老 App 下架关停(暂定,视活跃度定)。Plan in one sentence: at the end of June the legacy apps show an upgrade notice (satisfying the legal one-month visibility requirement) → on Jul 27 the new app launches and the legacy apps switch to three-phase download cards → at the end of September the legacy apps are delisted and later shut down (tentative, based on remaining activity).
2时间线Timeline
上线前(约 4 周)6 月底弹窗可见,法务窗口起算Pre-launch (~4 wks)popup live end of June
Phase 17/27–8/9 认知Awareness
Phase 28/10–9/6 迁移冲刺Active Push
Phase 39/7–9/27 收尾 + 下架Final + delist
Phase 49/28+ 关停(暂定)shutdown (tent.)
日期 / 阶段Date / Phase
事件Event
6/26–6/27
提审:Sleep Assist 改名版本 + 3 个老 App 弹窗版本(留 1–2 天审核缓冲)Store submission: renamed Sleep Assist + popup builds of all three legacy apps (1–2 days of review buffer).
老 App 服务端关停;关停前 ≥2 周发关停通知邮件(邮件 4)。最终时间视活跃用户残留量定Legacy server-side shutdown; shutdown notice email (Email 4) at least two weeks in advance. Final date depends on remaining active users.
⚠️提审 ≠ 用户可见:商店审核需 1–3 天且可能驳回。「用户 6 月底看到弹窗」意味着 6/26–6/27 必须提审——一旦驳回,「满 1 个月」底线就破。Submission ≠ visibility: store review takes 1–3 days and may be rejected. "Visible by end of June" means the Jun 26–27 submission date is firm — a rejection after that breaks the one-month requirement.
3触达方案User Touchpoints
3.1 升级告知弹窗(上线前唯一的迁移通知)Upgrade notice popup (pre-launch, the formal migration notice)
打开老 App 时的全屏通知。标题按宿主 App 实例化:"A new version of {App} is coming",不提「迁移」;正文 = 法务《迁移通知》全文(英文 6/11 定稿,开发直接灌入)。Full-screen notice when a legacy app is opened. Title per host app: "A new version of {App} is coming"; body is the full legal Migration Notice (EN final, Jun 11) injected verbatim by dev.
弹出规则:每人最多 2 次——首次冷启动弹第 1 次;未点「我已知晓」(点 X / 退出不算)1 周后再弹 1 次;点「我已知晓」即合规留痕、永久不弹。逻辑只看确认状态与计数、不看日期,7/27 后没弹过的用户仍会补弹。Frequency: max 2 per user — once on first cold start, once more a week later if not acknowledged (closing doesn't count). Tapping "I understand" is recorded for compliance and stops it permanently. Logic depends only on state and count, so late users still get a catch-up impression after Jul 27.
视觉:与宿主 App 统一样式;长文「头尾固定 + 正文滚动 + 滚到底解锁确认」(已拍板保留,合规留痕强)。Visual: matches the host app's styling; long-text layout with fixed header/footer, scrollable body, confirm button unlocked only after scrolling to the bottom (confirmed decision).
📌设计稿内文字仅为排版示意(6/3 旧口径占位):正文唯一来源是法务定稿 legal/Migration-Notice-EN-20260611.docx,开发以定稿文字灌入,不以图中文字为准。Copy inside the mockups is layout placeholder only (an outdated Jun 3 draft). The sole source for the body text is the legal final Migration-Notice-EN-20260611.docx; dev injects the final text — do not read the copy off these images.
3.2 Ergo 三阶卡片(上线后)Three-phase cards (post-launch)
居中浮层卡片,可点 X 关闭(推广提醒,不承担告知义务);新 Sleep Assist 品牌样式(区别于弹窗的宿主样式)。Centered overlay card, dismissible (promotional reminder — the popup above carries the legal notice duty); styled in new Sleep Assist branding (unlike the host-styled popup).
每阶段首次冷启动弹一次,关闭后该阶段不再弹,切下一 phase 再弹;三个老 App 同步上线、共用同一套文案;CTA 按设备 OS 跳 App Store / Google Play;仅英文。Shown once per phase on first cold start; dismissing ends that phase's impressions. All three legacy apps run the same cards and copy; the CTA deep-links to the App Store / Google Play by device OS; English only.
Phase
阶段Stage
文案(EN)Copy (EN)
CTA
Phase 1
Awareness
A new version of Sleep Assist® is available.
Get the new App
Phase 2
Active Push
We are moving — switch now for a new Sleep Experience.
主题 "A new version of {App} is coming on July 27";首句介绍新名 + 三步预览 + 「上线前一切照旧」安抚Subject "A new version of {App} is coming on July 27"; introduces the new name, previews the 3 steps, reassures nothing changes until launch day.
2 上线Launch
7/27
全量用户(不含 SSO 定向 261 人)All users (excl. the 261 SSO-targeted)
已上线 + 商店按钮 + 三步:下载 → 老账号邮箱登录 → 点 Migrate my accountLive announcement + store buttons + 3 steps: download → sign in with the legacy account email → tap Migrate my account.
3 SSO 定向targeted
7/27
Dawnhouse SSO:FB 10 + Google 181 + Apple 70 ≈ 261 人Dawnhouse SSO users: FB 10 + Google 181 + Apple 70 ≈ 261
人工协助三步:本邮箱注册新 App(Apple 匿名中转邮箱改用常用邮箱)→ 回复本邮件 → 我们关联历史数据并回执。附《账号迁移协议》EN。等待期两 App 均可用,仅暂看不到历史数据Manual-assist 3 steps: register in the new app with this email (Apple private-relay users switch to their everyday email) → reply once registered → we link the history and confirm. Account Migration Agreement (EN) attached. Both apps keep working during the waiting period.
4 关停通知Shutdown
待定(关停日前 ≥2 周)TBD (≥2 wks before shutdown)
届时仍未迁移的用户Users not yet migrated
必发——兑现《迁移通知》「关停时间另行通知」承诺:关停日期 + 数据后果 + 最后一次三步Mandatory — fulfills the Migration Notice promise that the shutdown date will be announced separately: date + data consequences + final reminder of the 3 steps.
回执Receipt
触发式:历史关联完成后Triggered after migration completes
完成人工协助迁移的 SSO 用户SSO users whose migration is done
恭喜迁移完成 + 历史报告入口(Settings → View Previous App Data);床状态按 A/B/C 变体一句带过;回复原线程Congratulations + where to find legacy reports (Settings → View Previous App Data); bed status in one sentence (A/B/C variants); sent as a reply in the original thread.
❓为什么 SSO 要定向:新 App 不支持 Facebook 登录;Dawnhouse 未存 Apple / Google 登录唯一标识,无法自动匹配老账号。261 人一律邮件 + 客服人工协助。Why SSO users get a targeted email: the new app has no Facebook login, and the legacy backend never stored Apple / Google sign-in identifiers, so these accounts cannot be matched automatically. All ~261 users are handled by email + support.
📎协议怎么附:邮件 1 / 2 / 4 不附文件——正文 = 《迁移通知》EN,Footer 仅 ULA 链接(UI 名 Privacy Policy)+ 客服;《账号迁移协议》在 App 内迁移流程中勾选。唯一例外:邮件 3 附《账号迁移协议》EN——SSO 的同意确认 = 附协议 + 回复邮件完成操作。Attachments: Emails 1/2/4 carry none — the body is the Migration Notice (EN), the footer has the ULA link (shown as "Privacy Policy") + support. The Account Migration Agreement is accepted in-app during migration. Sole exception: Email 3 attaches the Agreement (EN) — for SSO users, consent = attached agreement + completing the steps by reply.
统一模板(新 Sleep Assist 品牌,按宿主 App 实例化):宿主品牌条 → 过渡头图(老 icon → 新 icon)→ Hero → 图文三步(核心防错:必须用老账号邮箱)→ 商店按钮 → 《迁移通知》全文 → Footer。版式细节见
email-templates-preview.html(EN)/ 中文对照版。Shared template (new Sleep Assist branding, instantiated per host app): host brand bar → transition hero (old icon → new icon) → hero copy → illustrated 3 steps (key error-prevention: use the legacy account email) → store buttons → full Migration Notice → footer. Full layout: email-templates-preview.html (EN) / Chinese annotated version.
4商店、改名与关停Store Listings, Rename & Sunset
4.1 三 App 商店元数据Store metadata changes
App
名称Name
Icon
Subtitle / DescriptionSubtitle / Description
Sleep Assist(老)(legacy)
Sleep Assist | Old Version
OLD 角标黑白化OLD badge, grayscale
Subtitle:"This version will be replaced soon.";Description 首行加新 App 商店链接(待上线后再放)Subtitle: "This version will be replaced soon." Description first line adds the new-app store link (inserted after launch).
Dawnhouse
不变unchanged
OLD 角标黑白化OLD badge, grayscale
同上处理Same treatment as above.
Ergosportive
不变unchanged
OLD 角标黑白化OLD badge, grayscale
同上处理Same treatment as above.
Sleep Assist(新)(new)
Sleep Assist
全新 iconnew brand icon
Subtitle:"Next-Gen of Sleep Tracking and Assistance."Subtitle: "Next-Gen of Sleep Tracking and Assistance."
Icon 资产已全部交付(见第 1 章图);三老 App 的 Subtitle / Description 文案待 Monica / Marketing 确认(见 7.2)。All icon assets are delivered (see Section 1). Subtitles / descriptions for the three legacy apps await Monica / Marketing sign-off (see 7.2).
4.2 老 App 关停(Phase 4)Legacy app sunset (Phase 4)
时间暂定 9/28(Monica 提案 end of Week 9),最终视老 App 活跃用户残留量决定。Tentatively Sep 28 (per Monica's end-of-Week-9 proposal); final date decided by remaining active users.
关停范围 = 服务端 API;账号 + 床体配对数据保留至少 X 个月(时长待法务定);历史健康数据已迁独立 H5 查询器,不受影响。Scope = legacy server APIs. Account + bed-pairing data retained for a minimum period (duration with legal). Historical health data already lives in the standalone H5 viewer — unaffected.
商店动作(上线日禁新下载、9/27 下架)不影响已安装用户:老 App 可继续使用,直到服务端关停。Store actions (downloads disabled at launch, delisting Sep 27) do not affect installed users — legacy apps keep working until the server shutdown.
5依赖与约束Dependencies & Constraints
新 App 仅支持英文,多语言不在本次范围。The new app launches in English only; localization is out of scope for this program.
健康平台四个首发齐全:Apple Health / Google Fit / Garmin / Samsung Health(均确认赶上 7/27)。Health platforms at launch: Apple Health / Google Fit / Garmin / Samsung Health — all four confirmed for Jul 27.
不能改动项:Bundle ID / Package Name、商店 App ID、已上架用户账号 / 订阅 / 设备绑定——一旦改动即全新 App,老用户数据断链;账号迁移走业务层 PRD 流程,不动商店层。Must not change: bundle IDs / package names, store app records, existing accounts / subscriptions / device bindings — changing them orphans user data. Account migration happens at the product level, not the store level.
ULA:无独立隐私协议,用户协议 + 隐私条款合一为 ULA;UI 文案 / 链接仍叫 Privacy Policy。正式文本待法务交付。ULA: no separate privacy policy — terms + privacy merge into one ULA; the UI label / link still reads Privacy Policy. Final text pending from legal.
6风险与监控Risks & Monitoring
6.1 兜底 / 异常处理Fallbacks
异常情况Scenario
处理方案Handling
用户 6 月底前最后打开老 App,之后再没打开User never opens the legacy app again after June
仅靠邮件触达(预告 / 上线 / 关停通知)Reached by email only (preview / launch / shutdown).
用户拒绝更新到弹窗版本User refuses the update carrying the popup
老 App 不弹窗,靠邮件触达No popup; reached by email.
用户邮箱失效 / 进垃圾箱Email bounces or lands in spam
提供客服联系方式(入口待定)Support contact in every touchpoint (entry point TBD).
SSO 用户没看到定向邮件SSO user misses the targeted email
客服 + 新 App 注册流程内 fallback 提示Support + an in-app hint in the new app's registration flow.
用户 7/27 后才打开老 AppUser first opens the legacy app after Jul 27
升级告知没弹过则补弹 1 次;之后命中 Phase 卡片Popup catches up once if never shown; afterwards Phase cards apply.