Flutter & React Native
Cheggout publishes native Android and iOS SDKs only. There is no Flutter package, no React Native module, and no published artifact, API surface or timeline for either.
Do not plan a launch around a cross-platform SDK. If it matters to your roadmap, raise it with Cheggout — publisher demand is what moves it up the list.
What works today on a cross-platform app
Two of the four surfaces are platform-agnostic and work regardless of what your app is built in.
Hosted experience — the fastest route
A Cheggout microsite opens in a web view, and every cross-platform framework has a web view.
| Framework | Web view |
|---|---|
| Flutter | webview_flutter or an in-app browser package |
| React Native | react-native-webview, or the platform's custom tab |
You build a launch button and a return handler. Nothing else.
Headless API — full control
The headless API is HTTP. Your backend does the authenticated calls and your app renders the results in your own Flutter or React Native widgets.
This gives you a genuinely native-feeling scratch card or rewards screen, built in your own framework, with no bridging at all — the only cost is that you build the UI.
| Module | Available headless |
|---|---|
| Scratch cards | Available Full flow |
| Coupons and deals | Available Full flow |
| Marketplace | Via hosted |
| Advertisement | Beta Standalone product not yet packaged |
For most cross-platform teams this is the right answer: headless for rewards on your own screens, hosted for the full marketplace.
Bridging to the native SDKs
If you specifically need the native SDK experience — the full marketplace rendered natively — you can bridge to it yourself.
| Framework | Mechanism |
|---|---|
| Flutter | MethodChannel to Kotlin and Swift |
| React Native | A native module on both platforms |
You would wrap the launch call and whichever methods you need — see Android methods and iOS methods.
Be clear-eyed about the cost. You are writing and maintaining platform code on both sides, you own the bridge when either SDK changes, and it is unsupported — Cheggout does not publish or maintain a bridge, so nothing about it is covered by their documentation. Only take this on if the native marketplace is essential and hosted is genuinely not acceptable.
Choosing
What Cheggout would need to publish
For this page to describe a real product:
- A published package — a pub.dev package or an npm module.
- A documented API surface, mapping to the native SDK capabilities.
- Version and platform support — minimum framework versions, supported architectures.
- Installation and initialisation guidance.
- Example integration covering launch, banners, stores and scratch cards.
- A support commitment — who fixes it when a framework version breaks it.
Tracked on Open items.
Next
- Headless API — the recommended route today.
- Hosted experience — the fastest route.
- Support — register your interest.