Camera-first setup
Discover and connect to supported camera workflows, keep source intent explicit, and keep user permission requirements visible before activation.
Creator-first camera workflow
PocketRoar for mobile livestream creators
PocketRoar helps creators move from camera discovery to broadcaster setup using one mobile flow. The app focuses on reliable handoff for camera-first creators and clear provider authorization in beta.
- Built for DJI Pocket creators
- Android + iOS beta deployment flow
- OAuth fallback pages hosted with web-app links
What PocketRoar does
PocketRoar is an experimental mobile workflow for creators who want their camera as the center of the stream. It supports discovery and control for compatible DJI Pocket devices, exposes explicit capability-driven setup paths, and integrates provider tokens through the callback host at pocketroar.com/oauth/kick/callback and pocketroar.com/oauth/twitch/callback.
Provider handoff
OAuth returns through secure callback paths owned by this domain. Verified app-link files are included to support Android App Links and iOS Universal Links where identifiers are configured.
Transparent beta status
Unsupported claims are excluded from the landing promise. Features outside current proof are labeled as experimental and scoped to beta only.
How it works
- 1) Download and open PocketRoar Use the Android/iOS beta builds tied to this domain and callback configuration.
- 2) Connect a compatible camera session Run discovery, authorize access, and prepare your creator workflow.
- 3) Authorize and start streaming path Complete OAuth for your selected destination and return to the app through secure callbacks.
Supported workflow features
-
Cross-platform app experience
iOS and Android flows share callback and identity configuration through Cloudflare-hosted files.
-
Controlled OAuth routing
Callback handling is centralized on api.pocketroar.com and pocketroar.com paths.
-
Kick integration path
Kick is supported through the same secure fallback-first callback flow where users can retry from within the app if link handoff fails.
-
Camera workflow grounding
The landing copy and support references are aligned to current documented proof and avoid production guarantees until verification is complete.
Trust and security
- No tokens are echoed in callback pages.
- No secrets are committed in versioned files.
- OAuth callback pages are static fallback surfaces only.
- Worker secrets and production signing are held in Cloudflare environment secrets and separate from repository files.
FAQ
Is this production-ready?
No. This is a beta deployment route with explicit support boundaries. We publish current behavior, not broad claims.
Do I need an app store download?
Android and iOS beta builds are deployed through platform-specific channels tied to their build profiles.
Can OAuth run without app links?
Yes, via callback fallback pages; app-link files improve the direct handoff experience when identifiers and certificates are configured.