M/IC is a combination of components working together to deliver interactive experiences. Load volumes, profiles and behaviours are different from one app to another and always require best practice and testing.
However, when correctly scaled up, the core connectivity via the EnMasse Mesh can handle well in excess of a million concurrent users, or several million unique users during a live event. The platform is regularly tested to these levels and beyond.
If other services are in use, such as Leaderboards, the developer must ensure that they have consulted with the Monterosa account manager and best practices have been adopted. For example spreading data submissions over time, avoiding all connected devices reading at exactly the same time. No service levels are guaranteed or implied for unapproved applications.
The processing time to count all votes or interactions is affected by the type of vote, the frequency of votes or whether the vote is "signed". For an assessment of an application please contact firstname.lastname@example.org.
M/IC v23 Europe is hosted within the Amazon Web Services data centre in Dublin, within the EU. Other versions of M/IC are sometimes deployed in the US and other locations.
Scaling is described in the scaling page.
M/IC Studio is made for modern desktop browsers. It is not designed to work on mobile, although some functions will work on mobile.
>= Windows 10
M/IC does not yet support simultaneous users in the same event. Please avoid this scenario.
Each client app connecting to the M/IC Platform is allocated a unique ID. This ID is then stored in local storage on the client device and used to identify this user next time a connection to M/IC Platform is made.
The total number of different IDs connected to M/IC Event is displayed within M/IC Studio Timeline and Analytics pages as Unique Users.
Session length - this is the duration between client app connecting and disconnecting to/from M/IC platform in the context of an M/IC event. For more information see Analytics.
Average session length - this is the combined duration of all event sessions divided by the number of unique event users