bitdrift now supports issue triaging: - Assign issues directly - Set a status for any issue -Track which app version includes a fix Read more about how to go from detection ➝ fix, all without leaving bitdrift. #bitdrift #mobileobservability blog.bitdrift.io/post/announc...

🎙️ The newest episode of Beyond the Noise just dropped! Listen to @mattklein123.dev and @p-y.wtf chat about his journey from open source to Block, and why AI introducing so many new bugs may actually be a good thing for curious engineers 🪲 bitdrift.io/podcast/beyo...

We started with a simple idea: "Let’s prototype how bitdrift would work on godot". Normal teams would write a PRD. Maybe write a spec. We are not normal. We built a fully functional arcade cabinet. Here's the story: blog.bitdrift.io/post/introdu...

🎙️ New episode of Beyond the Noise just dropped! In this episode, Hemant Garg, VP of Engineering at DraftKings discusses working on the first Droid phone, his time at Evernote, JPMC, and now DraftKings, and more! Listen wherever you get your podcasts: open.spotify.com/episode/5QAb...

We’re hosting a mobile engineering happy hour in San Francisco next Tuesday, on the 11th. We'll be at Bar Darling, one of my favorite SF bars. We’d love for any folks local to SF to come join us for some food and drinks, talk mobile, and network a bit! Register here: luma.com/5mepetxx?tk=...

🚀 Crash Reporting is here… and it’s free. Stop chasing repro steps. See what actually happened before every crash. Signup: bitdrift.io/signup Join on Product Hunt: www.producthunt.com/products/bit... #mobiledev #crashreporting

Adding more telemetry to your app shouldn't require a re-deploy (and the long app store approval process that goes with it). With bitdrift, it doesn't 👇

It’s here! 🎙️ Beyond the Noise: Signals, Stories & Spicy Takes - our new podcast hosted by Matt Klein. Get the hottest takes from the people building the future of mobile. 1⃣ Lyft & bitdrift origins 2⃣ Instacart & the future of retail tech Listen now:

🚨 The third post in our hands-on series has dropped! In this post, we'll walk you through how to instrument a funnel in bitdrift. Follow along as we create a funnel for the Wikipedia iOS app to analyze user drop-off in the donation funnel.

We couldn’t agree more. Observability is essential...but legacy tools often bury teams in more noise, complexity, and bills. We’re here to change that.

What if you could spend less time chasing down hard-to-reproduce bugs and more time shipping features? We're happy to help teams like Bluesky Social do just that 🔎 🐛

As we work with more and more customers @bitdrift.io, one of the biggest usability problems that customers face that is inherent in real-time observability ...

What you don’t see can hurt you 👀 RUM is powerful, but sampling makes it way less effective. That's why we let you collect data without sampling (and without blowing up your budget) Read more here: blog.bitdrift.io/post/danger-...

Did you know that you can use bitdrift for crash reports? We designed our crash reporting tool alongside Capture. What does this mean for you? Well, instead of being limited to breadcrumbs, you get full context on every crash. Read more here 👇

Did you know that bitdrift comes with a ton of metrics out of the box, all of which you get just by integrating the bitdrift SDK? 👀

🚨 The second installment of our series on getting hands-on with bitdrift using the Wikipedia app is live! In this post, we'll show you how to simulate a memory leak & how to detect the symptoms before a crash happens. Check it out here👇

Learn how to take a production-grade app (The Official Wikipedia app for Android), and instrument it with the bitdrift SDK, including all of the existing network calls and custom logs. Check out the step-by-step guide here 👇

When did bitdrift first click for you?

bitdrift is 2 years old! 🎂 During that time, we've changed our hypothesis on what really matters in observability: The initial hypothesis: cost is what matters The new hypothesis: cost matters, but is a secondary concern More on what we've learned 👇

Workflows > a complex query language

It's time for No(more)QL! Why? 1. Queries don’t scale across teams 2. Queries create knowledge silos 3. Queries assume you know what to look for 4. Query languages create a barrier to entry. Read more in our post here 👇

New blog from me: @bitdrift.io recently turned 2 and I wrote a short retrospective of some of the things we have learned along the way. Check it out and let me know what you think! blog.bitdrift.io/post/bitdrif...

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

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/YwLMs6v

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

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

Favor Deliver handles millions of orders across Texas, so when something goes wrong, they need to know what it is, fast. Recently, we had the pleasure of sitting down with a few folks on their team to talk about how they approach mobile observability with bitdrift. Check it out 👉

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/8LdEW1f

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.

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 ⚡

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

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/IN3f48B

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. 😎 #bitdrift #InfraRed100 #CloudInfra

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

On Wednesday June 12 at 3:30 PM, Martín Conte from @bitdrift.io‬ will be giving a talk Behind the Screens at the One More Thing conference. You'll learn about observability and how you can explore in production what gets shown in your app! lu.ma/jhp3xzx6

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

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

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 ⬇️

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/kQxTR9T

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

Ever wondered how our Ring Buffer works? Read about the details here 👇 buff.ly/R0MT52q

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.

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

JankStats + bitdrift = 😍 Read our new post on the challenges of monitoring app responsiveness and how we tackled them by integrating JankStats: blog.bitdrift.io/post/jank-st...

Didn't expect to meet this legend at @deepdishswift.com Be sure to stop by the bitdrift booth today to meet another legend (spoiler alert, it's our CEO @pmorelli.bsky.social)

We're having an awesome time so far at @deepdishswift.com! Stop by our booth for stickers, flappy bird, and a chance to win some very cool prizes 😎 We promise we'll also tell you about how awesome bitdrift is while you're here 😉

ICYMI: last week we introduced dynamic spans and waterfall view to bitdrift! A first class tracing system + real-time dynamic control = devs getting the traces they need at an ROI that actually makes sense, w/o fighting overzealous sampling policies

Mobile observability is stuck in the past: 1. Continuously streaming data ➡️ unpredictable overages 2. Adding logs/telemetry requires waiting on an app release 3. Session replay tools are bandwidth-intensive and lack privacy controls What observability issues do you face?

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