Your Flexion Journey

Overview

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.

1. Existing Google Play Game
2. Build Flexion Variant
3. Integrate SDK
4. Configure Services
5. Test & Validate
6. Store Readiness
7. Launch
8. Operate

Step 1: Build Your Flexion Variant

The first step is to create a dedicated build variant for alternative app store distribution. This typically includes:

• Creating a separate package name
• Preparing a dedicated build configuration
• Removing dependencies on Google Play-specific services where required
• Preparing the project for Flexion SDK integration

At the end of this stage, you will have a dedicated Flexion Variant ready for implementation.

Step 2: Integrate the Flexion SDK

Once the Flexion Variant has been created, the Flexion SDK can be integrated into the project. This stage typically includes:

• SDK installation
• Purchase flow implementation
• Purchase validation
• Lifecycle handling
• Testing core platform functionality

At the end of this stage, the Flexion Variant should be technically functional and capable of running through the complete purchase flow.

Step 3: Configure Services

Some requirements are configured outside of the game build itself. Depending on your game's existing setup, this may include:

• Attribution configuration
• Social sign-in providers
• Push notifications
• Non-GMS device support
• Store account linking

The goal of this stage is to ensure all supporting services continue to function correctly across alternative app stores.

Step 4: Test & Validate

Before launch, the Flexion Variant should be thoroughly tested. This typically includes:

• Purchase testing
• Purchase validation testing
• Account and authentication testing
• Device compatibility testing
• Connected Test Mode verification
• End-to-end user journey testing

The objective is to confirm that the Flexion Variant behaves as expected across supported store environments.

Step 5: Store Readiness

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.

/The developer is typically responsible for

• Providing store assets and marketing materials
• Sharing game metadata and descriptions where required
• Reviewing store listings prior to launch

ⓘIn most casesThe assets supplied are the same assets already used for Google Play.

/Flexion is responsible for

• Reviewing store requirements
• Preparing store submissions
• Adapting assets where store-specific changes are required
• Managing compliance and approval processes
• Coordinating launch readiness across supported stores

Step 6: Launch

Once testing and store readiness activities are complete, Flexion will coordinate the launch process. This includes:

• Build submission
• Store publication
• Release coordination
• Launch validation

The goal is to ensure a smooth transition from testing into live distribution.

Step 7: Operate

Following launch, Flexion continues to support the title through ongoing store operations. This may include:

• Store management
• Update deployments
• Reporting and analytics
• Performance monitoring
• Store relationship management

This allows your team to focus on developing and operating the game while Flexion manages the complexities of alternative app store distribution.

Next Steps

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.