BetaFlox Documentation
Welcome to the official BetaFlox documentation. Whether you are a developer looking to meet Google Play's testing requirements or a tester looking to earn rewards, you'll find everything you need here.
For Developers
As an indie developer, launching an app on Google Play is fraught with challenges. BetaFlox is specifically designed to solve the two biggest developer pain points: Google Play's rigorous "closed testing" requirements and post-launch app discovery.
The 14-Day Testing Hurdle
Google Play requires developers to have their apps tested in a closed beta test by 12 real testers for 14 consecutive days before the app can be published to production.
Why is this so difficult? Without a tangible reward, friends and generic testers usually abandon the app after a few days and rarely provide constructive criticism. BetaFlox solves this by providing engaged testers bound by an incentivized structure.
Campaign Setup Workflow
1. Create Your Campaign
Start by creating a campaign in the BetaFlox dashboard for the specific application you need tested. Provide the app icon, app name, and exact package name accurately.
2. Draft Mode & IDs
Your campaign will remain in "draft mode" initially. The platform will automatically generate a unique Developer ID and Campaign ID for you.
3. Setup Google Play Closed Beta
Upload your app (with the integrated BetaFlox SDK) to the Google Play Console to create a closed beta test track. Crucially, you must add the BetaFlox Google Group email address to your testers list in the Play Console.
4. Publish
Once Google approves your closed beta release, return to the BetaFlox dashboard and click Publish Campaign. Our testers will immediately be notified and join the 14-day cycle.
The Growth Program Edge
Alternatively, joining the Growth Program gives you access to an expanded pool of testers, allowing your app to achieve 100 or 200 real app downloads.
More than just meeting the Google Play 14-day requirement, the higher user volume ensures genuine engagement for a month or more. This influx of engagement signals positive velocity to Google Play's discovery algorithm right out of the gate.
SDK Integration Guide
Configure Repository
In your application's settings.gradle.kts (or root build.gradle.kts), ensure JitPack is added to your dependency resolution management:
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
google()
mavenCentral()
maven { url = uri("https://jitpack.io") }
}
}JitPack Repository Line
maven { url = uri("https://jitpack.io") }Add Dependency
Add the dependency to your app module's build configuration:
dependencies {
implementation("com.github.BetaFlox-SDK:SDK:1.0.23")
}SDK Dependency Line
implementation("com.github.BetaFlox-SDK:SDK:1.0.23")Initialization
Initialize the SDK in your custom Application class. No manual lifecycle tracking required!
import com.betaflox.sdk.BetaFloxSDK
class InitApp : Application() {
override fun onCreate() {
super.onCreate()
BetaFloxSDK.initialize(
context = this,
apiKey = "YOUR_API_KEY",
campaignId = "YOUR_CAMPAIGN_ID"
)
}
}SDK Import
import com.betaflox.sdk.BetaFloxSDKSDK Initialization
BetaFloxSDK.initialize(
context = this,
apiKey = "YOUR_API_KEY",
campaignId = "YOUR_CAMPAIGN_ID"
)Manifest Merge Conflicts
If you encounter a manifest merge error (`Attribute application@appComponentFactory`), it means your project needs to migrate older support libraries to AndroidX using Jetifier.
Enable Jetifier in your gradle.properties:
android.useAndroidX=true
# Enable Jetifier to migrate 3rd party libraries
android.enableJetifier=trueAndroidX Setting
android.useAndroidX=trueJetifier Setting
android.enableJetifier=trueUnity SDK Integration
Welcome to the BetaFlox SDK integration guide for Unity! This tutorial will walk you through the process of adding the BetaFlox SDK to your Unity game or application.
Required: The minimum API Level is 24 for the Unity BetaFlox SDK to work without errors.
Import the SDK into Unity
- Open your project in the Unity Editor (2021.3 LTS or newer recommended).
- In the top menu, navigate to Assets > Import Package > Custom Package...
- Locate and select the downloaded
BetaFloxSDK.unitypackage. - The Import Unity Package window will appear. Leave all files selected and click Import.
This will add the BetaFlox folder to your Assets directory, containing the necessary C# wrappers, native plugins, and editor scripts.
Resolve Android Dependencies
The BetaFlox SDK relies on certain native Android libraries. To ensure these are correctly included in your build, use the External Dependency Manager for Unity (EDM4U):
- Go to Assets > External Dependency Manager > Android Resolver > Resolve.
- Wait for the resolution process to complete.
Initialize the BetaFlox SDK
You must initialize the SDK before using any of its features. The easiest way is using the built-in BetaFloxManager component.
- Create an empty GameObject in your first scene (e.g., name it
[BetaFlox]). - Add the BetaFloxManager component to it via Add Component → Scripts → BetaFloxManager.
- In the Inspector, fill in your Developer ID and Campaign ID from the BetaFlox Dashboard.
Alternatively, initialize it in code:
using BetaFlox;
var config = new BetaFloxConfig.Builder("YOUR_DEVELOPER_ID", "YOUR_CAMPAIGN_ID")
.SetLogLevel(BetaFloxLogLevel.Debug)
.Build();
BetaFloxSDK.Initialize(config);Test the Integration
- Build your project for Android (File > Build Settings > Android > Build and Run).
- Check the Unity logcat output for the success message:
BetaFlox SDK Initialized Successfully!
If initialization fails, ensure your Developer ID and Campaign ID are correct and that the device has internet access.
For Testers
As a BetaFlox Tester, you get paid to help fix applications. The process requires commitment and consistency.
The Commitment
You must test the application for at least 4 continuous minutes every single day for 14 consecutive days. Missing even one day instantly disqualifies you from the campaign.
Reward Structure
Earn 10 points for every day you complete the test. Furthermore, earn an extra 2 points for every helpful, constructive comment you submit to the developer.
Strict Rules & Anti-Fraud
We guarantee developers real, actionable feedback. Therefore, any attempt to farm rewards or automate testing will result in an immediate and permanent ban.
No VPNs or Proxies
Using a VPN to mask location, claim points across regions, or bypass daily limits falsifies data and violates our terms.
No Emulators
Apps must be tested on real mobile devices to provide real performance data. BlueStacks, Nox Player, etc. are strictly prohibited.
No Multiple Accounts
You are permitted one BetaFlox account per person and per device. Bot-netting alt accounts triggers immediate flagging.
No Auto-Clickers
Scripting gameplay or automating daily 4-minute sessions ruins test integrity. Our SDK detects machine-like interactions instantly.
No Spam Feedback
Providing gibberish, copy-pasting Play Store reviews, or giving single-word "good app" responses to get points will result in rejection.
The Golden Rule
Test exactly as a normal user would, provide genuine and actionable feedback, check in daily for 14 days, and you will thrive securely on BetaFlox.