Use Cases
One of the things that makes app marketplaces so powerful in so many different circumstances is that an app can be whatever you want it to be. As a marketplace owner, you can define what an app will mean within your ecosystem and how it will interact with your core product or platform.

Key Distinctions

From a practical perspective, we like to distinguish between use cases based on two criteria. This enables us to understand how apps will benefit the end user, what technical requirements the ecosystem will have, and what developers will need to create apps.

General vs specific

The first criterion is whether apps are general, like other standalone software, or specific to your core product or platform. Knowing this will help you decide how to best add apps to your marketplace and gauge what developers will need to create their own.
Example: Chrome Web Store
The app on the left is built specifically for Google Chrome, whereas the app on the right is a mobile app that has been ported to Google Chrome.

Superficial vs deep

The second criterion is how deeply apps will interact with your core product or platform. For example, will they just connect your product/platform to one piece of external data, or will they add significant new functionality? Knowing this will also help you gauge what developers will need to create their own apps, as well as where the value-add will be for end users.
"The point is: as a platform, it’s not enough to just technically enable other software companies to integrate with your software, as just another application that they swap limited data with over APIs. That’s table stakes today."
Scott Brinket ThinkGrowth, Full Article

App Types

Here are some of the most common app types:

Internal product features

Internal product features are internal features within your core product or platform that can only be activated through the app marketplace.

Web integrations

Web integrations are apps which connect your core product or platform to third-party software and systems, usually by means of one or more APIs.


Extensions, also known as add-ons, are pieces of functionality complementary to your core product or platform.

Downloadable files

Downloadable files are any files (e.g. executable files or templates) which can be downloaded onto the end user's computer or server. They're often used to extend offline systems.
Example: Microsoft Store

Web Plugins

Web plugins are small, complementary pieces of functionality to your core product or platform that usually exist within the browser.

Other Software

Other kinds of software that can be distributed through an app marketplace include:

App or Partner Listings

App marketplaces can also have listings that promote partners and their apps. In these cases, the call-to-action usually involves filling out a contact form or navigating to the partner's website. This is especially popular in highly regulated industries, where the cost of third party services is often much higher (e.g. 5-6 figures per year).
Last modified 10mo ago