妙鸭相机


1. 介绍

1.1 平台概况与定位

妙鸭相机是 2023 年 AI 写真赛道的第一波现象级产品:用户上传一批本人照片,付费制作一个"数字分身",再从这个分身批量生成不同风格的写真成片。它的运营主体为未序网络科技(上海)有限公司,由阿里大文娱参投的创业团队孵化,后并入阿里大文娱全资控股的"神力视界";技术底座为阿里大文娱自研的"提香"模型,该模型通过多角度照片分析生成 3D 人脸模型并支持动态表情模拟。

在 AI Harness 六层能力模型中,妙鸭是一个极端的单点样本:它在 L1(把"人"本身变成上下文)上做了当时最激进的尝试,在 L4(数字分身作为持久化身份资产)上做出了本组第一个面向大众的"身份资产产品",却在 L2、L3、L5 三层几乎空白,L6 在早期还发生了公开的信任事故。它最终没能活下来——团队于 2025 年 9 月底正式解散,产品仅维持最低限度运营,不再进行功能升级与推广

这个结局使妙鸭成为本组研究中唯一具备完整生命周期的负面样本。它的价值不在于"它做错了什么",而在于它证明了一个命题:在生成质量已经足够好的前提下,决定产品生死的不是模型,而是承载模型的 Harness

1.2 发展沿革与生命周期

时间事件说明
2023-07-17妙鸭相机正式上线以微信小程序、支付宝小程序为主入口
2023-08登顶 App Store 总榜日活突破 60 万,高峰期 4,000 余人排队出片
2023-09推出免费版允许上传 8 张照片体验,降低首次使用门槛
2023 年内用户协议争议因用户协议条款引发争议,官方道歉并修订协议
2025-09版本更新新增 AI 修图与穿搭方案定制服务
2025-09 底团队正式解散产品仅维持最低限度运营,不再升级与推广

需要特别说明的是:团队解散这一事实的权威信源仅有第三方工具站表述,尚未定位到科技媒体报道或工商/司法信息佐证,标注 ;当前 App 版本号也存在两个冲突口径(v4.6.14 更新于 2026-08-18、v4.3.1 更新于 2026-04-08),标注 [待填写]。本节后续所有基于"解散"这一事实的分析,均以该事实成立为前提,若后续复核推翻该事实,相关归因结论需重新评估。

1.3 定价与开放形态

内容
开放形态微信小程序 / 支付宝小程序(主入口)+ iOS / Android App + 官网 miaoya.cn(品牌展示)
数字分身制作推广价 ¥9.9(标准价 ¥29.9),含 10 张写真生成 + 5 次高清下载
后续单张精修 / 高清下载约 2 钻石/次(约 ¥2)
免费版2023-09 起推出,上传 8 张照片(数量低于付费版的 ≥20 张要求)
模型底座阿里大文娱自研"提香"模型,闭源、不对外提供 API

上述定价为 2023 年时点数据,来自多个第三方来源的一致表述,但均非官方原始页面存档,标注 。妙鸭的定价结构本身已经暴露了它的商业模式问题:一次性 ¥9.9 买断一个分身 + 10 张成片,是典型的"引流品定价",缺乏后续消耗场景与订阅锚点,这与同为身份类产品的可灵"主体创建"(按会员档位限制 30 / 50 / 150 / 500 个主体)形成鲜明对比。


2. 名词解释

2.1 方向通用术语

术语英文 / 缩写释义
虚拟试穿VTON(Virtual Try-On)将目标服装"穿"到指定人物图像上并生成视觉可信结果;与妙鸭 2025-09 新增的"穿搭方案定制"同属"以固定身份为底座做外观变换"的问题族
服装形变Garment Warping先用 TPS(薄板样条)等几何变换把平铺服装对齐到人体姿态,再送入生成;代表方法 GP-VTON
服装掩码Cloth Mask由人体解析(Human Parsing)得到的上衣 / 下装 / 外套区域二值图,用于限定重绘范围
试穿扩散Try-on Diffusion以扩散模型端到端完成服装与人体融合,抛弃显式形变步骤;代表方法 OOTDiffusion 的 Outfitting Fusion
换脸Face Swap把 A 的脸替换到 B 的面部位置;事后换脸(Post-hoc Swap)指生成完成后再替换,代表实现 ReActor
人脸重演Face Reenactment保留身份、迁移表情 / 口型 / 头部姿态;妙鸭的"动态写真"属于该能力的产品化形态
身份保持Identity Preservation生成结果在多大程度上仍"是那个人";是换装、换脸、数字分身三类产品的共同核心指标
图像提示适配IP-Adapter用图像编码器(CLIP)特征注入注意力,实现"以图为提示词"
零样本身份定制InstantID单张参考图、无需微调即可迁移身份;由 ID Embedding + 轻量适配模块(解耦交叉注意力)+ IdentityNet 三组件构成
纯度闪电身份定制PuLID(Pure and Lightning ID Customization)字节跳动提出的对比学习 + Lightning 蒸馏方案,用于缓解 InstantID"脸过硬、提示词跟随弱"的问题
可控生成ControlNet以 Canny 边缘、Depth 深度、Pose 姿态、Mask 等视觉信号作为额外条件控制生成结构的插件式网络
局部重绘Inpainting对图像指定区域(需遮罩 / 涂抹)重新生成,区域外保持不变
低秩适配LoRA小参数量微调模块,用于固化特定人物 / 风格 / 服装资产
深度伪造Deepfake用深度合成伪造人脸 / 声音,是肖像权与诈骗风险的核心来源
可识别性Identifiability司法判定肖像权侵权的核心标准:不要求完全一致,公众能认出即成立

2.2 妙鸭相机特有术语

术语英文 / 缩写释义
数字分身Digital Avatar / Digital Twin用户上传 ≥20 张多角度、多表情、多光线半身照后,由模型构建的专属人脸 / 形象模型;一次性训练、多次复用的身份资产
提香模型Tixiang Model阿里大文娱自研的人像生成模型,妙鸭的技术底座,通过多角度照片分析生成 3D 人脸模型
更像我一点Similarity Tuning妙鸭的相似度微调功能,用于提升生成图与本人的相似度;是产品内唯一的"评估与修正"入口
排队出片Queue-based Rendering因算力受限,分身制作与成片生成需排队,从数小时到十几小时不等(高峰期)
风格模板库Style Template Library30+ 种场景化模板(日系清纯、职场正装、苗寨少女、古风、证件照、旅行大片等);App 内另有"11 种 AI 制图风格"的口径
钻石Diamonds妙鸭的站内虚拟货币单位,用于单张精修与高清下载(约 2 钻石/次)
穿搭方案定制Outfit Customization2025-09 版本新增能力,是妙鸭向换装(VTON)方向的一次延伸

3. 功能说明

3.1 核心功能链路

妙鸭的功能链路极短,只有三步:

  1. 上传与训练:用户上传 ≥20 张本人多角度、多表情、多光线的半身照,系统构建数字分身(需排队,高峰期从数小时到十几小时);
  2. 模板套用:从 30+ 种风格模板中选择,由分身驱动生成对应风格的写真成片;
  3. 精修与下载:对选中成片做精修、高清下载(消耗钻石),或进行 AI 修图(2025-09 版本新增)。

这条链路的工程特征是:每次交互都是一个原子操作。用户上传 → 等待 → 选模板 → 出片,四步之间没有中间状态可供干预,没有参数可供调节,也没有批处理入口。成片质量不满意时,用户唯一能做的是"再选一次模板"或"用更像我一点微调"——无法像可灵 O1 那样用自然语言在同一会话内迭代修正,也无法像 ComfyUI 那样回溯到某个节点重跑。

3.2 模板与风格体系

维度妙鸭的实现工程评价
风格来源平台预置的 30+ 种模板(App 内另称 11 种 AI 制图风格)平台侧强控,用户不可自定义
身份来源用户自有数字分身(≥20 张照片训练)用户侧投入高,沉没成本大
组合方式分身 × 模板 = 成片,一一对应无交叉组合、无参数空间
扩展方式穿搭方案定制(2025-09 新增)延伸方向正确,但落地时点已晚

