Our session replay isn't just regular session replay, it's *cool* session replay: buff.ly/x1lkvOw

What does bitdrift Capture's metrics architecture look like, you ask? Well, *you* specifically might not have asked, but now you can find out too! It looks like this: buff.ly/ZjVSkqD

Despite small improvements, the cost of observability is still astronomically high. Why? Because the fundamental origin of observability data has not changed. How did we arrive at this cost crisis? And what are we going to do about it? Here's our take ⬇️ buff.ly/R6K7PjD

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

New from me. Will the Apple payments decision be the turning point for mobile observability? 💰 📈 blog.bitdrift.io/post/payments-…

Do you know what this teaser is? It's first party crash reporting support in bitdrift 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! 🚀

We're back on the Nasdaq tower! bitdrift is on @redpoint’s 2025 #InfraRed100 list of the top infra startups! A huge thanks to the @redpoint panel, and most of all, to the bitdrift team. Full report: 🔗 buff.ly/OFIborH 📸 Times Square. 😎 #InfraRed100 #CloudInfra

Martin from bitdrift with a mind-blowing technique for reproducing full screen layouts with an extremely dense and efficient byte format. Super impressive stuff! 🤯 One More Thing Conference

The vast majority of user sessions in a mature mobile app don’t result in a crash. In fact, crashes make up just 0.01% to 0.1% of total sessions 🕵 When you rely on crash data alone, serious issues can easily slip through the cracks: buff.ly/FhyMeaL

🥖 Breadcrumbs are out. Full loaves are in. In other words: bitdrift now supports first-party crash reporting! Check it out here → buff.ly/vjJNlII

ICYMI: last week we announced our crash reporting beta (included for free with Capture) Check out a quick demo of what you'll find, and be sure to look out for some major product updates over the next few weeks ⚡ buff.ly/D9xDOr9

Another #hottaketuesday for you ➡️ most mobile observability solutions aren't actually built for mobile. The founding team at bitdrift knows this well. While they were at Lyft, they needed a mobile-specific solution, but nothing out there worked – so they built bitdrift.

Traditional tracing systems have extremely poor ROI given the cost required to overcome suboptimal sampling policies that make it difficult to find the right trace at the right time. 🔎 Read our approach to tracing here buff.ly/3glt5bH

Favor Deliver handles millions of orders across Texas, so when something goes wrong, they need to know what it is, fast. More on how they sped up their mobile observability with bitdrift 👇 buff.ly/uppQ0gJ

Super excited to launch a small yet mighty addition to the bitdrift 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/announcin…

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

bitdrift's real user monitoring (RUM) solution lets you see performance & behavior trends across your entire fleet. A few of the metrics you can see: app opens, app freezes, force quits, network failures, and disk usage. Explore more in the sandbox 👉 buff.ly/num45ke

Super excited to ship fully custom dashboards in bitdrift Capture. Real-time dynamic observability is also about operational agility. 🎉 blog.bitdrift.io/post/announcin…

Product overview: workflows. Use workflows to choose what data you ingest, and what to do with that data (all without learning a pesky new query language). In this example, we're recording sessions and plotting a chart on app open. Try it out here: buff.ly/num45ke

The case for No(more)QL: observability can be hard to adopt, and bespoke query languages don’t make it any easier. What would a future of NoQL observability look like? What problems would it solve? Check out the newest post here: buff.ly/9dP9oGA