Do you know what this teaser is? It's first party crash reporting support in @bitdrift.io Capture. Do you know what that means? Legacy mobile observability tools are about to be obsolete. So, so excited to ship this. Watch this space! ๐
Do you know what this teaser is? It's first party crash reporting support in @bitdrift.io Capture. Do you know what that means? Legacy mobile observability tools are about to be obsolete. So, so excited to ship this. Watch this space! ๐
That's right. We also use MUI as the underlying component library, xyflow for our workflow editor, and airbnb/visx for visual chart primitives .
Spicy Tuesday take from me:
blog.bitdrift.io/post/reality...
Early prototype of bitdrift Capture running in the browser, including session replay. This is our Rust core compiled to WASM and executed. Still a lot to do, but very promising.
Real-time dynamic observability coming to a browser near you. Get in touch if this sounds interesting. ๐
In that snippet the "ComparisonProvider.Treatment" context has access to the treatment tooltip position setter, and the control getter, while "ComparisonProvider.Control" has access to the control setter, and the treatment getter.
<ComparisonProvider> <ComparisonProvider.Treatment> <Chart range="7d-14d"/> </ComparisonProvider.Treatment> <ComparisonProvider.Control> <Chart range="now-7d"/> </ComparisonProvider.Control> </ComparisonProvider>
๐งต 4/4
End result looks something like:
๐งต 3/4
Problem 3: Expose the setter/getter to the relevant chart.
Solution: Add two variants of a nested context which exposes getter A / setter B, and getter B / setter A.
๐งต 2/4
Problem 2: Prevent changes in your new context propagating back to the chart component which dispatched the change.
Solution: Track the tooltip position for each chart separately, splitting the context to expose the setter/getter separately.
๐งต 1/4
Build a comparison view while reusing your existing chart component.
Problem 1: Sync tooltip position between two separate charts.
Solution: Wrap in a context to track the tooltip position (when it is displayed), reading the position back into the other chart.
#react
Real-time observability Tuesday: the best session replay for mobile is about to get a lot more exciting! Now take on-demand pixel screen shots based on workflow rules. Want to see exactly what the user is seeing when something specific happens? ๐