platform-product-manager

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Platform Product Manager

平台产品经理

Strategic product management expertise for API-first and developer-focused platforms — from API design and developer experience to ecosystem building and platform metrics.

面向API优先及开发者聚焦型平台的战略性产品管理专业知识——涵盖API设计、开发者体验、生态系统构建及平台指标等内容。

Philosophy

核心理念

Great platform products aren't about features. They're about making developers successful.

The best API and platform products:

Developer experience is product experience — DX is your primary differentiator
APIs are user interfaces — Design them with the same care as visual UIs
Documentation is product — Great docs reduce support, increase adoption, drive success
Ecosystem multiplies value — Your integrations make your platform stickier

优秀的平台产品无关功能堆砌，而是致力于让开发者获得成功。

最佳的API与平台产品具备以下特质：

开发者体验即产品体验——DX是你的核心差异化优势
API即用户界面——像设计可视化UI一样精心设计API
文档即产品——优质文档能减少支持成本、提升采用率、推动成功
生态系统放大价值——你的集成功能让平台更具粘性

How This Skill Works

该技能的运作方式

When invoked, apply the guidelines in

rules/

organized by:

```
api-*
```
— API design principles, standards, and patterns
```
dx-*
```
— Developer experience, onboarding, and success
```
docs-*
```
— Developer documentation strategy and standards
```
sdk-*
```
— SDK and library strategy
```
versioning-*
```
— API versioning, deprecation, and migration
```
community-*
```
— Developer community and ecosystem building
```
marketplace-*
```
— Integration marketplace and partner strategy
```
metrics-*
```
— Platform health and success metrics

调用时，将应用

rules/

目录下按以下类别组织的指导原则：

```
api-*
```
— API设计原则、标准与模式
```
dx-*
```
— 开发者体验、入门引导与成功策略
```
docs-*
```
— 开发者文档策略与标准
```
sdk-*
```
— SDK与库策略
```
versioning-*
```
— API版本控制、弃用与迁移
```
community-*
```
— 开发者社区与生态系统搭建
```
marketplace-*
```
— 集成市场与合作伙伴策略
```
metrics-*
```
— 平台健康度与成功指标

Core Frameworks

核心框架

Platform Maturity Model

平台成熟度模型

Stage	Focus	Key Metrics	Team Structure
Foundation	Core API, basic docs	API uptime, error rates	PM + Engineers
Growth	DX, SDKs, onboarding	Time-to-first-call, activation	+ DevRel, DX engineers
Scale	Ecosystem, marketplace	Integration count, partner revenue	+ Partner team
Platform	Network effects, flywheel	Platform GMV, ecosystem value	Full platform org

阶段	核心聚焦	关键指标	团队结构
基础阶段	核心API、基础文档	API可用性、错误率	产品经理 + 工程师
增长阶段	开发者体验、SDK、入门引导	首次调用时间、激活率	+ 开发者关系、DX工程师
规模化阶段	生态系统、集成市场	集成数量、合作伙伴收入	+ 合作伙伴团队
平台化阶段	网络效应、飞轮效应	平台GMV、生态系统价值	完整平台团队

The Developer Journey

开发者旅程

┌─────────────┐   ┌─────────────┐   ┌─────────────┐   ┌─────────────┐
│  DISCOVER   │ → │   EVALUATE  │ → │   ADOPT     │ → │   EXPAND    │
│             │   │             │   │             │   │             │
│ - Search    │   │ - Docs      │   │ - Signup    │   │ - More APIs │
│ - Content   │   │ - Sandbox   │   │ - First call│   │ - Higher    │
│ - Referral  │   │ - Pricing   │   │ - Use case  │   │   volume    │
│             │   │             │   │   solved    │   │ - Referral  │
└─────────────┘   └─────────────┘   └─────────────┘   └─────────────┘

┌─────────────┐   ┌─────────────┐   ┌─────────────┐   ┌─────────────┐
│  DISCOVER   │ → │   EVALUATE  │ → │   ADOPT     │ → │   EXPAND    │
│             │   │             │   │             │   │             │
│ - Search    │   │ - Docs      │   │ - Signup    │   │ - More APIs │
│ - Content   │   │ - Sandbox   │   │ - First call│   │ - Higher    │
│ - Referral  │   │ - Pricing   │   │ - Use case  │   │   volume    │
│             │   │             │   │   solved    │   │ - Referral  │
└─────────────┘   └─────────────┘   └─────────────┘   └─────────────┘

API Design Hierarchy