模板体系的设计暴露了一个关键取舍:妙鸭把"可控性"全部放在了平台侧,把"投入"全部放在了用户侧。用户付出了 20 张照片与数小时排队,换来的却是对生成过程零控制权。这种不对称在产品早期会被"新鲜感"掩盖,但在新鲜感消退后必然转化为留存问题。

3.3 B 端与开放能力

妙鸭曾尝试向 B 端延伸:通过开放 API 与携程等平台合作推出"AI 旅拍"等企业级服务。该信息的置信度较低,标注 ——未检索到官方公告、合作通稿或携程侧的产品页面佐证。

从 Harness 视角看,即便该合作属实,妙鸭也不具备支撑 B 端工程集成的基础设施:无公开的 API 文档、无并发与配额契约、无回调机制、无错误码规范。相比之下,同期面向企业的图像平台(如 Leonardo.ai)已经把速率限制、并发上限、队列深度三类容量约束显式文档化,并提供 Webhook 与幂等指引。这一对比正是"有无 Harness"的分水岭。


4. 平台架构

图 4-1|妙鸭相机训练式身份管线:从照片到写真成片

妙鸭相机训练式身份管线:从照片到写真成片 信息截止 2026-09 · 示意:基于本文分析绘制 上传 ≥20 张多角度照片 本人半身照 · 多表情多光线 人脸检测与对齐 多角度照片预处理 提香模型 per-user 训练 训练式身份注入路线 数字分身 人脸/形象模型 · 持久身份资产 分身驱动生成 风格模板 提示词 + 构图 + 光影 合成 分身 × 模板一一对应 写真成片 30+ 场景模板可选 精修 / 高清下载 消耗钻石 · 约 2 钻石/次 分发形态(4.2) 微信小程序 / 支付宝 主入口 · 低获客成本 iOS / Android App 多端账号互通 · 云端存储 官网 miaoya.cn 仅品牌展示 · 无开放 API 对照路线:零样本身份注入(InstantID / PuLID)——单张照片 · 秒级出图 · 权重可跨管线迁移 结构解读:训练式路线把身份资产做成产品内私有状态,成本与等待高企,L4 锁死是失效根因。

数据来源:基于本文分析绘制的示意图。

4.1 训练式身份管线

妙鸭采用训练式(Per-user Fine-tune)而非零样本适配的技术路线:

≥20 张多角度照片 → 人脸检测与对齐 → 提香模型 per-user 训练 → 数字分身(人脸 / 形象模型)
                                                                    ↓
                                        风格模板(提示词 + 构图 + 光影)→ 合成 → 成片 → 精修 / 高清下载

这是与 InstantID、PuLID 等"零样本身份注入"路线的根本差异,也是其成本与等待时间居高不下的根因:

维度训练式(妙鸭)零样本注入(InstantID / PuLID)
样本要求≥20 张多角度、多表情、多光线照片单张参考图即可
首次可用时延数小时至十几小时(排队)秒级至分钟级
算力成本每用户一次完整训练单次前向推理
身份保真上限高(见过多角度)中—高(依赖单图泛化)
迭代成本极高(重新上传、重新训练)极低(换参考图即可)
可迁移性锁定在单一产品内权重 / 适配器可被任意管线加载

训练式路线在 2023 年是合理选择——当时零样本方案尚不成熟;但妙鸭没有在 2024—2025 年零样本方案成熟后完成路线迁移,反而把成本结构固化了下来。这是技术债转化为商业失败的典型案例。

4.2 分发形态

  • 主入口为小程序(微信 / 支付宝),App 为辅,官网仅做品牌展示。小程序优先的策略在 2023 年带来了极低的获客成本与极快的传播速度,但代价是能力受宿主环境约束(文件导出、后台任务、算力调度均受限)。
  • 多端账号互通(iOS / Android / 微信 / 支付宝),云端存储分身与成片。
  • 无对外开放 API(B 端合作若有,亦为个案定制,非平台化能力)。

4.3 与零样本身份注入路线的对比

从 Harness 角度,两条路线的差异可以归结为一句话:训练式路线把身份资产做成了"产品内的私有状态",零样本路线把身份资产做成了"可跨管线流通的上下文"。前者在 L4 上看似更强(专属模型),实则更弱——因为它不可迁移、不可组合、不可审计;后者看似更轻,却因为"身份适配器可被任意加载"而获得了真正的资产流动性。


5. Harness 设计

5.1 六层能力总览

妙鸭的实现成熟度证据强度
L1 上下文工程把"人"本身变成上下文:20 张照片 → 数字分身 → 模板提示词
L2 工具与执行模板套用为主,工具化能力极弱(裁剪 / 调色 / 瑕疵修复 / AI 修图)
L3 编排与控制几乎无编排:单次"选模板 → 生成"的原子操作
L4 记忆与状态数字分身是唯一持久化资产,但锁定在单一产品内、不可迁移
L5 评估与观测仅"更像我一点"的人工主观微调,无量化评估
L6 治理与安全曾因用户协议条款引发争议,后道歉修订;无标识机制公开说明中(早期为负)

5.2 L1 上下文工程层

妙鸭在 L1 上做了一个当时极具想象力的设计:把"人"本身压缩为上下文。传统文生图的上下文是提示词,妙鸭的上下文是"一个训练好的人"。从工程上看,这是把高维身份信息(骨相、五官比例、肤色、表情习惯)从"每次生成都要重新描述"变为"一次性注入、长期复用"。

这个设计的问题在于它是一次性的、不可编辑的:

  • 用户无法调整"哪些特征被记住、哪些被忽略"(对比可灵 Identity Map 把"稳定身份标记"与"瞬时属性(表情 / 穿搭 / 光线)"解耦);
  • 用户无法为新场景补充上下文(对比 FLUX.2 支持最多 8—10 张参考图随任务携带);
  • 唯一的调节旋钮是"更像我一点"——一个没有量纲、没有反馈回路的模糊滑块。

换言之,妙鸭的 L1 是"写入一次、只读"的上下文,而第三代 Harness 要求上下文是"可组装、可裁剪、可优先级排序"的。

5.3 L2 工具与执行层

工具集极其单薄:模板选择、裁剪、调色、瑕疵修复、AI 修图(2025-09 新增)。没有外部工具注册机制,没有脚本化入口,没有批量处理,没有任何形式的工具契约。

对 C 端写真产品而言工具少并不致命,致命的是:工具少 + 无编排 = 用户的一切需求都必须由平台预置。当 30+ 种模板被用完,产品就失去了新的价值供给点。

5.4 L3 编排与控制层

这是妙鸭最薄弱的一层,也是其用户体验崩塌的直接原因:

缺失的编排能力具体后果
无任务队列可视化与优先级调度高峰期 4,000 余人排队出片,等待时长不可预期
无批处理无法"一次生成 20 个风格"批量挑选
无中间态干预成片不满意只能重跑,无法定向修正局部
无工作流 / 无 API 编排B 端集成只能个案定制,无法规模化
无失败重试与状态恢复训练中断后用户的沉没成本无法追溯

"排队出片"是这一层失效最直观的产物:它本质上是把算力稀缺性直接转嫁给了用户,而没有通过编排层做削峰、降级、异步化与预期管理。

5.5 L4 记忆与状态层

数字分身是妙鸭唯一的持久化资产,也是其全部价值所在——这句话既是它的产品定位,也是它的死亡判决书。

身份一致性(Identity Preservation)是换装、换脸、数字分身三类产品共同的 L4 核心难题:它的技术本质是把"身份特征"作为跨会话状态持久化。谁把 L4 做扎实,谁才留得住用户——因为用户的投入(照片、时间、审美偏好沉淀)都附着在这一层上,形成迁移成本。

妙鸭的 L4 却是一个单向锁死的资产

  1. 不可迁移:分身只存在于妙鸭产品内,用户无法导出模型、无法在别处复用。这意味着用户在妙鸭的全部投入是一次性沉没成本,而非可携带资产。
  2. 不可组合:分身只能与平台预置模板组合,无法与用户自己的参考图、品牌资产、场景约束组合。
  3. 不可版本化:没有"分身 v1 / v2"的概念,用户无法回到某个更满意的身份版本。
  4. 随产品消亡:团队解散、产品停止运营后,用户的身份资产一并消失。

