Liveblocks Storage and Yjs just got better.
• Support for larger documents, preventing out of memory crashes.
• Quicker initial load times, especially for sizable documents.
• Higher limits and lower overhead.
The best thing—you're upgraded already!
lblcks.io/mwR3hmy
Creating a multiplayer game on @v0 using @threejs and @liveblocks
Models/textures/tracks/environments/physics, everything is being created by v0.
The key part was asking v0 to create automation scripts to export logs/screenshots so it can iterate on its own.
@ctnicholasdev@liveblocks Thanks for all the help!
I've been looking through the liveblocks docs and the YouTube tutorials (they're a bit outdated, but they still work fine!), already gotten to work!
I'm creating docDuo, a basic site that allows multiple users to collaboratively create and edit documents in realtime.
Now the problem is, do I write the websocket logic on the backend by myself, or use the free tier of something like @liveblocks to speed up production?
Add commenting to your @ag_grid cells!
I've set up a demo & guide showing how to do this in 5 mins using new Liveblocks comments components. Add in our notification components, and you get a full in-app inbox, email notifications about missed comments, and more.
Learn more ↓
We've just released new React components!
Build a collaborative app with @liveblocks using customisable avatar stack, cursors, and commenting components. We've written a blog post that takes you through what they are, and how to use them.
Link ↓
@ctnicholasdev@liveblocks I think I'll go the simpler route for now with liveblocks' libraries, then tiptap for the text editor. I've seen that they integrate very nicely
Integrate presence and contextual commenting in 5 minutes.
We've released new React components, making it even quicker to build your collaborative app. Add realtime cursors, live avatars, and use new pinned comments in canvases or table libraries like @ag_grid.
Blog post ↓
If collaboration happens outside your product, you lose your most valuable data. Docs, notes, Slack threads.
@Rippling built a collaborative product so that 1:1 meeting content lives inside their platform.
Liveblocks powers their realtime collaboration.
lblcks.io/blog-rippling
Zod isn't the only option.
Our team uses decoders, built by the wonderful @nvie. We find it's:
• Easier to read, as it looks like TypeScript.
• Quicker to debug, with its human-readable error messages.
• Lighter to ship, with tree-shaking and smaller bundles.
Get it ↓