4 ms·
Heh, I've been waiting for this Show/HN/Launch, as I applied to the company a few months back via workatastartup, and it seemed to me like this would be an awes
by tough 5y ago
Heh, I've been waiting for this Show/HN/Launch, as I applied to the company a few months back via workatastartup, and it seemed to me like this would be an awesome product.
Looks very promising, wish the team the best!
Catch those errors before hitting prod, sounds like the dream
PS: As on open sourcing the record+replay code, I'm sure that'd be awesome, I only have this on my radar https://github.com/openreplay/openreplay https://github.com/openreplay/openreplay as a FOSS alternative to fullstory/logrocket for now.
- Gabriel_h 5y agoThank you for the wishes here! That is very kind of you. > Open sourcing Openreplay is awesome, but we ended up building heavily on top of rrweb (https://github.com/rrweb-io/rrweb https://github.com/rrweb-io/rrweb). Did you know they have their own documentary on the project? I only noticed that today.
- gary_chambers 5y agoBoth rrweb and OpenReplay are very solid projects. I've spent the last year or so building a session recording tool, and I've scrutinised their code quite heavily. Conceptually, session recording is quite simple, but there are so many edge cases, security models (CSP, feature policies) and performances issues to overcome. Performance is probably the area I've spent the most time thinking about: if you want to measure performance regressions in a page, instrumenting it with a session recorder is definitely a way to skew the results (for example, checking scroll position of elements during snapshotting will trigger a reflow).