一个代码库藏着两个产品
Mio 给你 25 个可以连接的角色。Lumi 给你一个完全理解你的存在。它们满足不同的情感需求,但共享同一套记忆管线、情绪引擎和语音链。一个 monorepo 怎么装下两个陪伴产品——以及 agentId?: string 这个模式教会了我什么。
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.
用户说'入门流程太麻烦了'。听起来像个 UX 问题。实际上它引爆了整个产品哲学的重构——从'先配置再聊天'到'一切从关系中涌现'。
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.
© Xingfan Xia 2024 - 2026 · CC BY-NC 4.0