Choose the Integration Model

This documentation describes how to choose the right integratience level, and operate deployments across platforms.

When to Use the Branded Experience

Choose this model when you need:

• A fully managed Zing app with partner branding.
• No or minimal engineering work required.
• Rapid deployment in days instead of months.
• Automatic access to new features.
• A controlled set of customisations without maintaining code.

When to Use the Zing SDK

Choose this model when you need:

• Keep your users in your mobile app.
• Full ownership of the client experience.
• Control over the UI and the client experience.
• The ability to mix and match the SDK layers.

You need to have engineering resources and access to the codebase to implement the SDK and maintain the integration.

When to Use a White-label

Choose this model when you need:

• You don’t want to write or maintain any code. Zing ships, updates and operates the application on your behalf.
• You require extensive branding and feature-level customisation beyond what the SDK or branded experience can provide (navigation structure, flows, media libraries, coach personas, specialised content, region-specific logic, etc.).
• You want a product that feels 100% native to your ecosystem, with no visible connections to Zing.
• You prefer minimal operational overhead.

Bug fixes, platform updates, security, compliance and new feature releases are delivered by Zing, with optional partner approval gates where needed.