Agora.io RTM是否支持打字状态？聊天应用动效实现方案咨询

Great question! Let's walk through each part of your inquiry clearly:

1. Does Agora RTM have a built-in "on typing" event? #

Nope, Agora RTM doesn’t provide a native typing indicator event out of the box. You won’t find this mentioned in their official docs because it’s not a pre-built feature—you’ll need to implement it yourself using the tools they do offer.

2. Can I send custom events with Agora RTM? #

Absolutely! Agora RTM allows you to send custom peer-to-peer or channel messages, which is perfect for building typing indicators. You can structure your own message payload to signal when a user starts or stops typing.

Here’s a quick example of how to do this in JavaScript:

Sending Typing Status (Sender Side) #

// Assume your Agora RTM client is already initialized
const rtmClient = createAgoraRtmClient({ mode: "rtc" });

// Send "typing start" signal to a specific peer
async function sendTypingStart(peerId) {
  const customMessage = {
    type: "typing_indicator",
    status: "start"
  };
  await rtmClient.sendMessageToPeer(
    { text: JSON.stringify(customMessage) },
    peerId
  );
}

// Send "typing end" signal to a specific peer
async function sendTypingEnd(peerId) {
  const customMessage = {
    type: "typing_indicator",
    status: "end"
  };
  await rtmClient.sendMessageToPeer(
    { text: JSON.stringify(customMessage) },
    peerId
  );
}

Receiving Typing Status (Receiver Side) #

// Listen for incoming peer messages
rtmClient.on("MessageFromPeer", (message, peerId) => {
  try {
    const parsedMsg = JSON.parse(message.text);
    if (parsedMsg.type === "typing_indicator") {
      if (parsedMsg.status === "start") {
        // Show your "on typing" animation for this peer
        showTypingAnimation(peerId);
      } else {
        // Hide the animation when they stop typing
        hideTypingAnimation(peerId);
      }
    }
  } catch (err) {
    console.error("Failed to parse custom message:", err);
  }
});

Pro tip: Add a debounce function to avoid spamming messages as the user types. Wait 1 second after the user stops typing before sending the "end" signal—this cuts down on unnecessary network traffic:

let typingDebounceTimer;

function handleUserInput(peerId) {
  // Send start signal immediately
  sendTypingStart(peerId);
  
  // Clear existing timer
  clearTimeout(typingDebounceTimer);
  
  // Set timer to send end signal after 1 second of inactivity
  typingDebounceTimer = setTimeout(() => {
    sendTypingEnd(peerId);
  }, 1000);
}

3. Can I use Socket.io instead? Is it efficient? Do I need to rebuild my chat system? #

You absolutely can use Socket.io for typing indicators, and it’s a solid choice—Socket.io is lightweight, low-latency, and perfect for real-time state updates like this.

The best part? You don’t need to rebuild your entire chat system! Keep using Agora RTM for core chat functionality (message delivery, presence tracking, channel management) and use Socket.io only for the typing indicator feature. This way, you leverage Agora’s strengths for chat while adding the typing feature with minimal extra work.

In terms of efficiency, Socket.io uses WebSockets under the hood (with fallbacks for older browsers), so it’s just as efficient as Agora RTM for these small status messages. You won’t notice any significant performance difference.

Final Recommendation #

Stick with Agora RTM for your core chat system and implement the typing indicator using Agora’s custom messages—it’s the most straightforward approach that keeps your stack consistent. If you already have Socket.io set up for other features, using it for typing indicators is also fine, but there’s no need to switch entirely.

内容的提问来源于stack exchange，提问作者Istiyak Tailor