Client library
Realtime Android (Kotlin) with WebSockets Native Android apps in Kotlin or Java.
Sign in to see these snippets with your own cluster host. Sign in
Using an AI coding agent? Copy the agent prompt ↓
Install implementation("com.pusher:pusher-java-client:2.4.4" )Subscribe to a channel val options = PusherOptions()
.setHost("ws.hibira.io" )
.setWsPort(443 )
.setWssPort(443 )
.setUseTLS(true )
val pusher = Pusher("YOUR_APP_KEY" , options)
pusher.connect()
pusher.subscribe("orders" ).bind("order-shipped" ) { event ->
Log.d("orders" , event.data )
}Agent prompt Paste this into Claude Code, Cursor, GitHub Copilot or another AI coding agent, and it will wire Hibira into your Android (Kotlin) project with the settings above.
Integrate Hibira realtime messaging into this Android (Kotlin) project. Hibira is a hosted WebSocket service that speaks the Pusher Channels protocol, so it works with the standard Pusher libraries (here: pusher-java-client, https://github.com/pusher/pusher-websocket-java) pointed at Hibira instead of pusher.com.
Connection details:
- Host: ws.hibira.io
- Port: 443
- TLS: yes (https)
- App key: YOUR_APP_KEY
- No app secret: it belongs on the server, never in this app
What to do:
1. Look at the project first (framework version, package manager, config and env conventions, where similar integrations live) and follow what it already does.
2. Add the dependency in the app module's build.gradle(.kts) and make sure the INTERNET permission is in AndroidManifest.xml.
3. Put the key and host in BuildConfig fields or resources, and keep one Pusher instance for the app (for example in the Application class or a DI singleton).
4. Event callbacks run on a background thread; switch to the main thread before touching the UI, and tie connect/disconnect to the app lifecycle.
5. If the app needs private or presence channels, set an HttpChannelAuthorizer pointing at the backend's auth endpoint; the app secret must never be in the Android app.
6. Read the credentials and host from environment variables or the project's config, and add placeholder entries to .env.example (or its equivalent). Never commit real values.
7. Always pass the host, port and TLS setting above. The library defaults to pusher.com; where it requires a cluster, use "ap" (the host decides where it connects).
8. If YOUR_APP_KEY above is still a placeholder, keep it as an env placeholder and tell me where to fill it in rather than inventing a value.
9. When you are done, list the files you changed and tell me how to check it works, for example by publishing a test event and watching it arrive.
Reference setup from the Hibira Android (Kotlin) guide (adapt it to the project's structure):
Install:
```kotlin
implementation("com.pusher:pusher-java-client:2.4.4")
```
Subscribe to a channel:
```kotlin
val options = PusherOptions()
.setHost("ws.hibira.io")
.setWsPort(443)
.setWssPort(443)
.setUseTLS(true)
val pusher = Pusher("YOUR_APP_KEY", options)
pusher.connect()
pusher.subscribe("orders").bind("order-shipped") { event ->
Log.d("orders", event.data)
}
```
Replace YOUR_APP_KEY and the other placeholders with the values from your dashboard, or let the agent leave them as environment variables for you to fill in.
Or connect the Hibira MCP server, and your agent can create the app and fill in its credentials itself. Connect your AI coding agent →
Use the app key and secret from your dashboard. Channels, events and authorization endpoints work exactly as they do with Pusher. Library reference ↗
