There’s a specific moment in a piece of software’s life when it stops being a tool and starts being a platform. It isn’t a redesign or a feature launch — it’s the moment the vendor opens a door and lets someone else’s code walk through it: a plugin API, a scripting surface, a marketplace. Once that door exists, the software’s actual capability stops being bounded by what the vendor’s own roadmap decided to build, and starts being bounded by what its users are willing to write. The same pattern — extension surface, a marketplace or repository to distribute through, and a community that outpaces the original team’s roadmap — shows up across wildly different kinds of software. Here are seven.
Music software: Ableton Live’s Max for Live
Max for Live launched in 2009 as a joint project between Ableton and Cycling ‘74, the company behind the visual programming environment Max/MSP — shipping as an add-on to Live 8, initially for $29. The pitch was direct: instead of waiting for Ableton to build a specific device you wanted, build it yourself inside Max’s node-based patching environment and drop it straight into a Live set as a working instrument or effect. Ableton’s relationship with Cycling ‘74 eventually went further than a partnership — Ableton acquired the company outright in 2017, folding the plugin maker into the host it had spent eight years extending. It’s a useful data point on how seriously a platform owner can come to take its own extension ecosystem: eventually, owning it outright beats merely supporting it.
Data visualization: Tableau’s Extensions API
Tableau unveiled its Extensions API at its TC17 conference and shipped it with the 2018.2 release, letting dashboards embed genuinely interactive third-party functionality rather than static charts. An early example from partner Starschema, built during Tableau’s beta program, was an autorefresh extension that reads a native Tableau parameter to drive a countdown-based data refresh — a small utility, but exactly the kind of connective-tissue feature a plugin ecosystem tends to produce first: not a flashy new chart type, but a fix for a workflow gap the core product never addressed directly.
Business software: Salesforce’s AppExchange, Apex, and Flow
Salesforce built its extensibility story on three layers at once: Apex, a proprietary programming language for writing custom logic directly against Salesforce’s data model; Flow, a no-code automation builder for people who’d never write Apex at all; and the AppExchange, the marketplace where both kinds of work get packaged and sold. Third-party tracking puts the current AppExchange catalog at roughly 6,000 listed apps as of late 2025 — Salesforce doesn’t publish an official running count — spanning everything from sales-pipeline add-ons to full vertical-industry rebuilds of the CRM. The two-tier approach (a real programming language for developers, a visual builder for everyone else) is arguably Salesforce’s most-copied idea: most mature CRM and automation platforms now offer some version of the same split.
Note-taking into workflows: Notion and Joplin
Notion opened a public API beta in May 2021 with exactly three launch partners — Typeform, Zapier, and Automate.io — explicitly positioning the note-taking app as something that could receive data from other tools and trigger actions in them, turning a notes database into a lightweight workflow hub. By the time the API left beta in March 2022, Notion reported over 30,000 developers building against it. Joplin, the open-source note app, took a different but complementary route: a plugin API (stable since version 1.4) that lets contributors ship features like tabbed notes, an outline sidebar, or an inline math calculator directly into the open-source project’s own plugin repository — proof that an extension ecosystem doesn’t require a venture-funded platform team, just a stable API and a place to publish against it.
Game engines and modding: Minecraft’s Forge and Fabric
Minecraft’s mod loader ecosystem split into two major approaches: Forge, which arrived around November 2011 to resolve conflicts between early large-scale mods, and Fabric, a lighter, more modular toolchain launched in December 2018. The two now effectively coexist as parallel platforms serving different mod-development priorities — Forge carrying the larger historical back-catalog, Fabric generally quicker to support new Minecraft versions — and the modding repository CurseForge is reported to host well over 100,000 Minecraft projects. It’s the starkest example on this list of a plugin ecosystem outgrowing any single technical approach: there isn’t one modding platform for Minecraft, there are competing ones, each with its own community.
Design tools: Figma’s plugin system
Figma shipped its web-based API in March 2018 and followed with a full plugin system in 2019, launching with roughly 40 approved plugins after a beta testing period. Early community favorites tracked by Figma’s own year-in-review — a PDF exporter, a style-guide generator, bulk find-and-replace across text and layer names — were exactly the unglamorous workflow utilities a design team actually needs and a vendor rarely prioritizes building itself. The plugin API now supports read and write access across Figma’s editors, including its FigJam whiteboard product.
Browser extensions: the Chrome Web Store
The Chrome Web Store opened in December 2010 with roughly 8,500 extensions in its first year, crossing 10,000 around its first anniversary — modest numbers by today’s standard, but notable because the browser itself is arguably the most-extended piece of software most people use daily without thinking of it as a “platform” at all. By 2024, per Wikipedia’s tracking, the store hosted roughly 138,000 extensions and 33,000 themes. A web browser becoming a plugin platform is easy to take for granted precisely because it happened first, and most completely — nobody calls their ad blocker or password manager a “mod.”
The pattern underneath all seven
None of these ecosystems started as platforms. Ableton Live, Salesforce, Notion, Figma, Tableau, Minecraft, and Chrome were each, at launch, a tool that did one thing. What turned each into something bigger was the same structural decision, made at different points in each product’s life: open an extension surface, give it somewhere to be distributed, and then — critically — let the community’s priorities diverge from the vendor’s roadmap without trying to control that divergence too tightly. The tools that resisted that opening, or opened it too narrowly, tend to stay tools. The ones that didn’t became the platforms everything else on this list is still building on top of.
Related Reading
- Three Years of Max for Live — Ableton
- Tableau Extensions API — Official GitHub Repository
- State of AppExchange: Salesforce Apps Market 2025 — DEV Community
- Notion’s API: 2021 Release Notes
- Joplin Plugin API — Official Documentation
- Introducing: Figma’s Platform
- Chrome Web Store — Wikipedia
- Using AI to Create Open Source Versions of Commercial Software
- Ghidra and the Community That Grew Up Around the NSA’s Reverse-Engineering Tool