Integration & Build

The technical work required to prepare your game for distribution through Flexion's alternative app store network.

Overview

This section covers the technical work required to prepare your game for distribution through Flexion's alternative app store network.

The majority of integrations involve implementing the Flexion SDK, adapting the purchase flow, validating the implementation using Connected Test Mode, and preparing the game for Flexion validation.

Additional configuration requirements such as attribution, push notifications, social sign-in, deep linking and referral systems are covered separately and may only be required if your game currently uses those services.

Before You Begin

Before starting the integration, ensure you have access to:

  • Flexion SDK credentials
  • Flexion Portal (DropPoint)
  • Application Token
  • Connected Test Mode
  • A working Android build of your game
Missing something?

If you are missing any of the above, please contact your Flexion representative.

Developer Resources

/ Flexion Portal (DropPoint)

The Flexion Portal provides access to resources required throughout the integration process, including:

  • Application Tokens
  • SDK credentials
  • Connected Test Mode downloads
  • Build submissions
  • Release management tools
  • Reporting tools

/ SDK Credentials

CredentialPurposeApp TokenUniquely identifies your game within the Flexion platform; required during SDK configuration.Public KeyUsed as part of purchase validation when validating purchase data returned by the Flexion SDK.Personal Access TokenUsed to access the Flexion SDK repository when configuring project dependencies.Signing KeysGames distributed through Flexion are signed using Flexion certificates; hash keys are available in the Portal.

If your game uses services that rely on signing certificate fingerprints, such as social sign-in providers or anti-tampering solutions, the required signing hashes can be found within the Flexion Portal. If multiple signing certificates are required for your title, multiple hash key sets will be available.

/ Connected Test Mode

Connected Test Mode allows developers to test the Flexion SDK without requiring live store payment integrations. The Connected Test Mode application must be installed on test devices during development and testing.

Core Integration Journey

  1. SDK Installation
  2. SDK Initialization
  3. Flexion Screens
  4. Purchase Flow
  5. Purchase Validation
  6. Connected Test Mode Testing
  7. Additional Integrations (optional)
  8. Integration Completion Checklist
  9. Flexion Validation

The core SDK implementation is required for all games distributed through Flexion, while additional integrations are only required if your existing game already uses those services. Additional integrations include:

  • Attribution (AppsFlyer, Adjust, Singular)
  • Push Notifications
  • Social Sign-In
  • Deep Linking
  • Friend Referral Systems
  • Advertising SDK Configuration

Next Steps

Continue to Package Name Requirements to learn how to prepare your application for a Flexion package name and review any Android configuration changes that may be required.