对比同一赛道中把 L4 做对的做法:可灵把"主体创建(Element)"做成按档位计量(30 / 50 / 150 / 500 个)的可复用主体;Runway 把 Brand Kits(最多 3 个)与 Custom Voice Clones(最多 3 个)做成一等公民资产;FLUX.2 的 Base 变体专为 LoRA 微调设计,使身份与品牌资产以权重形式被用户自己持有;ComfyUI 生态把工作流 JSON 图与 LoRA 权重双双纳入版本控制。共同点是:资产的所有权与可携带性在用户侧。妙鸭恰恰相反——它把用户最强的资产留在了自己的服务器里,却没有给出足以让用户留下的长期价值。

5.6 L5 评估与观测层

妙鸭没有工程意义上的评估层。产品内唯一的评估入口是"更像我一点"——依赖用户主观判断反复试错,没有客观指标、没有回归集、没有 A/B 机制。

对身份类产品而言,这不是小问题:身份保真度是一个可量化的指标(人脸识别嵌入相似度、跨年龄 / 跨风格稳定性),开源生态早已用 SSIM / FID / KID / LPIPS 与人脸识别准确率建立了评测基线(如第三方实测中 PuLID 人脸识别准确率 91%、InstantID 84%、IP-Adapter FaceID 76—82%,该组数据为社区低置信实测,仅作量级参考)。妙鸭既没有公开自己的评测口径,也没有把评测能力交到用户手上,导致用户无法判断"这次生成的分身是否比上次更像我",只能用脚投票。

5.7 L6 治理与安全层

妙鸭在治理层的记录是先负后修正

  • 用户协议争议(2023):产品初期因用户协议条款引发争议——争议焦点在于平台对用户上传照片与生成内容的使用权边界。官方随后道歉并修订协议,承诺照片仅用于本次分身制作、完成后自动删除原始上传照片、支持匿名化处理。该事件的细节来自第三方转述,标注
  • 标识合规空白:未检索到妙鸭关于生成内容标识(显式标识 / 元数据隐式标识 / 数字水印)的任何公开实现说明,标注 [待填写]。

就合规适用性而言,妙鸭的产品形态落在多条监管要求的作用范围内:

  • 《人工智能生成合成内容标识办法》(国信办通字〔2025〕2 号,2025-09-01 施行)第四条:服务提供者提供生成合成内容下载、复制、导出等功能时,应当确保文件中含有满足要求的显式标识;第五条:应当在文件元数据中添加隐式标识(含生成合成内容属性信息、服务提供者名称或编码、内容编号等),并鼓励添加数字水印形式的隐式标识。妙鸭的核心付费点正是"高清下载",直接落入第四条适用范围
  • 《中华人民共和国民法典》第一千零一十八条:肖像是"在一定载体上所反映的特定自然人可以被识别的外部形象";第一千零一十九条:任何组织或者个人不得以丑化、污损,或者利用信息技术手段伪造等方式侵害他人的肖像权,未经肖像权人同意,不得制作、使用、公开肖像权人的肖像。数字分身虽以用户本人肖像训练,但一旦被用于生成与本人不同的场景形象并对外分发,即进入肖像权与授权链的审查范围。
  • 北京互联网法院 2026-03 生效判决确立两项关键规则:可识别性为侵权核心判定标准(AI 换脸形象与原肖像无需完全一致,社会一般公众能够识别即构成使用特定自然人肖像);举证责任转移(被告主张"AI 偶然撞脸"的,须复现创作过程,无法复现则承担举证不能的不利后果)。该判决还明确"技术中立"不是免责事由。
  • 行业警示:2026-04-28,同为本组研究对象的即梦 AI 因未有效落实人工智能生成合成内容标识规定要求被网信部门依法查处。这说明监管落点在导出与分发环节,而非模型能力本身。

妙鸭的教训在于:治理不是合规部门的文档工作,而是 L6 的工程实现——授权链、标识嵌入、审计留痕、可复现的创作记录,缺一不可。用户协议争议只是 L6 缺失最先被看见的那一面。

5.8 成熟度判断与失效归因

结论:妙鸭是"强模型、弱 Harness"的典型。 它的生成能力在 2023 年属于第一梯队(不然不会登顶 App Store 总榜),但 Harness 六层中有四层(L2 / L3 / L4 / L5)处于空白或失效状态,L6 在关键时点还是负资产。

失效层失效表现直接后果传导到商业的后果
L2 工具工具集仅模板与基础修图用户无二次创作空间成片即终点,无追加消费
L3 编排无批处理、无队列调度、无中间态排队数小时、成片不可控体验崩塌、口碑损耗
L4 状态分身锁死、不可迁移、不可版本化用户投入无法沉淀为可携带资产一次性买卖,无留存锚点
L5 评估无量化身份保真评估质量不可回归、不可证明用户无法建立信任
L6 治理协议争议 + 标识机制空白信任事故 + 合规敞口品牌受损、监管风险

这五层并非独立失效,而是相互放大:L4 锁死使用户无法沉淀资产 → L2/L3 缺失使用户无法创造新价值 → 用户离开 → L5 缺失使平台无法察觉质量下滑 → L6 事故加速信任流失。模型再强,也补不上 Harness 的结构性缺口。


6. 实际案例

6.1 2023 年爆发时点的规模数据

可获得的规模数据均为 2023 年时点值,须如此标注,不可作为当前状态引用:

  • 2023-08 登顶 App Store 总榜;
  • 日活突破 60 万
  • 高峰期 4,000 余人排队出片。

这组数据的意义在于刻画"AI 写真赛道第一波爆发"的行业背景:它证明了 C 端对"AI 生成本人形象"存在真实且强烈的需求。需求是真的,产品却没留住——这恰恰说明需求侧不是瓶颈,供给侧的工程能力(Harness)才是

6.2 携程「AI 旅拍」

据第三方来源,妙鸭曾开放 API 与携程合作推出"AI 旅拍"企业级服务。该信息置信度低,未检索到官方公告或携程侧产品页佐证,标注

即便属实,从 Harness 角度看该合作也难以规模化:妙鸭没有公开的 API 契约、并发配额、回调机制与错误码规范,B 端集成只能靠个案定制,边际成本不随客户数下降。这与"平台化 B 端能力"有本质区别。

6.3 用户协议争议事件

2023 年,妙鸭因用户协议条款引发争议——争议核心是平台对用户上传照片与生成内容的使用权边界。官方随后道歉并修订协议,并作出三项承诺:照片仅用于本次分身制作、制作完成后自动删除原始上传照片、支持匿名化处理。

这一事件是本组文档中最早的"身份资产治理事故"记录,其工程含义是:当产品把用户的生物特征(人脸)作为核心输入时,授权链与数据生命周期必须是 L6 的一等公民,而不能藏在一份冗长的协议文本里。后续同类产品(如即梦在 2026-02 起限制真人素材使用并引入数字人分身认证)正是对这一教训的产品化回应。

6.4 生命周期复盘

妙鸭证明了"单点爆款 + 无工作流深度 + 无资产可迁移性"的 AI 写真产品难以留存。它的生命周期可以概括为四段:

  1. 需求验证期(2023-07 至 2023-08):极低的获客成本 + 极强的新鲜感 → 爆发式增长;
  2. 体验透支期(2023-08 至 2023-12):排队、成片不可控、协议争议 → 口碑回落;
  3. 能力停滞期(2024 全年):竞品快速补齐零样本身份注入与编辑能力,妙鸭未见架构级升级;
  4. 退出期(2025):2025-09 版本新增 AI 修图与穿搭方案定制后,团队于 2025-09 底解散,产品维持最低限度运营。

其中第 3 段最值得警惕:妙鸭不是被某个竞品打败的,而是被"技术范式迁移"抛下的。当零样本身份注入(InstantID / PuLID)把"20 张照片 + 数小时排队"压缩为"1 张照片 + 秒级出图"时,妙鸭的成本结构瞬间从"可接受的代价"变成"不可理喻的负担"。而它没有能力完成这次迁移,因为它的整个产品架构(乃至商业模式)都建立在"训练式分身"这一技术前提上。


