> For the complete documentation index, see [llms.txt](https://help.blings.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blings.io/guides/ecosystem-and-apps.md).

# Ecosystem and Apps

Blings has multiple product surfaces. The important first distinction is between the self-serve Blings app and the enterprise Platform and Studio workflow.

Use this guide to decide which app or tool owns the work in front of you.

## App Map

| Surface                     | What it is for                                                                                  | Use it when                                                                                                                                                       |
| --------------------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Blings app**              | The self-serve app covered by the main Help Center.                                             | You are creating template-based self-serve videos, managing simple projects, or following self-serve Help Center workflows.                                       |
| **Blings Platform**         | The enterprise operating workspace for MP5 projects.                                            | You need analytics, editable content, flow management, data schema, live controls, catalog, simulation, integration, player settings, form data, or optimization. |
| **Blings Studio**           | The enterprise visual editor for MP5 experiences.                                               | You need to inspect or change scenes, layers, timing, assets, connector behavior, data bindings, flow maps, previews, or publishing state.                        |
| **After Effects extension** | The creator workflow for converting motion design work into MP5 project material.               | A designer is building or updating animation in Adobe After Effects before sending compositions into Blings.                                                      |
| **SDK and API tools**       | Developer implementation surfaces for embedding, controlling, and personalizing the MP5 player. | A website, app, CRM, backend, or custom integration needs to pass data or handle events programmatically.                                                         |
| **CRM and marketing apps**  | External systems that deliver links, tokens, thumbnails, campaign messages, and viewer data.    | A campaign is delivered through tools such as Braze, Salesforce Marketing Cloud, HubSpot, Iterable, Klaviyo, AJO, Marketo, or another CRM.                        |

{% hint style="info" %}
The self-serve Blings app is not the same workflow as enterprise Platform and Studio. Enterprise Flow Map, Studio connector setup, SDK implementation, and Platform operations belong in the enterprise docs.
{% endhint %}

## How the Surfaces Work Together

{% stepper %}
{% step %}

### Start With the Project Goal

The team defines the audience, use case, delivery channel, data source, interaction model, and success metric.
{% endstep %}

{% step %}

### Build or Import the Creative

Designers can use After Effects and the Blings extension, then continue work in Studio. Studio is also where teams inspect scenes, timing, layers, connectors, data bindings, and flow behavior.
{% endstep %}

{% step %}

### Define the Data Contract

Studio and Platform share the project schema. Developers and CRM operators use the same field names when they pass viewer data into the experience.
{% endstep %}

{% step %}

### Operate and Validate in Platform

Platform manages simulation, delivery setup, editable content, player settings, form submissions, analytics, and optimization.
{% endstep %}

{% step %}

### Deliver Through the Right Channel

The project can be delivered with landing-page URLs, CRM links, dynamic thumbnails, spreadsheet flows, SDK embeds, or custom code.
{% endstep %}
{% endstepper %}

## Deep Dives

{% content-ref url="/pages/vcNIkVG2DBfI7SBBBS8G" %}
[Blings Platform](/apps/blings-platform.md)
{% endcontent-ref %}

{% content-ref url="/pages/HJLmxqx5Lda9OQtaCUVd" %}
[Blings Studio](/apps/blings-studio.md)
{% endcontent-ref %}

{% content-ref url="/pages/GnNBVYduIP95kZAUwmu7" %}
[Getting started](/role-guides/creator/exstension/getting-started.md)
{% endcontent-ref %}

{% content-ref url="/pages/oNeRtfOObG8V08dUeRby" %}
[Getting Started with Blings.io Dynamic Video SDK](/role-guides/developer/getting-started/getting-started-with-blings.io-dynamic-video-sdk.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.blings.io/guides/ecosystem-and-apps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.