Integration Overview

Flexion enables developers to distribute their games across multiple alternative Android app stores through a single integration and managed service model.

Rather than supporting each store individually, developers create a dedicated Flexion Variant of their game and integrate the Flexion SDK. This allows the same build to be distributed across supported alternative app stores while maintaining the functionality required for each platform.

The goal is to minimise the engineering and operational effort traditionally associated with alternative store distribution.

‍

What Is a Flexion Variant?

A Flexion Variant is a dedicated version of your Android application that is distributed through alternative app stores. In most cases, the Flexion Variant:

• Uses a separate package name from the Google Play version
• Contains the Flexion SDK
• Uses Flexion purchase processing instead of Google Play Billing
• Supports devices and ecosystems that may not have access to Google Mobile Services (GMS)

The Flexion Variant exists alongside your existing Google Play build and is used exclusively for alternative app store distribution.

‍

What Does the Flexion SDK Do?

The Flexion SDK provides the platform functionality required to support alternative app store distribution. Key capabilities include:

• Purchase processing
• Purchase restoration
• Store entitlement management
• Flexion platform services
• Store-specific integrations
• Alternative app store compatibility

ⓘ Familiar by design

‍The SDK is designed to provide a familiar implementation experience for developers already using Google Play Billing or Unity IAP.

‍

What Changes Are Typically Required?

Every game is different, however most integrations involve changes in the following areas:

• Purchase flow implementation
• Purchase validation
• Package name configuration
• User authentication configuration
• Attribution setup
• Device compatibility testing

The exact requirements depend on the services and third-party SDKs currently used by the game.

‍

What Remains the Same?

While a dedicated Flexion Variant is required, the majority of the game remains unchanged. In most cases:

• Gameplay systems remain unchanged
• Backend services remain unchanged
• LiveOps processes remain unchanged
• Existing game content remains unchanged
• Existing analytics implementations remain unchanged

The integration effort is typically focused on platform services rather than game systems.

‍

Responsibilities

DeveloperFlexionCreating and maintaining the Flexion VariantAlternative store distributionIntegrating the Flexion SDKStore submissionsImplementing purchase flowsStore operationsSupporting testing and validationStore relationship managementProviding store assets and metadataLaunch coordination and ongoing store support

‍

Next Steps

Continue to Managed Service Overview to learn more about the services Flexion provides beyond the SDK integration.