What’s new in Liveblocks: May edition

This May, we made a number of changes to our website and documentation:

• Changelog: New weekly changelog on our website.
• Events: Learn more about your users and their activities.
• Better analytics: Improved insights into billing and usage.
• New onboarding: Start your project from within the dashboard.
• Improved API reference: New components and lots more information.

Changelog

We’ve introduced a new Changelog section to our website, where we’ll be posting detailed weekly updates on everything we’ve shipped in the past week.

We’ve already posted three weeks of changes, and we’ll sum up each month’s changelogs in a blog post, like this one.

Events

Events are now visible in the dashboard, giving you detailed information on your users, for example when they connect, and where they are. A number of filters are available, such as date range, event type, user ID, and more.

To find your events, open the dashboard, select a project, and click “Events” in the navigation menu.

Better analytics

We’ve added new analytics to the project overview page, giving better insights into active users and rooms, along with information on your product usage.

To the find the new analytics, open the dashboard and select a project.

New onboarding

We’ve created a new onboarding flow for new users, to help get everyone started more quickly.

As part of this improvement, we’ve also incorporated our quickstart section into the dashboard, meaning you can get started without leaving your project.

See confetti as soon as the project detects an initial WebSocket connection!

Improved API reference

We’ve completely rewritten the @liveblocks/client API reference page, filling it with a wealth of knowledge. We’ve also created new components for detailing arguments, and more, adding lots more information.

You might not know

Here’s some interesting @liveblocks/client features you may not be aware of:

• You can automatically disconnect users when they’re unfocused, and specify how long to wait before this occurs. They’ll reconnect on focus.
• You can convert a comment’s body into HTML and markdown, ideal for sending notifications about threads, or rendering comments manually.
• You can have your realtime application update up to 60 times per second by modifying the throttle rate.

More information

This post is a summary of May’s changes, make sure to read our Changelog to learn about every change we’ve made, no matter how minor.

Contributors

Contributors include:

7 authors