7. 总结

7.1 优势

  1. 首个把"身份"做成大众产品的尝试:在 2023 年就让普通用户体验到"一次投入、多次复用"的身份资产形态,具有开创性。
  2. 生成质量在同期属第一梯队:能够登顶 App Store 总榜并形成社交裂变,说明成片质量通过了大众审美检验。
  3. 极低的获客成本:小程序优先 + 社交分享,是 C 端 AI 产品低成本获客的经典范式。
  4. 验证了真实需求:日活 60 万证明"AI 生成本人形象"是真实需求而非伪需求。

7.2 局限与失效根因

  1. 技术路线被范式迁移抛下:训练式分身在零样本身份注入成熟后彻底失去成本优势,且架构无法平滑迁移。
  2. L4 资产单向锁死:身份资产不可迁移、不可组合、不可版本化,用户投入沦为沉没成本。
  3. L3 编排缺失导致体验崩塌:排队数小时、无批处理、无中间态干预。
  4. L5 评估空白:无身份保真量化口径,质量不可回归、不可证明。
  5. L6 治理早期为负:用户协议争议 + 标识机制空白。
  6. 商业模式无纵深:¥9.9 一次买断,缺乏订阅锚点与后续消耗场景。

7.3 适用边界

场景是否适用说明
作为当前生产可用的写真 / 换装方案不适用团队已解散,产品仅维持最低限度运营,不再升级
作为"身份资产产品"的历史样本研究适用完整生命周期 + 完整失败链条,研究价值极高
作为 Harness 负面案例的教学材料高度适用五层失效的传导路径清晰可追溯
作为商业模式参考谨慎需求侧成立,供给侧定价与留存结构失败

7.4 对后来者的工程启示

  1. 身份资产必须可携带:把身份做成用户可导出、可迁移、可版本化的资产,而不是平台的私有状态。
  2. 技术路线要能跨范式迁移:把"训练式"作为可替换的实现细节,而非产品架构的前提。
  3. L3 编排是体验的底线:排队、批处理、中间态干预不是优化项,而是可用性项。
  4. L5 必须量化身份保真:没有指标就没有回归,没有回归就没有信任。
  5. L6 治理前置:授权链、标识嵌入、审计留痕应在产品上线前完成,而不是在争议发生后补救。
  6. 合规落点在导出与分发:《标识办法》第四条直指"下载、复制、导出",即梦 AI 2026-04-28 被查处即为明证。

7.5 选型建议

妙鸭相机不具备当前选型价值,其价值在于作为评估其他平台的对照坐标。在评估任何换装、换脸、写真类平台时,可直接使用以下四条由妙鸭案例提炼的判据:

判据提问方式不通过的信号
L4 可携带性用户能否导出 / 迁移自己的身份资产?资产只能在本产品内使用
L3 可干预性成片不满意时,能否定向修正而非重跑?只能换模板重来
L5 可量化性平台是否提供身份保真的量化口径?只有"更像我一点"式模糊滑块
L6 可审计性授权链与标识是否在工程层实现?只有一份用户协议

四条全不通过的产品,无论模型多强,都应视为高风险标的。

信息缺口声明

  1. 团队解散的权威信源:仅第三方工具站表述"2025 年 9 月底正式解散",未定位到科技媒体报道或工商 / 司法信息佐证,标注 。
  2. 当前 App 版本号:存在 v4.6.14(更新于 2026-08-18)与 v4.3.1(更新于 2026-04-08)两个冲突口径,标注 [待填写]
  3. 当前运营状态:产品是否仍在提供服务、服务范围如何,未检索到可靠信息,标注 [待填写]
  4. 定价数据:¥9.9 / ¥29.9 及 2 钻石/次均为 2023 年时点的第三方一致表述,非官方页面存档,标注 。
  5. B 端合作(携程「AI 旅拍」):单一低置信来源,无官方公告佐证,标注 。
  6. 用户协议争议的具体条款内容:仅第三方转述争议焦点,未检索到协议原文文本,标注 [待填写]
  7. 标识合规实现:未检索到妙鸭关于显式标识 / 隐式标识 / 数字水印的任何公开说明,标注 [待填写]
  8. 官方商家案例与量化效果数据:未检索到,如实标注"未检索到",不以"行业广泛使用"等模糊表述替代。
  9. "提香"模型的技术细节(参数量、架构、训练数据):未检索到公开技术报告,标注 [待填写]

8. 参考资料

  1. 星火集 · 妙鸭相机产品页(含上线时间、团队解散信息、定价口径,第三方来源,中置信)。https://www.sparkx.zone/tools/174
  2. 《人工智能生成合成内容标识办法》全文 — 中央网信办、工业和信息化部、公安部、国家广播电视总局,2025-03-14。https://www.cac.gov.cn/2025-03/14/c_1743654684782215.htm
  3. 《人工智能生成合成内容标识办法》解读 — 中国政府网 / 新华社,2025-03-16。https://www.gov.cn/zhengce/202503/content_7014281.htm
  4. 《9月1日起,AI生成合成内容必须添加标识》 — 央视网,2025-03-15。https://big5.cctv.com/gate/big5/news.cctv.cn/2025/03/15/ARTI36OOL0hP5mpvU5cDgo4L250315.shtml
  5. 《技术不是侵权"挡箭牌" 法院这样认定 AI"盗脸"》 — 新华社《经济参考报》,2026-04-17。http://dz.jjckb.cn/www/pages/webpage2009/html/2026-04/17/content_115180.htm
  6. 《e案e审丨短剧角色 AI 换脸"神似"知名演员,是偶然"撞脸"还是故意侵权?》 — 北京互联网法院供稿,澎湃新闻。https://www.thepaper.cn/newsDetail_forward_32799628
  7. 百度百科 · 即梦AI(含 2026-04-28 因未落实标识规定被查处、数字人分身认证机制等条目,二次来源,建议以官方通报复核)。https://baike.baidu.com/item/%E5%8D%B3%E6%A2%A6App/67386767
  8. InstantID 官方项目页 — InstantX Team / 小红书 / 北京大学(零样本身份注入的技术对照基准)。https://instantid.github.io/
  9. CatVTON: Concatenation Is All You Need for Virtual Try-On with Diffusion Models — arXiv 2407.15886(换装方向术语与指标基准)。https://arxiv.org/pdf/2407.15886
  10. InstantID vs PuLID vs FaceID Comparison — Apatero(第三方实测对比,低—中置信,仅作量级参考)。https://apatero.com/blog/instantid-vs-pulid-vs-faceid-ultimate-face-swap-comparison-2025
  11. 妙鸭相机官网 — 未序网络科技(上海)有限公司。https://www.miaoya.cn/

Miaoya Camera (妙鸭相机)

1. Introduction

1.1 Platform Overview and Positioning

Miaoya Camera was the first phenomenon-level product of the 2023 AI portrait (AI 写真) track: users upload a batch of photos of themselves, pay to create a "digital avatar", and then batch-generate portrait outputs in different styles from that avatar. Its operating entity is Weixu Network Technology (Shanghai) Co., Ltd., incubated by a founding team in which Alibaba's Digital Media & Entertainment Group (DMEG) participated, and later merged into "Shenli Shijie", a wholly-owned company of Alibaba DMEG; its technical foundation is the "Tixiang" model developed in-house by Alibaba DMEG, which analyzes multi-angle photos to generate a 3D face model and supports dynamic expression simulation.

In the six-layer capability model of AI Harness, Miaoya is an extreme single-point sample: at L1 (turning the "person" itself into context) it made the most radical attempt of the time, at L4 (digital avatar as a persistent identity asset) it created this group's first mass-market "identity asset product", yet L2, L3, and L5 were nearly blank, and L6 suffered a public trust incident early on. It ultimately did not survive — the team was formally disbanded at the end of September 2025, and the product is kept running at minimum-level operation only, with no further feature upgrades or promotion.

