Documentation

Build chat for AI-native apps

SDK and API guides for chat, voice & video, and push.

Chat

One-to-one and group chat, conversations, relationships, history and reliable ordered delivery.

Voice & video

Cloud-native real-time media through one API, hosted or deployed privately.

Push notifications

Integrate the major mobile vendors once and manage credentials in one place.

A name you will meet in the SDK

Why does “floo” keep appearing?

If floo keeps turning up in package names, imports, and repositories, you have not wandered into a second product. It is the SDK's original codename—a nod to the Floo Network from the Wizarding World, where a pinch of powder turns a fireplace into a doorway.

The engineering metaphor is fitting: your app hands a message to the SDK, and floo carries it to the right person, group, or device. Today, names such as floo-web, floo-ios, and im.floo.floolib remain unchanged so existing integrations keep working. Treat them as SDK identifiers, not a separate service.

Quick start

Create an application once, then integrate each end. The same App ID works across every client and your backend.

References

API surface for each end, all built on the same XSYNC protocol core.

Platform support at a glance

iOS

9.0+

Android

4.1+

Web

IE10+, Chrome, Firefox, Safari

Desktop

Electron, x86_64

Linux

C++ on x86 / ARM / MIPS

Mini Programs

WeChat native and uni-app

Full compatibility table