Overview
An overview of developer capabilities and where to find help
Monterosa / Interaction Cloud is a real-time engagement platform which supports creation of custom apps that power audience-facing Experiences. The platform also offers backend APIs for content automation and incorporating custom extensions.
We recommend you review Core Concepts and Platform Terminology first.
You can also review a list of APIs: Available APIs or dive straight into a use case:
Building Apps: how to build an app on the platform (Beta)
Embedding Apps: how to embed an app into your site or native app
Content Automation: how to automate the generation of content in the platform
Interaction SDK
The Monterosa / Interaction SDK has two core use cases:
The SDK can be used to embed an Experience into your web or native app. This provides loading and resizing capabilities which save you integration effort and make for a smoother user experience.
You can load any ready-made Experiences such as the ones available on The Store or those that have been developed specifically and made available in the platform.
Using the SDK to embed Experiences is not mandatory, you can also deploy Experiences using custom code to manage loading and sizing.
You can see a working example of an Experience embedded using the SDK here.
Building Apps (Beta)
The SDK has a powerful lower level purpose: helping you build apps using the platform. By leveraging the capabilities of of the Interaction Cloud, you save time and increase the performance of your end-product. There are also commercial benefits as you become part of the Monterosa eco-system.
To learn how to build your first JavaScript app, see DEVELOPER GUIDE
To review the core functions of the SDK, see Building Apps
Terminology
Understanding the terminology and concepts behind the platform is important before you start developing. In summary:
Your organisation can have multiple spaces. Inside each Space you can keep multiple Projects which are each associated with a different app or app version. You link a Project with an App by associating with an App Spec, the collection of JSON files describing your app. Within Studio, the various Fields within the App Spec will define what settings become available within App Settings. Once that app becomes configured for end users via a Project we then refer to it as an Experience.
App
An App is an application written in JavaScript, Swift or Kotlin, deployed into the platform. The App is an underlying model, including the core application and its App Spec, on which an Experience is made.
Experience
Experience is the fully configured App, including styling and content boilerplates that is ready to be used with real users.
Project
A Project is a working contained within Studio which is associated with an App. You can have two projects associated with the same app, but offering differing Experiences because you have configured them differently.
Element
An Element is the interactive content building block for example a poll or prediction, often referred to as an ‘atom’ of an App.
Space
Space holds multiple Projects. For example you may choose to have a Space per TV channel or a Space per territory.
Organisation
The organisation is the highest level parent of the platform. When you login to Studio you are logging into your Organisation as part of that company's subscription.
Field
Projects, Events and Elements each have an associated set of fields. These are key-value pairs where the set of keys available to customise and the type of data they'll contain is configured in the App Spec.
Studio
Studio is the Interaction Management System. It serves multiple functions including App Configuration, Live Content Management and Reporting.
Extensions
Extensions are backend plug-ins which run independently but interface with the platform via Studio UI and other inputs / outputs to the platform.
Last updated