This outcome makes Miaoya the only negative sample with a complete lifecycle in this group's research. Its value lies not in "what it did wrong", but in proving a proposition: given that generation quality is already good enough, what determines a product's survival is not the model but the Harness that carries the model.

1.2 Development History and Lifecycle

DateEventNotes
2023-07-17Miaoya Camera officially launchedPrimarily accessible via WeChat Mini Program and Alipay Mini Program
2023-08Reached #1 on the App Store overall chartDAU exceeded 600,000; at peak, 4,000+ people queued for portrait generation
2023-09Free version launchedAllows uploading 8 photos to try, lowering the first-use barrier
Within 2023User agreement controversyControversy over the terms of the user agreement; officially apologized and revised the agreement
2025-09Version updateAdded AI photo retouching and outfit-plan customization services
End of 2025-09Team formally disbandedProduct maintained at minimum-level operation only; no more upgrades or promotion

It should be noted that: the authoritative source for the fact of the team's disbandment is only the wording on a third-party tools website; no corroboration from tech media reports or business/judicial information has been located, marked [To be verified]; the current App version number also has two conflicting figures (v4.6.14 updated on 2026-08-18, and v4.3.1 updated on 2026-04-08), marked [To be filled]. All analyses in this section that are based on the fact of "disbandment" presume that the fact holds; if later review overturns it, the related attribution conclusions need to be re-evaluated.

1.3 Pricing and Open Form

