The end-to-end onboarding process, from creating your Flexion Variant through to launch and ongoing operations.
The Flexion onboarding process is designed to take an existing Android game and prepare it for distribution across multiple alternative app stores through a single integration and managed service model.
While every game is different, most integrations follow the same high-level journey. This documentation is structured around that journey, guiding your team from initial implementation through to launch and ongoing operations.
The first step is to create a dedicated build variant for alternative app store distribution. This typically includes:
At the end of this stage, you will have a dedicated Flexion Variant ready for implementation.
Once the Flexion Variant has been created, the Flexion SDK can be integrated into the project. This stage typically includes:
At the end of this stage, the Flexion Variant should be technically functional and capable of running through the complete purchase flow.
Some requirements are configured outside of the game build itself. Depending on your game's existing setup, this may include:
The goal of this stage is to ensure all supporting services continue to function correctly across alternative app stores.
Before launch, the Flexion Variant should be thoroughly tested. This typically includes:
The objective is to confirm that the Flexion Variant behaves as expected across supported store environments.
Before launch, the game must be prepared for distribution across alternative app stores. Flexion manages the majority of the store readiness process on behalf of the developer, reducing the operational effort typically associated with launching across multiple stores.
ⓘ In most cases
The assets supplied are the same assets already used for Google Play.
Once testing and store readiness activities are complete, Flexion will coordinate the launch process. This includes:
The goal is to ensure a smooth transition from testing into live distribution.
Following launch, Flexion continues to support the title through ongoing store operations. This may include:
This allows your team to focus on developing and operating the game while Flexion manages the complexities of alternative app store distribution.
Now that you understand the overall onboarding process, continue to the Integration Overview page to learn more about the Flexion Variant, SDK architecture and implementation requirements.