A Network View of the History of WordPress

One of the key distinguishing features of digital technology is its generativity. Simply put, it is how the people do things that you as the original creator never thought about doing. Zittrain popularized the concept by analyzing the growth of PC and the Internet. In an ISR article that I wrote with Ola Henfridsson and Kalle Lyytinen, I proposed the notion of layered modular architecture as the technical underpinning of such generativity of digital platform ecosystems.

Despite its importance, there is not enough empirical research looking at the patterns of generative evolution of digital platform ecosystem. One such ecosystem is the platform that I am now using to write my blog. With the generous support from the National Science Foundation, my former student, Sungyong Um, and I have been looking at the evolution of WordPress since its inception in 2004. Sungyong has collected every plug-in written for WordPress and analyzed their source codes to find out which APIs they use. We found out that plug-in developers mix both APIs developed by WordPress and those by others (such as Google, Twitter, and Facebook). In January 2004, there were 86 plug-ins using 40 APIs by WordPress and 4 by others. A decade later (December 2014), there were 23,218 plug-ins using a pool of 443 APIs, only 99 of which were created by WordPress and the remaining 344 APIs coming from other large and small web service providers.

We characterized each plug-in as a combination of APIs, which allowed us to build a dynamic network of APIs to understand the generative evolution of the entire ecosystem. Below is an animation that shows the dynamic growth of WordPress. In the animation, blue dots are APIs built by WordPress. A line connecting two APIs indicates that those two APIs are being used to build a plug-in. If two APIs are repeatedly used, the lines become thicker. The animation is a bit jittery as the software changes the angle for different years.

The full manuscript is in the final stage (we hope) of the review process. What you will see from the animation is the important role that certain outside APIs play as the network grows over time. We are in the process of analyzing the history of the R ecosystem. I will share the results here soon.

Published January 7, 2019January 7, 2019

Originally published at youngjinyoo.com on January 7, 2019.




reflection on technology, design, and innovation in everyday experiences

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Youngjin Yoo

Youngjin Yoo

Professor @CaseWeatherhead @cwru Visiting Professor @LSE and @WBS #digital #innovation #organizationalgenetics #design

More from Medium

“…dark electronic music centered around deep minimal techno, ambient drones, and melancholic synth…

2022 Fonts Trend: What’s In Trend This Year?

Image of Azkasia Script Font.

How to setup iCloud email with your own domain while using Wix.

The Rule of Thumb for Creating Atomic Notes Without Stressing About “Atomicity”