Android SDKs

HotMic provides two Android SDKs. Pick the one that matches how much UI you want from HotMic — both share the same authentication and stream model.

Android Player SDK

The drop-in player. Ships HotMicPlayer — a Fragment-based integration that gives you the full HotMic experience: HLS playback, chat, polls, tipping, guest call-in, and analytics. Customizable via themes and delegate interfaces. Use this if you want the fastest path to a working stream view inside your Android app.

Open the Player SDK →

Android Headless SDK

io.hotmic:sdk — pure Kotlin API client with no UI and no player. Targets JVM 17 (Android API 24+ with desugaring), so it also runs in Spring Boot, Ktor, or any Kotlin/JVM project. Gives you HotMicClient, a StreamSession with coroutine-based event handlers covering auth, the 3-second delta-poll loop, presence, chat, reactions, polls, and battle questions. You bring the player (ExoPlayer / Media3) and every screen.

Open the Headless SDK →

Which should I pick?

| | Player SDK | Headless SDK | |---|---|---| | Ships a player | Yes (Fragment) | No — bring your own ExoPlayer / Media3 | | Ships UI | Yes (chat, polls, tipping) | No — pure API | | Customizable look | Themes + delegate interfaces | Full control | | Anonymous viewers | Supported | Supported (default) | | Platform reach | Android (API 24+) | Android (API 24+) and any Kotlin/JVM 17 | | Best for | Standard Android app integration | Custom designs, multi-surface, server-side |