How the Flyy SDK works
The Flyy SDK puts rewards, referrals, scratch cards, spin wheels, leaderboards, quizzes and games inside your app. You integrate it once. After that, what users see — which campaigns run, where they appear, how they look — is set from the Flyy dashboard, not your code.
The pieces
| Piece | What it does |
|---|---|
| Native SDK | A small Kotlin or Swift library. It handles identity, events, push, referral attribution, and hosts the rewards UI in a WebView. |
| Rewards UI | Every Flyy screen — offers, wallet, scratch cards, spin wheel, quiz, games — is one web build. It ships inside the SDK and updates over the air. |
| Flyy API | Decides rewards, holds wallets and pays out. Your events go here. |
| Dashboard | Where you create campaigns, segments, placements and floating widgets. |
What that means for you
- No UI to build. Open a screen with one line, or embed a widget in your own layout.
- UI fixes without an app release. New rewards UI builds reach users over the air (OTA).
- It looks like your app. The SDK reads your app's colors, fonts, corner radius and dark mode and applies them (theming).
- Changes without code. Placements (stories, banners, tooltips, sheets) and floating widgets are set from the dashboard and reach running apps by push.
- v1 code keeps compiling. Every legacy Android and iOS method still exists under its old name (migration).
Platforms
| Platform | Package | Min OS |
|---|---|---|
| Android (Kotlin / Java) | com.theflyy:flyy:2.1.0 | Android 5.0 (API 21) |
| Jetpack Compose | com.theflyy:flyy-compose:2.1.0 | Android 5.0 (API 21) |
| iOS (Swift / Obj-C) | FlyyFramework 3.0.0 (CocoaPods) | iOS 14 |
| Flutter / React Native | Existing Flyy plugins, on the v2 native SDKs | — |
Ready? Start with the quick start.