Below is a list of frequently asked questions curated by us.

If you have a different question, contact us on info@mtribes.com or leave a message on the chat widget at the bottom of the page.

----------------------------------------------------------------------------------------------------------------------------

Q: What SDKs do you support?

A: Javascript, Native iOS and Android SDKs are currently available.

Our SDKs are built to be universal for their respective mobile and TV platforms on each tech stack. The iOS SDK will support tvOS, and the Android SDK will support Fire and Android TV.

We're working on a Roku SDK, and on several server-side SDKs including NodeJS (for customers building server-side rendered web apps).

Q: Do I need to update my app if I make changes in mtribes?

A: You do not need to update your app for day-to-day scheduling in mtribes. This is one of the platform's key advantages. Once your app is integrated with mtribes, schedulers can dynamically control and personalize Experiences without relying on developers.

You do need to update your app if you make changes to the Experience template, because the template in mtribes may become unsynchronized with your app. In this case, we suggest using the mtribes CLI to easily update and regenerate the code, and reintegrate it with your app.

Q: What happens if my app loses connectivity with the mtribes server?

A: mtribes has been developed with the end user experience in mind, even in times of connectivity issues. Experience fallbacks have been built into the generated code. The default Scenario on an Experience provides this fallback state.

If the default Scenario on an Experience is switched off, the Experience will not show as a fallback. If switched on, the Experience will display with the properties set within that default Scenario.

Did this answer your question?