和朋友争论 Mio 该走疗愈树洞还是恋爱模拟,争到最后发现两条路都不对。市场数据说这个品类的用户和角色平均只处 5 到 7 天,差评第一名是失忆。我觉得毛病出在关系是单方面的。这一篇讲 Mio 的新方向,双向奔赴,附一份完整的产品主线 deck。

Mio 给你 25 个可以连接的角色。Lumi 给你一个完全理解你的存在。它们满足不同的情感需求，但共享同一套记忆管线、情绪引擎和语音链。一个 monorepo 怎么装下两个陪伴产品——以及 agentId?: string 这个模式教会了我什么。

Mio gives you 25 personas to connect with. Lumi gives you one presence that knows you completely. They serve different emotional needs but share the same memory pipeline, emotion engine, and voice chain. Here's how a monorepo houses two companion products — and what the agentId?: string pattern teaches about building parallel products.

内测用户嫌入门流程太麻烦。回头一查，六步 onboarding 把 80–95% 的用户挡在第一条消息之前，根子是「先配置再聊天」这个假设本身就是反的。

A user said 'the onboarding is too much work.' It sounded like a UX complaint. It was actually the catalyst for rethinking the entire product philosophy — from 'configure first, chat later' to 'everything emerges from the relationship.'

Mio 不是聊天机器人 App。它是一个恰好跑在 AI 上的关系模拟器。产品就是关系本身——不是聊天界面，不是模型，不是功能集。这个原则如何重塑了从入门到付费的每一个设计决策。

Mio is not a chatbot app. It's a relationship simulator that happens to run on AI. The product IS the relationship — not the chat interface, not the model, not the feature set. Here's what that means for every design decision from onboarding to monetization.