Post

Matt Klein
@mattklein123.dev

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...

blog.bitdrift.ioAnnouncing crash reporting: why have breadcrumbs when you can have the whole loaf? - bitdrift BlogToday 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...

1 repost3 likes

Matt Klein
@mattklein123.dev

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!

Matt Klein
@mattklein123.dev

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.

Matt Klein
@mattklein123.dev

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.

Matt Klein
@mattklein123.dev

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.