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: the strict 12 testers closed testing requirement 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.

SDK Integration Guide

📦 Version 1.0.22

Configure Repository

In your application's settings.gradle.kts (or root build.gradle.kts), ensure JitPack is added to your dependency resolution management:

settings.gradle.kts

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
        maven { url = uri("https://jitpack.io") }
    }
}

Add Dependency

Add the dependency to your app module's build configuration:

build.gradle.kts (App Module)

dependencies {
    implementation("com.github.skihal43:BetaFlox-SDK:1.0.22")
}

Initialization

Initialize the SDK in your custom Application class. No manual lifecycle tracking required!

InitApp.kt

import com.betaflox.sdk.BetaFloxSDKclass InitApp : Application() {
    override fun onCreate() {
        super.onCreate()
        
        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:

gradle.properties

android.useAndroidX=true
# Enable Jetifier to migrate 3rd party libraries
android.enableJetifier=true

For Testers

As a BetaFlox Tester, you get paid to help fix applications. The process requires commitment and consistency.

14 Days

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.

Points

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.