Matt Klein

Announcing custom dashboards - bitdrift Blog Today we are extremely excited to announce support for fully custom exploration dashboards inside bitdrift Capture. Real-time dynamic mobile observability is an operational super power, and the abilit...

Super excited to ship fully custom dashboards in @bitdrift.io Capture. Real-time dynamic observability is also about operational agility. 🎉

blog.bitdrift.io/post/announc...

Announcing SLO alerting - bitdrift Blog Today we are extremely excited to announce support for Service Level Objective (SLO) alerts in Capture. SLO alerts are an industry best practice for operating reliable systems and they are now availab...

Very excited to announce SLO alerting within @bitdrift.io Capture. Because "mobile observability that doesn't suck" should also enable modern SRE best practices. Come and get it! 📈

blog.bitdrift.io/post/announc...

Friday treat: coming soon to @bitdrift.io Capture: fully custom dashboards! Because mobile observability can be both awesome and beautiful at the same time. Amazing, right? 🎉

Sorry I don't. :(

Announcing workflow timeout actions: observing silence - bitdrift Blog Today we are very excited to launch a small yet extremely powerful addition to the bitdrift Capture workflow engine: timeout actions. Timeout actions unlock an entirely new set of investigations that ...

Super excited to launch a small yet mighty addition to the @bitdrift.io Capture workflow engine: timeout actions. This feature allows you to observe things that do *not* happen, something that traditional observability tools simply cannot do. 🚀

blog.bitdrift.io/post/announc...

bitdrift - Because mobile observability shouldn't suck bitdrift Capture provides real-time views into mobile experiences, without breaking the bank

As part of our crash reporting launch we refreshed the @bitdrift.io website, and if I do say so myself, it looks amazing. "Because mobile observability shouldn't suck" pretty much says it all. Check it out!

bitdrift.io

If you are struggling to solve your non-crashing app issues with a legacy solution that was never built to scale to 100% of sessions, just the 0.01% of crashing sessions, Capture is a one-stop shop and has got you covered. Let's talk! 🚀

Starting today, Capture has you covered for ALL of your mobile obs needs, from the 0.01% of crashing sessions, to the 99.99% of sessions that are crash free but not converting due to app bugs, performance issues, and who knows what else.

Capture's lack of built-in crash reporting has meant that though customers love the product, it requires an additional solution to provide crash reporting capabilities. And let's be real, no one likes multiple tools.

Yet, up until recently, crash reporting *was* the lingua franca of mobile obs, even though in mature apps over 99.99% of sessions are crash free! This is because, frankly, mobile obs is ridiculously hard, and without local storage and real-time control I would argue impossible to do well.

When we launched Capture 1.5 years ago, we fundamentally changed mobile observability by coupling local storage with real-time control. As we like to say, get 1000x the data when you need it and none when you don't!

Announcing crash reporting: why have breadcrumbs when you can have the whole loaf? - bitdrift Blog Today we are immensely excited to announce the biggest addition to bitdrift Capture in the history of the product: first party crash reporting! At the risk of extreme hyperbole, we believe that the ad...

Today we are thrilled to launch built-in app crash reporting capabilities inside @bitdriftio Capture! 🚀 You can read more about it in the linked blog, but a short 🧵 on why this launch makes existing mobile observability tools obsolete. 🌶️

blog.bitdrift.io/post/announc...

This is an important reminder that the red/blue state maps that everyone likes to show are a ridiculous simplification of the people that live all throughout the US. Boise is a fantastic city. Come and visit!

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! 🚀

Spoke w @mattklein123.dev, Co-founder & CTO of @bitdrift.io, about how hard mobile observability is compared to server-side observability. We discuss privacy control's impact on data collection, the cultural divide between mobile & backend engineers, & @opentelemetry.io. redmonk.com/blog/2025/06...

The Apple payments decision: a turning point for mobile observability? - bitdrift Blog The recent court ruling against Apple that made the app store’s 27% commission on external payments illegal in the US has upended the mobile app industry. Nearly every application developer is moving ...

New from me. Will the Apple payments decision be the turning point for mobile observability? 💰 📈

blog.bitdrift.io/post/payment...

Announcing unique device tracking, multiple group by, and table charts - bitdrift Blog Today we are excited to announce several new charting features within bitdrift Capture: unique device tracking, dynamic grouping by more than one dimension, and a new table view that streamlines high ...

Very excited to announce some great new charting features in @bitdrift.io Capture including unique device tracking, multiple group by, and table charts. Blog link in the comments! 📈 📊

blog.bitdrift.io/post/announc...

Yes we use Figma and I believe React but I don't know a lot of the low level details on the FE side. @jacksonhardaker.bsky.social can provide more info!

This video shows some recent work on @bitdrift.io Capture to implement an adaptive sidebar which removes clutter when viewing data and when working on small screens. Observability tools can be both transformational AND eye catching. 😉

All too often beautiful UI is an afterthought in infrastructure tooling. This is a miscalculation as users of these tools are drawn to exceptional design just as much as users of consumer products.

Those days are long gone. 😂

The complexity and importance of metric backfill in mobile observability - bitdrift Blog One of Capture’s most powerful capabilities is the ability to create synthetic counter and histogram metrics from wide logs that never leave mobile devices. This allows mobile developers to log as muc...

New post from me on the complexity and importance of metric backfill in mobile observability. Backfill is typically an afterthought in traditional server-centric TSDBs, and it is anything but in the mobile world. Enjoy!

blog.bitdrift.io/post/mobile-...

Great post on Android internals. Check it out!

Also if you come back through Boise let me know!

I hope you are headed north. You are very close to even more glorious views. :)

Mobile tracing done right: introducing dynamic spans & waterfall view - bitdrift Blog Today we are excited to announce a major expansion of Capture’s ability to understand real user application performance: dynamic session spans and a waterfall view to visualize them. Capture gives dev...

Very, very excited to announce mobile tracing done right for @bitdrift.io Capture.

blog.bitdrift.io/post/introdu...

With this solution you will be able to capture sessions and performance tracing based on arbitrary matching criteria, and update that criteria in real-time, getting you the traces you need to iteratively debug performance issues all without a single code deploy. Can't wait to ship this! 🚀

As a result, "tail sampling" is still expensive, and the total trace duration is usually short. None of these downsides apply with @bitdrift.io Capture's real-time control and local storage. Sessions can be hours or days long, and the capture decision is based on dynamic state machine execution.

"Tail sampling" is more sophisticated and decides at the end of the trace whether to capture (based on observing an error or some other indicator). Without real-time control and local storage, this requires sending *all* data to some intermediate buffer where it can be held to make a decision.

Traditional tracing requires some type of sampling to control volume and cost. "Head sampling" is the simplest and just decides at the beginning of the trace whether to capture it or not. Thus sampling does not have any trace specific context.