API设计层级

                    ┌─────────────────┐
                    │   CONSISTENCY   │  ← Predictable patterns
                    ├─────────────────┤
                    │   SIMPLICITY    │  ← Easy to understand
                    ├─────────────────┤
                    │   DISCOVERABILITY│ ← Self-documenting
                    ├─────────────────┤
                    │   RELIABILITY   │  ← Stable and trustworthy
                    ├─────────────────┤
                    │   PERFORMANCE   │  ← Fast and efficient
                    └─────────────────┘

                    ┌─────────────────┐
                    │   CONSISTENCY   │  ← Predictable patterns
                    ├─────────────────┤
                    │   SIMPLICITY    │  ← Easy to understand
                    ├─────────────────┤
                    │   DISCOVERABILITY│ ← Self-documenting
                    ├─────────────────┤
                    │   RELIABILITY   │  ← Stable and trustworthy
                    ├─────────────────┤
                    │   PERFORMANCE   │  ← Fast and efficient
                    └─────────────────┘

Developer Success Metrics Stack

开发者成功指标体系

┌─────────────────────────────────────────────────────────────────┐
│                    BUSINESS OUTCOMES                            │
│        Revenue, Retention, Net Dollar Retention                 │
├─────────────────────────────────────────────────────────────────┤
│                    DEVELOPER SUCCESS                            │
│     Active Developers, API Calls, Use Cases Completed           │
├─────────────────────────────────────────────────────────────────┤
│                    DEVELOPER EXPERIENCE                         │
│   Time-to-First-Call, Activation Rate, Support Tickets          │
├─────────────────────────────────────────────────────────────────┤
│                    PLATFORM HEALTH                              │
│        Uptime, Latency, Error Rates, Documentation Quality      │
└─────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│                    BUSINESS OUTCOMES                            │
│        Revenue, Retention, Net Dollar Retention                 │
├─────────────────────────────────────────────────────────────────┤
│                    DEVELOPER SUCCESS                            │
│     Active Developers, API Calls, Use Cases Completed           │
├─────────────────────────────────────────────────────────────────┤
│                    DEVELOPER EXPERIENCE                         │
│   Time-to-First-Call, Activation Rate, Support Tickets          │
├─────────────────────────────────────────────────────────────────┤
│                    PLATFORM HEALTH                              │
│        Uptime, Latency, Error Rates, Documentation Quality      │
└─────────────────────────────────────────────────────────────────┘

Platform Types

平台类型

Type	Examples	Key Success Factor	Primary Metric
Infrastructure API	Stripe, Twilio, AWS	Reliability + DX	API calls, uptime
Data API	Plaid, Clearbit	Data quality + freshness	Data coverage
Aggregation Platform	Zapier, Segment	Integrations + ease	Connections made
Developer Tools	GitHub, Vercel	Workflow fit + speed	Active projects
Embedded Platform	Shopify Apps	Distribution + value	Install rate, GMV

类型	示例	关键成功因素	核心指标
基础设施API	Stripe、Twilio、AWS	可靠性 + DX	API调用量、可用性
数据API	Plaid、Clearbit	数据质量 + 新鲜度	数据覆盖范围
聚合平台	Zapier、Segment	集成数量 + 使用便捷性	建立的连接数
开发者工具	GitHub、Vercel	工作流适配性 + 速度	活跃项目数
嵌入式平台	Shopify Apps	分发能力 + 价值贡献	安装率、GMV

API Style Comparison

API风格对比

Style	Best For	Complexity	Flexibility	Caching
REST	CRUD operations, simple resources	Low	Medium	Excellent
GraphQL	Complex data fetching, mobile	Medium	High	Manual
gRPC	Internal services, high perf	High	Low	N/A
Webhooks	Real-time events, async flows	Low	Medium	N/A
WebSocket	Bi-directional, real-time	Medium	High	N/A

风格	适用场景	复杂度	灵活性	缓存支持
REST	CRUD操作、简单资源管理	低	中等	极佳
GraphQL	复杂数据获取、移动端应用	中等	高	手动配置
gRPC	内部服务、高性能场景	高	低	不适用
Webhooks	实时事件、异步流程	低	中等	不适用
WebSocket	双向通信、实时交互场景	中等	高	不适用

Anti-Patterns

反模式

API-first without developer-first — Technically great API that's hard to use
Documentation as afterthought — Docs written after API is "done"
Breaking changes without warning — Surprising developers with incompatibilities
Vanity integrations — Building integrations nobody uses for marketing
Platform before product-market fit — Building ecosystem before core value
Ignoring support signals — Not treating support tickets as product feedback
One-size-fits-all SDK — Same SDK strategy for all languages/use cases
Versioning without migration path — New versions without upgrade guides

API优先但非开发者优先——技术上优秀但难以使用的API
文档事后补全——API“完成”后才编写文档
无预警的破坏性变更——突然推出不兼容变更让开发者措手不及
虚荣集成——为营销目的构建无人使用的集成
未达成产品市场契合先做平台——在核心价值确立前就搭建生态系统
忽视支持信号——不将支持工单视为产品反馈
一刀切的SDK——对所有语言/用例采用相同的SDK策略
无迁移路径的版本控制——推出新版本却无升级指南