ItemDetails
Open formWeChat Mini Program / Alipay Mini Program (primary entry) + iOS / Android App + official site miaoya.cn (brand showcase)
Digital avatar creationPromotional price ¥9.9 (standard price ¥29.9), including 10 portrait generations + 5 HD downloads
Subsequent per-photoRetouching / HD download about 2 Diamonds/time (about ¥2)
Free versionLaunched from 2023-09, upload 8 photos (fewer than the paid version's requirement of ≥20)
Model foundationIn-house "Tixiang" model by Alibaba DMEG, closed-source, no public API

The pricing above is point-in-time data from 2023, from consistent wording across multiple third-party sources, but none are archived official original pages, marked [To be verified]. Miaoya's pricing structure itself already exposed the problem with its business model: a one-time ¥9.9 buyout of one avatar + 10 outputs is typical "loss-leader pricing", lacking subsequent consumption scenarios and subscription anchors — a stark contrast with Kling's "Elements" (subject creation), another identity-type product, which limits 30 / 50 / 150 / 500 subjects by membership tier.


2. Glossary

2.1 General Direction Terms

TermEnglish / AbbreviationDefinition
Virtual Try-OnVTON (Virtual Try-On)Putting a target garment "on" a given person image and generating a visually plausible result; like Miaoya's "outfit-plan customization" added in 2025-09, it belongs to the problem family of "appearance transformation grounded in a fixed identity"
Garment WarpingGarment WarpingFirst aligning a flat garment to the human pose via geometric transforms such as TPS (Thin-Plate Spline), then feeding it into generation; representative method GP-VTON
Cloth MaskCloth MaskA binary map of top / bottom / outerwear regions obtained via Human Parsing, used to limit the repainting scope
Try-on DiffusionTry-on DiffusionFusing garment and body end-to-end with a diffusion model, dropping the explicit warping step; representative method OOTDiffusion's Outfitting Fusion
Face SwapFace SwapReplacing A's face onto B's facial position; post-hoc swap means replacing after generation completes, representative implementation ReActor
Face ReenactmentFace ReenactmentPreserving identity while transferring expression / lip-sync / head pose; Miaoya's "dynamic portrait" is a productized form of this capability
Identity PreservationIdentity PreservationTo what extent the generated result is still "that person"; the shared core metric of the three product families: outfit-changing, face-swapping, and digital avatars
IP-AdapterIP-AdapterInjecting features from an image encoder (CLIP) into attention to realize "image as prompt"
Zero-shot Identity CustomizationInstantIDSingle reference image, transferring identity without fine-tuning; composed of ID Embedding + lightweight adapter module (decoupled cross-attention) + IdentityNet
Pure and Lightning ID CustomizationPuLID (Pure and Lightning ID Customization)ByteDance's contrastive-learning + Lightning-distillation scheme, to alleviate InstantID's problems of "face too stiff, weak prompt following"
Controllable GenerationControlNetA plug-in style network that uses visual signals such as Canny edges, Depth, Pose, and Masks as extra conditions to control generation structure
InpaintingInpaintingRegenerating a specified region of an image (requires a mask / brush), leaving the rest unchanged
Low-Rank AdaptationLoRAA small-parameter fine-tuning module used to fix specific person / style / garment assets
DeepfakeDeepfakeUsing deep synthesis to forge faces / voices; a core source of portrait-right and fraud risk
IdentifiabilityIdentifiabilityThe core standard for judging portrait-right infringement in court: exact identity is not required — it holds if the public can recognize the person

2.2 Miaoya-Specific Terms

TermEnglish / AbbreviationDefinition
Digital AvatarDigital Avatar / Digital TwinAfter the user uploads ≥20 multi-angle, multi-expression, multi-lighting half-body photos, the model builds a dedicated face / image model; an identity asset that is trained once and reused many times
Tixiang ModelTixiang ModelAlibaba DMEG's in-house portrait-generation model and Miaoya's technical foundation, which generates a 3D face model by analyzing multi-angle photos
Make It More Like MeSimilarity TuningMiaoya's similarity fine-tuning feature for raising the similarity between the generated image and the user; the only "evaluate and correct" entry point in the product
Queue-based RenderingQueue-based RenderingBecause of compute limits, avatar creation and output generation require queues, from several hours to a dozen-plus hours (at peak)
Style Template LibraryStyle Template Library30+ scenario templates (Japanese pure-cute, workplace formal wear, Miao-village girl, ancient-style, ID photo, travel blockbuster, etc.); the App additionally cites "11 AI image-making styles"
DiamondsDiamondsMiaoya's in-app virtual currency unit, used for per-photo retouching and HD download (about 2 Diamonds/time)
Outfit CustomizationOutfit CustomizationCapability added in the 2025-09 version; an extension by Miaoya toward the outfit-changing (VTON) direction

3. Feature Description

3.1 Core Functional Chain

Miaoya's functional chain is extremely short, with only three steps:

  1. Upload and Training: the user uploads ≥20 multi-angle, multi-expression, multi-lighting half-body photos of themselves, and the system builds a digital avatar (requiring a queue, from several hours to a dozen-plus hours at peak);
  2. Template Application: choose from 30+ style templates, and the avatar drives generation of portrait outputs in the corresponding style;
  3. Retouching and Download: retouch and HD-download the selected output (consuming Diamonds), or use AI photo retouching (added in the 2025-09 version).

The engineering feature of this chain is: every interaction is an atomic operation. User upload → wait → choose template → generate output; among these four steps there is no intermediate state to intervene in, no parameter to tune, and no batch-processing entry. When an output's quality is unsatisfactory, the only things a user can do are "choose a template again" or "fine-tune with Make It More Like Me" — unlike Kling O1, which can iterate and correct in the same session with natural language, or ComfyUI, which can go back to some node and rerun.

3.2 Template and Style System

DimensionMiaoya's implementationEngineering assessment
Style source30+ platform-preset templates (also called 11 AI image-making styles in the App)Strongly controlled by the platform; users cannot customize
Identity sourceUser's own digital avatar (trained from ≥20 photos)High user-side investment, large sunk cost
Combination methodAvatar × template = output, one-to-oneNo cross-combination, no parameter space
Extension methodOutfit customization (added 2025-09)Extension direction is correct, but the timing of rollout was already late

The design of the template system exposes a key trade-off: Miaoya put all of the "controllability" on the platform side and all of the "investment" on the user side. Users paid 20 photos and hours of queuing, yet got zero control over the generation process. This asymmetry is masked by "novelty" in a product's early days, but once the novelty fades it inevitably turns into a retention problem.

3.3 B-Side and Open Capabilities

Miaoya once attempted to extend toward the B side: by opening an API, it cooperated with platforms such as Ctrip to launch enterprise-level services like "AI Travel Photography". This information has low confidence and is marked [To be verified] — no official announcement, cooperation press release, or Ctrip-side product page has been found to corroborate it.

From a Harness perspective, even if that cooperation were real, Miaoya lacked the infrastructure to support B-side engineering integration: no public API documentation, no concurrency/quota contracts, no callback mechanism, no error-code specification. By contrast, enterprise-oriented image platforms of the same period (such as Leonardo.ai) had already explicitly documented the three capacity constraints of rate limits, concurrency caps, and queue depth, and provided Webhook and idempotency guidance. This contrast is the watershed of "whether a Harness exists".


4. Platform Architecture

图 4-1|妙鸭相机训练式身份管线:从照片到写真成片

妙鸭相机训练式身份管线:从照片到写真成片 信息截止 2026-09 · 示意:基于本文分析绘制 上传 ≥20 张多角度照片 本人半身照 · 多表情多光线 人脸检测与对齐 多角度照片预处理 提香模型 per-user 训练 训练式身份注入路线 数字分身 人脸/形象模型 · 持久身份资产 分身驱动生成 风格模板 提示词 + 构图 + 光影 合成 分身 × 模板一一对应 写真成片 30+ 场景模板可选 精修 / 高清下载 消耗钻石 · 约 2 钻石/次 分发形态(4.2) 微信小程序 / 支付宝 主入口 · 低获客成本 iOS / Android App 多端账号互通 · 云端存储 官网 miaoya.cn 仅品牌展示 · 无开放 API 对照路线:零样本身份注入(InstantID / PuLID)——单张照片 · 秒级出图 · 权重可跨管线迁移 结构解读:训练式路线把身份资产做成产品内私有状态,成本与等待高企,L4 锁死是失效根因。

数据来源:基于本文分析绘制的示意图。

4.1 Training-Based Identity Pipeline

Miaoya adopts a training-based (per-user fine-tune) technical route rather than zero-shot adaptation:

≥20 张多角度照片 → 人脸检测与对齐 → 提香模型 per-user 训练 → 数字分身(人脸 / 形象模型)
                                                                    ↓
                                        风格模板(提示词 + 构图 + 光影)→ 合成 → 成片 → 精修 / 高清下载

This is a fundamental difference from the "zero-shot identity injection" route of InstantID, PuLID, etc., and is the root cause of its persistently high cost and waiting time:

DimensionTraining-based (Miaoya)Zero-shot injection (InstantID / PuLID)
Sample requirement≥20 multi-angle, multi-expression, multi-lighting photosA single reference image suffices
Time to first useSeveral hours to a dozen-plus hours (queuing)Seconds to minutes
Compute costOne full training run per userSingle forward inference
Identity-fidelity ceilingHigh (has seen multiple angles)Medium—high (relies on single-image generalization)
Iteration costVery high (re-upload, re-train)Very low (just swap the reference image)
PortabilityLocked within a single productWeights / adapters can be loaded by any pipeline

The training-based route was a reasonable choice in 2023 — zero-shot approaches were not yet mature; but Miaoya did not complete the route migration after zero-shot approaches matured in 2024—2025, instead cementing its cost structure. This is a typical case of technical debt turning into commercial failure.

4.2 Distribution Form

  • The primary entry is the Mini Program (WeChat / Alipay), with the App as auxiliary and the official site as a brand showcase only. The mini-program-first strategy brought extremely low acquisition costs and very fast dissemination in 2023, but the price was capabilities constrained by the host environment (file export, background tasks, and compute scheduling are all limited).
  • Cross-platform account interoperability (iOS / Android / WeChat / Alipay), with avatars and outputs stored in the cloud.
  • No open API (any B-side cooperation, if it existed, was bespoke per case, not a platformized capability).

4.3 Comparison with the Zero-Shot Identity-Injection Route

From a Harness standpoint, the difference between the two routes can be summed up in one sentence: the training-based route turns the identity asset into a "private state within the product", while the zero-shot route turns the identity asset into a "context that can circulate across pipelines". The former looks stronger at L4 (a dedicated model) but is in fact weaker — because it cannot be migrated, combined, or audited; the latter looks lighter, yet gains true asset liquidity because "the identity adapter can be loaded by anything".


5. Harness Design

5.1 Six-Layer Capability Overview

LayerMiaoya's implementationMaturityEvidence strength
L1 Context EngineeringTurning the "person" itself into context: 20 photos → digital avatar → template promptMediumMedium
L2 Tools and ExecutionTemplate application primarily; tooling capability very weak (crop / color / defect fix / AI retouch)WeakMedium
L3 Orchestration and ControlAlmost no orchestration: a single "select template → generate" atomic operationWeakMedium
L4 Memory and StateDigital avatar is the only persistent asset, but locked within a single product and not migratableWeakMedium
L5 Evaluation and ObservabilityOnly the "Make It More Like Me" manual subjective fine-tuning; no quantitative evaluationWeakMedium
L6 Governance and SafetyControversy over user-agreement terms, later apologized and revised; no public explanation of identity-marking mechanismsMedium (negative early on)Medium

5.2 L1 Context Engineering Layer

At L1, Miaoya made a design that was highly imaginative for its time: compressing the "person" itself into context. Traditional text-to-image context is the prompt; Miaoya's context is "a trained person". From an engineering standpoint, this changes high-dimensional identity information (bone structure, facial-proportion, skin tone, expression habits) from "needing to be re-described for every generation" into "injected once, reused long-term".

The problem with this design is that it is one-shot and non-editable:

  • Users cannot adjust "which features are remembered and which are ignored" (contrast Kling's Identity Map, which decouples "stable identity markers" from "transient attributes (expression / outfit / lighting)");
  • Users cannot add context for new scenarios (contrast FLUX.2, which supports carrying up to 8—10 reference images with a task);
  • The only tuning knob is "Make It More Like Me" — a vague slider with no dimension and no feedback loop.

In other words, Miaoya's L1 is a "write-once, read-only" context, whereas the third-generation Harness requires context to be "assemblable, trimmable, and priority-orderable".

5.3 L2 Tools and Execution Layer

The toolset is extremely thin: template selection, crop, color, defect repair, AI photo retouching (added 2025-09). There is no external tool-registration mechanism, no scripting entry point, no batch processing, and no tool contract of any kind.

For a C-end portrait product, few tools is not fatal; what is fatal is: few tools + no orchestration = every user need must be preset by the platform. Once the 30+ templates are used up, the product loses any new source of value supply.

5.4 L3 Orchestration and Control Layer

This is Miaoya's weakest layer and the direct cause of its user-experience collapse:

Missing orchestration capabilityConcrete consequence
No task-queue visualization or priority schedulingAt peak, 4,000+ people queued for portrait generation; wait times unpredictable
No batch processingCannot select from "generating 20 styles at once" in bulk
No intermediate-state interventionIf an output is unsatisfactory, only full rerun; cannot target-fix a region
No workflow / no API orchestrationB-side integration only as bespoke cases, unable to scale
No failure retry or state recoveryAfter a training interruption, users' sunk cost cannot be traced

"Queue-based rendering" is the most visible product of this layer's failure: it essentially passes compute scarcity directly on to users, without shaping load, degrading, async-ing, or managing expectations through the orchestration layer.

5.5 L4 Memory and State Layer

The digital avatar is Miaoya's only persistent asset and the whole of its value — this sentence is both its product positioning and its death sentence.

Identity Preservation is the shared L4 core challenge of the three product families — outfit-changing, face-swapping, and digital avatars: its technical essence is persisting "identity features" as cross-session state. Whoever makes L4 solid is who keeps users — because users' investment (photos, time, accumulated aesthetic preferences) all attaches to this layer, forming switching costs.

But Miaoya's L4 is a one-way locked asset:

  1. Not migratable: the avatar exists only inside the Miaoya product; users cannot export the model or reuse it elsewhere. This means all of a user's investment in Miaoya is one-off sunk cost, not a portable asset.
  2. Not combinable: the avatar can only combine with platform-preset templates, not with the user's own reference images, brand assets, or scene constraints.
  3. Not versionable: there is no concept of "avatar v1 / v2"; users cannot go back to a more satisfactory identity version.
  4. Dies with the product: once the team disbanded and the product stopped operating, users' identity assets disappeared along with it.

Contrast the same track's practitioners who got L4 right: Kling made "Elements" (subject creation) reusable subjects metered by tier (30 / 50 / 150 / 500); Runway made Brand Kits (up to 3) and Custom Voice Clones (up to 3) first-class assets; FLUX.2's Base variant is designed specifically for LoRA fine-tuning, so identity and brand assets are held by users themselves as weights; the ComfyUI ecosystem puts both workflow JSON graphs and LoRA weights under version control. What they share: ownership and portability of assets rest on the user side. Miaoya is exactly the opposite — it kept users' strongest asset on its own servers while failing to offer enough long-term value to make users stay.

5.6 L5 Evaluation and Observability Layer

Miaoya has no evaluation layer in the engineering sense. The only evaluation entry point in the product is "Make It More Like Me" — relying on users' subjective judgment through trial and error, with no objective metrics, no regression set, and no A/B mechanism.

For identity-type products, this is not a minor issue: identity fidelity is a quantifiable metric (face-recognition embedding similarity, cross-age / cross-style stability), and the open-source ecosystem has long built evaluation baselines with SSIM / FID / KID / LPIPS and face-recognition accuracy (e.g. community measurements where PuLID face-recognition accuracy is 91%, InstantID 84%, IP-Adapter FaceID 76—82%; this set is low-confidence community measurement, for order-of-magnitude reference only). Miaoya neither publicized its own evaluation methodology nor put evaluation capability into users' hands, so users could not judge "whether the avatar generated this time looks more like me than last time" and could only vote with their feet.

5.7 L6 Governance and Safety Layer

Miaoya's record at the governance layer is negative first, then corrected:

  • User-agreement controversy (2023): early on, its user-agreement terms sparked controversy — the focus was the boundary of the platform's rights to use users' uploaded photos and generated content. Officials later apologized and revised the agreement, promising that photos would be used only for this avatar creation, that original uploaded photos would be automatically deleted after completion, and that anonymization would be supported. The details of this incident come from third-party accounts and are marked [To be verified].
  • Identity-marking compliance gap: no public explanation of any implementation of generated-content marking (explicit marking / implicit metadata marking / digital watermark) has been found for Miaoya, marked [To be filled].

In terms of compliance applicability, Miaoya's product form falls within the scope of multiple regulatory requirements:

  • Measures for the Labeling of AI-Generated Synthetic Content (National Cyberspace Administration Communication Note 〔2025〕No. 2, effective 2025-09-01), Article 4: when service providers provide functions such as downloading, copying, and exporting of generated synthetic content, they shall ensure the file contains the required explicit labeling; Article 5: they shall add implicit labeling to the file metadata (including attribute information of the generated synthetic content, the service provider's name or code, content number, etc.), and are encouraged to add digital-watermark forms of implicit labeling. Miaoya's core paid point is precisely "HD download", which falls directly within the scope of Article 4.
  • Civil Code of the People's Republic of China, Article 1018: a portrait is a "recognizable external image of a specific natural person reflected on a certain medium"; Article 1019: no organization or individual may infringe another's portrait right by defaming, defacing, or forging through information-technology means or otherwise, and without the portrait-right holder's consent, may not produce, use, or publish the portrait-right holder's portrait. Although the digital avatar is trained on the user's own portrait, once it is used to generate scene images different from the user and distributed externally, it enters the review scope of portrait right and the authorization chain.
  • A Beijing Internet Court judgment effective 2026-03 established two key rules: identifiability is the core criterion for determining infringement (an AI face-swapped image need not be fully identical to the original portrait; if the general public can identify the person, it constitutes use of a specific natural person's portrait); burden-of-proof shift (a defendant claiming "accidental AI resemblance" must reproduce the creative process; failure to reproduce leads to the adverse consequence of failing to prove). The judgment also clarified that "technological neutrality" is not a ground for exemption.
  • Industry warning: on 2026-04-28, Jimeng AI — also an object of this group's research — was investigated and dealt with by cyberspace authorities for failing to effectively implement the labeling requirements for AI-generated synthetic content. This shows that the regulatory focus is on the export and distribution stages, not the model capability itself.

Miaoya's lesson: governance is not a documentation exercise for the compliance department, but an engineering implementation of L6 — the authorization chain, identity labeling, audit trails, and reproducible creation records, all indispensable. The user-agreement controversy is merely the first visible face of the missing L6.

5.8 Maturity Assessment and Failure Attribution

Conclusion: Miaoya is the archetype of "strong model, weak Harness". Its generation capability was top-tier in 2023 (otherwise it would not have topped the App Store overall chart), but four of the six Harness layers (L2 / L3 / L4 / L5) were blank or failed, and L6 was even a negative asset at a critical time.

Failed layerFailure manifestationDirect consequenceConsequence transmitted to business
L2 ToolsToolset is only templates and basic retouchingUsers have no room for secondary creationOutput is the end point; no add-on consumption
L3 OrchestrationNo batch processing, no queue scheduling, no intermediate statesHours of queuing, uncontrollable outputsExperience collapse, reputation loss
L4 StateAvatar locked, not migratable, not versionableUser investment cannot settle into portable assetsOne-off sale; no retention anchor
L5 EvaluationNo quantitative identity-fidelity evaluationQuality cannot be regressed or demonstratedUsers cannot build trust
L6 GovernanceAgreement controversy + blank identity-marking mechanismTrust incident + compliance exposureBrand damage, regulatory risk

These five layers did not fail independently but amplified one another: L4 lock-in prevented users from accumulating assets → missing L2/L3 prevented users from creating new value → users left → missing L5 prevented the platform from noticing quality decline → the L6 incident accelerated trust erosion. No matter how strong the model, it cannot fill the structural gaps of the Harness.


6. Actual Cases

6.1 Scale Data at the 2023 Outbreak Moment

The available scale data are all point-in-time values from 2023 and must be labeled as such; they cannot be cited as the current state:

  • Topped the App Store overall chart in 2023-08;
  • DAU exceeded 600,000;
  • At peak, 4,000+ people queued for portrait generation.

The meaning of this data is to depict the industry backdrop of "the first wave of the AI portrait track": it proves that there is real and strong C-end demand for "AI-generating one's own image". The demand was real, yet the product failed to keep users — which precisely shows that the demand side was not the bottleneck; the supply-side engineering capability (Harness) was.

6.2 Ctrip "AI Travel Photography"

According to a third-party source, Miaoya once opened an API to cooperate with Ctrip on an enterprise-level "AI Travel Photography" service. This information has low confidence; no official announcement or Ctrip-side product page has been found to corroborate it, marked [To be verified].

Even if true, from a Harness standpoint this cooperation would be hard to scale: Miaoya has no public API contract, concurrency quota, callback mechanism, or error-code specification; B-side integration could only rely on bespoke per-case work, with marginal cost not declining with customer count. This is fundamentally different from "platformized B-side capability".

6.3 User-Agreement Controversy Incident

In 2023, Miaoya sparked controversy over its user-agreement terms — the core of the dispute was the boundary of the platform's rights to use users' uploaded photos and generated content. Officials later apologized and revised the agreement, making three promises: photos would be used only for this avatar creation, original uploaded photos would be automatically deleted after completion, and anonymization would be supported.

This incident is the earliest "identity-asset governance incident" record in this group's documents; its engineering meaning is that when a product takes users' biometric features (faces) as a core input, the authorization chain and the data lifecycle must be first-class citizens of L6, not hidden inside a lengthy agreement text. Subsequent products of the same kind (such as Jimeng restricting real-person material use and introducing digital-human avatar authentication from 2026-02) are precisely a productized response to this lesson.

6.4 Lifecycle Review

Miaoya demonstrated that an AI portrait product defined by "single-point viral hit + no workflow depth + no asset portability" is hard to retain. Its lifecycle can be summarized in four phases:

  1. Demand-validation phase (2023-07 to 2023-08): extremely low acquisition cost + extremely strong novelty → explosive growth;
  2. Experience-overdraft phase (2023-08 to 2023-12): queuing, uncontrollable outputs, agreement controversy → reputation decline;
  3. Capability-stagnation phase (all of 2024): competitors rapidly caught up on zero-shot identity injection and editing capabilities, while Miaoya saw no architecture-level upgrade;
  4. Exit phase (2025): after the 2025-09 version added AI retouching and outfit-plan customization, the team disbanded at the end of 2025-09 and the product was kept at minimum-level operation.

Of these, the third phase is the most alarming: Miaoya was not defeated by a specific competitor but was left behind by a "technology paradigm shift". When zero-shot identity injection (InstantID / PuLID) compressed "20 photos + hours of queuing" into "1 photo + second-level output", Miaoya's cost structure instantly went from "an acceptable price" to "an unreasonable burden". And it lacked the ability to complete this migration, because its entire product architecture (and even its business model) was built on the technical premise of "training-based avatars".


7. Summary

7.1 Strengths

  1. First attempt to make "identity" into a mass-market product: in 2023 it already let ordinary users experience an identity-asset form of "invest once, reuse many times", which was pioneering.
  2. Generation quality was top-tier among its peers: being able to top the App Store overall chart and drive social virality shows the output quality passed the test of mass-market aesthetics.
  3. Extremely low acquisition cost: mini-program-first + social sharing is a classic paradigm for C-end AI products to acquire users cheaply.
  4. Validated a real demand: 600,000 DAU proves that "AI-generating one's own image" is a real need, not a fake one.

7.2 Limitations and Root Causes of Failure

  1. The technical route was left behind by a paradigm shift: the training-based avatar completely lost its cost advantage after zero-shot identity injection matured, and the architecture could not migrate smoothly.
  2. L4 asset locked one-way: the identity asset could not be migrated, combined, or versioned, so user investment became sunk cost.
  3. Missing L3 orchestration collapsed the experience: hours of queuing, no batch processing, no intermediate-state intervention.
  4. Blank L5 evaluation: no quantitative identity-fidelity methodology; quality could not be regressed or demonstrated.
  5. L6 governance was negative early on: user-agreement controversy + blank identity-marking mechanism.
  6. No depth to the business model: one-time ¥9.9 buyout, lacking subscription anchors and subsequent consumption scenarios.

7.3 Applicability Boundary

ScenarioApplicable?Notes
As a currently production-usable portrait / outfit-changing solutionNot applicableTeam already disbanded; product maintained at minimum-level operation only, no more upgrades
As historical sample research of an "identity asset product"ApplicableComplete lifecycle + complete failure chain, extremely high research value
As teaching material for a Harness negative caseHighly applicableTransmission path of five layers' failure is clear and traceable
As a business-model referenceWith cautionDemand side holds; supply-side pricing and retention structure failed

7.4 Engineering Lessons for Successors

  1. Identity assets must be portable: make identity an asset users can export, migrate, and version, not the platform's private state.
  2. The technical route must be able to migrate across paradigms: treat "training-based" as a swappable implementation detail, not a premise of the product architecture.
  3. L3 orchestration is the floor of experience: queuing, batch processing, and intermediate-state intervention are not optimization items but usability items.
  4. L5 must quantify identity fidelity: no metrics means no regression; no regression means no trust.
  5. L6 governance upfront: the authorization chain, identity labeling, and audit trails should be done before the product launches, not patched after a controversy.
  6. The compliance focus is on export and distribution: Article 4 of the Labeling Measures directly targets "download, copy, export", and Jimeng AI being investigated on 2026-04-28 is the proof.

7.5 Selection Recommendation

Miaoya Camera has no current-selection value; its value lies in serving as a reference coordinate for evaluating other platforms. When evaluating any outfit-changing, face-swapping, or portrait platform, the following four criteria distilled from the Miaoya case can be used directly:

CriterionHow to askSignal of failure
L4 portabilityCan users export / migrate their own identity assets?Assets can only be used within this product
L3 intervenabilityWhen an output is unsatisfactory, can it be targeted-corrected rather than rerun?Can only switch templates and start over
L5 quantifiabilityDoes the platform provide a quantitative methodology for identity fidelity?Only a "Make It More Like Me"-style vague slider
L6 auditabilityAre the authorization chain and identity labeling implemented at the engineering layer?Only a user agreement

Any product that fails all four criteria, no matter how strong its model, should be treated as a high-risk target.

Information-Gap Statement

  1. Authoritative source for the team's disbandment: only a third-party tools website states it was "formally disbanded at the end of September 2025"; no corroboration from tech media or business / judicial information has been located, marked .
  2. Current App version number: two conflicting figures exist — v4.6.14 (updated 2026-08-18) and v4.3.1 (updated 2026-04-08), marked [To be filled].
  3. Current operating status: whether the product still provides services and its scope have not been reliably found, marked [To be filled].
  4. Pricing data: ¥9.9 / ¥29.9 and 2 Diamonds/time are all third-party consistent statements at the 2023 point in time, not archived official pages, marked .
  5. B-side cooperation (Ctrip "AI Travel Photography"): a single low-confidence source, no official announcement confirms it, marked .
  6. The specific terms of the user-agreement controversy: only third-party accounts of the dispute's focus; no original agreement text has been found, marked [To be filled].
  7. Identity-marking compliance implementation: no public explanation by Miaoya of explicit / implicit labeling or digital watermarks has been found, marked [To be filled].
  8. Official merchant cases and quantitative effectiveness data: none found; honestly marked as "not found" rather than replaced by vague wording such as "widely used in the industry".
  9. Technical details of the "Tixiang" model (parameter count, architecture, training data): no public technical report has been found, marked [To be filled].

8. References

  1. Sparkx Collection · Miaoya Camera product page (includes launch time, team-disbandment information, and pricing figures; third-party source, medium confidence). https://www.sparkx.zone/tools/174
  2. Full text of the Measures for the Labeling of AI-Generated Synthetic Content — Cyberspace Administration of China, Ministry of Industry and Information Technology, Ministry of Public Security, National Radio and Television Administration, 2025-03-14. https://www.cac.gov.cn/2025-03/14/c_1743654684782215.htm
  3. Interpretation of the Measures for the Labeling of AI-Generated Synthetic Content — Gov.cn / Xinhua News Agency, 2025-03-16. https://www.gov.cn/zhengce/202503/content_7014281.htm
  4. "From September 1, AI-generated synthetic content must carry a label" — CCTV, 2025-03-15. https://big5.cctv.com/gate/big5/news.cctv.cn/2025/03/15/ARTI36OOL0hP5mpvU5cDgo4L250315.shtml
  5. "Technology is not an infringement shield; court rules this way on AI face 'theft'" — Xinhua Economic Information Daily, 2026-04-17. http://dz.jjckb.cn/www/pages/webpage2009/html/2026-04/17/content_115180.htm
  6. "e-case | e-trial: A short-drama character's AI face-swap 'closely resembles' a famous actor — accidental resemblance or deliberate infringement?" — contributed by the Beijing Internet Court, The Paper. https://www.thepaper.cn/newsDetail_forward_32799628
  7. Baidu Baike · Jimeng AI (including entries on being investigated on 2026-04-28 for failing to implement labeling rules, the digital-human avatar authentication mechanism, etc.; secondary source, recommended to cross-check against official announcements). https://baike.baidu.com/item/%E5%8D%B3%E6%A2%A6App/67386767
  8. InstantID official project page — InstantX Team / Xiaohongshu / Peking University (technical reference baseline for zero-shot identity injection). https://instantid.github.io/
  9. CatVTON: Concatenation Is All You Need for Virtual Try-On with Diffusion Models — arXiv 2407.15886 (terminology and metric baseline for the outfit-changing direction). https://arxiv.org/pdf/2407.15886
  10. InstantID vs PuLID vs FaceID Comparison — Apatero (third-party measured comparison, low—medium confidence, for order-of-magnitude reference only). https://apatero.com/blog/instantid-vs-pulid-vs-faceid-ultimate-face-swap-comparison-2025
  11. Miaoya Camera official site — Weixu Network Technology (Shanghai) Co., Ltd. https://www.miaoya.cn/