Web & Mini Program development guide

Prerequisites and build selection

1. Create an application in the console and copy its App ID.
2. Download the matching floo-web or floo-uniapp release.
3. For voice & video, install the runtime dependencies used by the Web demo, including webrtc-adapter.
4. Choose one application-wide SDK instance; do not create a separate instance per view.

Register, sign in, restore, and sign out

im.userManage.asyncRegister(this.user).then(() => {
  console.log("注册成功");
}).catch(ex => {
  console.log(ex.message);
});

im.login({
  name, // 用户名
  password,
});

With autoLogin enabled, the SDK restores the previous session from local storage. In production, clear application-specific SDK state rather than unrelated origin storage, and coordinate sign-out with push-token unbinding on mobile containers.

const list = im.userManage.getConversationList();
console.log(list);

Groups and membership

Group work includes the group lifecycle, membership, roles, invitations, join requests, mute and block lists, announcements, shared files, and per-group notification settings. Load group details before rendering a chat so policy and permissions are current.

im.groupManage
  .asyncCreate({
    name,
    type, // 是否 pulbic， 0， 1
    avatar,
    description,
    user_list, // user ids
  })
  .then(() => {
    console.log("群创建成功");
  });

Send, forward, recall, and receive

im.sysManage.sendRosterMessage(message);
//or
im.sysManage.sendGroupMessage(message);

im.on({
  onRosterMessage: function(message) {
    console.log(message);
  }
});

im.on({
  onGroupMessage: function(message) {
    console.log(message);
  }
});

• Use onMessageStatusChanged to reconcile local pending messages with server state.
• Handle recall and deletion events by message ID and make each handler idempotent.
• Forward and recall through sysManage; enforce the server recall window in the UI.
• Persist message IDs and conversation IDs rather than relying on rendered-list indexes.

Voice & video lifecycle

主动发起音视频通话端
im.rtcManage.initRTCEngine(message);
//or 被动接受加入音视频通话端
im.rtcManage.joinRoom(message);

1. Register onRosterRTCMessage before sending or accepting an invitation.
2. Use sendRTCMessage for call signalling and the engine APIs for media state.
3. Publish local tracks only after room join succeeds; subscribe after remote sources arrive.
4. On every exit path, unpublish, unsubscribe, leave the room, destroy the engine, and remove listeners.