3 ms·
> You could do the same at scale with the right implementation of events. It's not worth the cost to roll your own. I use fullstory.com for web, and it's an i
by tomnipotent 8y ago
> You could do the same at scale with the right implementation of events.
It's not worth the cost to roll your own. I use fullstory.com for web, and it's an incredibly invaluable tool - next best thing to in-person user interviews. I'm able to see front-end errors in TrackJS/Sentry/NewRelic and find the matching session in FullStory to review with my team. With this tooling, there isn't a single issue/bug I haven't been able to re-produce and witness firsthand across any device/platform (like esoteric IE 11/Safari 10 issues).
- Fogest 8y agoI personally use TrackJS and find it quite useful. I never heard of Fullstory and it looks interesting. I see that they advertise showing JS errors as well similar to TrackJS. Is it not as good as TrackJS for this? I am curious why you need to use multiple if Fullstory gives that? I'm just looking at either replacing TrackJS with Fullstory, or keeping both if fullstory is helpful with TrackJS.
- tomnipotent 8y agoI still use TrackJS for primary error reporting, but FullStory happens to capture them as well and they show them inline with the viewing session in a mock console. It's a nice little feature and can be convenient.