SDK Demo is here as an example of how you can embed Appmixer into your product. As you already know, Appmixer is not an end-user product. Being seamlessly embedded into your platform, Appmixer becomes a natural part of your product without your end-users noticing.
The SDK Demo and especially its source code is very useful as an example of how to use the Appmixer JavaScript SDK to display e.g. the drag&drop workflow automation designer, connected accounts, flow manager, and logs in your product. Moreover, it shows you how you can associate your user management system with Appmixer virtual users.
Use SDK Demo to:
study the source code in order to understand how to embed Appmixer in your product using the Appmixer JavaScript SDK
preview what Appmixer looks like in your platform and, thus, reveal the experience your end-users have when interacting with Appmixer's interfaces.
Further in the Knowledge Base, you'll find out there are two SDK Demos:
Workflow automation helping you preview the interface in which you or your end-users build sophisticated flows from scratch.
Integration templates empowering your end-users with a simplistic way to integrate different apps.
Access both SDK Demos below.
As outlined in the previous section, Appmixer consists of three main interfaces: Appmixer Studio, Backoffice, and SDK Demo.
Appmixer Studio is the environment where the flow configuration happens, Besides flow creation, you can manage your connected accounts, troubleshoot errors, view insights and set up custom key-value data stores.
Backoffice, being the most technical part of Appmixer, serves similarly like an admin panel. Here, you can grant access to other users, manage access control lists, register third-party apps etc.
SDK Demo helps you preview what your end-users see and interact with. As you already know, Appmixer is an embedded (white-label) solution that lives inside your software. The SDK Demo serves as an inspiration for your developers on how they can use the Appmixer JavaScript SDK to embed Appmixer in your product.
Let's explore all the interfaces one by one.
Think of Backoffice as your admin panel. Our customers use it mainly to register third-party apps (using API keys), manage users, user scopes and their rights, and see all flows created in their Appmixer instance.
Use Backoffice to:
view high-level insights (monthly message volume and message size),
access all flows created in your Appmixer instance,
manage users, user scopes and their rights,
register third-party apps (Slack, Salesforce etc.).
Learn about the core features of the Appmixer Backoffice:
Appmixer Studio is the interface where the flow configuration happens. As you already know, this interface can be used to build flows for internal processes, integration templates that will be exposed to your less technical end-users via simple integration wizards, or can be embedded into your platform to empower your end-users to build sophisticated workflows.
Besides that, Appmixer Studio helps you connect and manage your accounts (connection to third-party apps), create, edit and manage Data storage, and access insights that help you control the performance of your flows.
Use Appmixer Studio to:
create and manage your flows and integration templates,
connect and manage your accounts (connections with third-party apps),
create, edit and manage data storage,
access insights (dashboard, logs) to find out how flows are performing.
We dedicated a whole section to Appmixer Studio features. Learn more about them by reading the section below.
Don't forget that Appmixer Studio is just one of the three Appmixer interfaces. Next, you will learn about the basics of Backoffice.
