There is some internal support of dynamic add events to the replayer. But to build a solid live-replay still need to handle things like reorder/retry/missing-tolerant and I'm not sure whether this should be implemented in rrweb.
@DecaK
I think you can check whether it's fit by answering the following questions.
Does your app need collaboration? If yes, rrweb is not suitable. Because of real-time collaboration needs some algorithm to solve the confliction of write which is not included in rrweb's design.
Does your app have some mechanism to describe the state of the app in a serializable format? If yes, it would be more efficient to send the state and rebuild a synced UI on the other side via it.
I would like to explain a little more on the second point since it's a common mystery.
For example, if you have a TODO app, then you can describe the state as
[
{ content: "todo A", finished: true },
{ content: "todo B", finished: false }
]Syncing this array allows you to rebuild a TODO app, and it could be more efficient when you implement some incremental state algorithm. But with rrweb, you will have a much larger state contains many DOM things and will be hard to optimize because it was very general.
Hi @grohsfabian_twitter
Is the situation of “100+ mb per user” actually happens? Or just an estimation based on the testing?
rrweb use an incremental op-log data structure, which contains a relative big full snapshot and many small incremental op-logs. As the time of recording increase, the size of events should increase slowly.
But there are also some ways to increase the size of events, such as:
- Disable the inline CSS option if you are sure the remote stylesheet will not change.
- Block some DOM which log many events, like animation elements.
- Use some compression algorithm like gzip to compress the data.
It would be helpful if you can share your events for a further analyze.
Hey there @Yuyz0112
After some more testing I see some more problems / things that can be improved and I hope I do not intrude when mentioning them:
- rrweb-player does auto play in some cases even though autoplay is false
- rrweb-player is not responsive ( not a big deal )
- Similar to @aaqibjavith I get those errors from time to time and I am sending the events to the database every few seconds + on click + on form submissions, I would have to check this more in depth to see when is happening more specifically
- The most annoying one is when trying to replay, the player with the iframe is making the browser show the "load" sign / animation infinitely in my case and you can see this happening on rrweb.io that after the page has been loaded fully, it still shows the loading icon and if you look on chrome, it shows "Waiting for github.io" and its coming from the iframe for the replayer
Hello,
I tried to install rrweb. I can record it and I can replay the events (no errors).
But the screen of the replay is just empty. The content of the homepage, where I recorded the events, is not showing.
My events look like this:{"type":3,"data":{"source":1,"positions":[{"x":984,"y":720,"id":528,"timeOffset":0}]},"timestamp":1571996501626}
{"type":3,"data":{"source":3,"id":1,"x":0,"y":1},"timestamp":1571996501626}
{"type":3,"data":{"source":0,"texts":[],"attributes":[],"removes":[{"parentId":457,"id":461}],"adds":[]},"timestamp":1571996501727}
{"type":3,"data":{"source":3,"id":1,"x":0,"y":300},"timestamp":1571996501727}
Since I'm having a lot of company works in this month, the development may start in weeks later. Any feedback/feature-requests are welcomed in the process.
