The 0.5 Chronicles
Chapter 37 (2016): The API Economy / 第37章(2016):API 经济与平台化协作
More services stop standing alone and begin to exist as composable interfaces. / 越来越多的服务不再独立存在,而开始以可被调用、拼装与嵌套的接口形式出现。
English
2016 matters because digital services begin to operate less as isolated products and more as interoperable layers.
Earlier internet systems had already linked people, content, payments, and platforms. But in 2016, another organizing principle becomes stronger: many capabilities are no longer offered only through complete standalone products. They are increasingly exposed as interfaces that other systems can call, combine, and build upon.
This matters because it changes how software is imagined. A service no longer needs to own the full user journey in order to become economically meaningful. It can provide one capability—authentication, messaging, maps, storage, recognition, payment, recommendation, delivery, analytics—and survive as infrastructure for other services.
The significance of this shift lies in composition. Once more functions can be assembled through APIs, digital systems become easier to extend, faster to launch, and more deeply dependent on platform layers. Development turns from building everything from scratch toward orchestrating available components.
In China, as elsewhere, this logic matters because it accelerates the platformization of both technical and business life. Startups, enterprise systems, and consumer services can all move faster when core capabilities are rented, called, or embedded rather than fully rebuilt. But this speed comes with dependency. To build through interfaces is also to inherit the rules of the interfaces.
Historically, 2016 is important because it pushes software further into an era of modular dependence. Services become stackable. Coordination becomes programmable. Ecosystems gain power not only by attracting users, but by becoming indispensable layers in the products of others.
One-sentence summary:
The key to 2016 is that services increasingly become interfaces, and software development shifts toward composing platform capabilities rather than building every layer alone.
中文
2016 年的重要性,在于数字服务开始越来越少地作为彼此隔绝的完整产品存在,而越来越多地作为可以互相调用的层来运作。
更早的网络系统已经把人、内容、支付和平台连接起来了,但到了 2016 年,另一种组织原则变得更强:很多能力不再只通过完整独立产品来提供,而越来越多地以接口的形式暴露出来,供其他系统调用、拼接和继续构建。
这件事重要,因为它改变了软件的想象方式。一个服务不再必须拥有整条完整用户旅程,才能在经济上成立。它只需要提供一种能力——认证、消息、地图、存储、识别、支付、推荐、配送、分析——就可以作为别的服务的基础设施而存在。
这种变化的核心意义,在于“组合”。一旦越来越多功能可以通过 API 被调用,数字系统就更容易扩展、更快上线,也更深地依赖平台层。开发不再主要是从零搭建所有东西,而越来越像调度现成组件、拼装已有能力。
在中国,这种逻辑之所以重要,是因为它同时加速了技术生活和商业生活的平台化。创业公司、企业系统和消费服务,都可以因为“能力可租用、可嵌入、可调用”而大幅提速。但速度的另一面是依赖:你通过接口来构建,也就同时接受了接口的规则、边界和成本结构。
从历史上看,2016 年的重要性在于,它把软件进一步推向“模块化依赖”的时代。服务变得可堆叠,协作变得可编程,生态系统获得力量的方式,也不再只是吸引最终用户,而是成为别人产品里不可缺少的一层。
如果说 2015 年让 AI 在公共叙事里重新变得可信,那么 2016 年则写的是另一条同样关键的线:数字世界不只是变得更聪明,也变得更可拼装。平台不再只是流量入口,它还开始变成能力接口。软件世界从一个个孤立应用,进一步变成一个层层叠加、彼此依赖的系统网络。
一句话概括:
2016 年的关键,是服务越来越多地以接口形式存在,软件开发也因此从“独自搭完整产品”转向“组合平台能力来构建系统”。