How to use Liveblocks Presence with React
In this guide, we’ll be learning how to use Liveblocks Presence with React using
the hooks from the @liveblocks/react
package.
This guide uses TypeScript. Liveblocks can definitely be used without TypeScript. We believe typings are helpful to make collaborative apps more robust, but if you’d prefer to skip the TypeScript syntax, feel free to write your code in JavaScript.
Get other users in the room
Now that the provider is set up, we can start using the Liveblocks hooks. The
first we’ll add is useOthers
, a hook that provides us information about
which other users are connected to the room.
To show how many other users are in the room, import useOthers
into a
component and use it as below.
Great! We’re connected, and we already have information about the other users currently online.
Define initial presence
Most collaborative features rely on each user having their own temporary state, which is then shared with others. For example, in an app using multiplayer cursors, the location of each user’s cursor will be their state. In Liveblocks, we call this presence.
We can use presence to hold any object that we wish to share with others. An example would be the pixel coordinates of a user’s cursor:
To start using presence, let’s define a type named Presence
in
liveblocks.config.ts
.
Then, define an initialPresence
value on our RoomProvider
. We’ll set the
initial cursor to null
to represent a user whose cursor is currently
off-screen.
Update user presence
We can add the useUpdateMyPresence
hook to share this information in
realtime, and in this case, update the current user cursor position when
onPointerMove
is called. Next, import updateMyPresence
and call it with the
updated cursor coordinates whenever a pointer move event is detected.
We’re setting cursor
to null
when the user’s pointer leaves the element.
Get other users’ presence
To retrieve each user’s presence, and cursor locations, we can once again add
useOthers
. This time we’ll use a selector function to map through each
user’s presence, and grab their cursor property. If a cursor is set to null
, a
user is off-screen, so we’ll skip rendering it.
Presence isn’t only for multiplayer cursors, and can be helpful for a number of other use cases such as live avatar stacks and realtime form presence.