bitdrift
bitdrift.io
bitdrift
@bitdrift.io
The future of observability: https://bitdrift.io
🎙️ 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...
From Droid Days to DraftKings: Hemant Garg on Velocity with Guardrails
open.spotify.com
November 10, 2025 at 6:09 PM
Reposted by bitdrift
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=...
Telemetry on Tap: Mobile Engineering Happy Hour | hosted by bitdrift · Luma
You're invited to join the bitdrift team for an evening of food, drinks, and good conversation with other mobile devs! This event is invite-only. RSVP to…
luma.com
November 7, 2025 at 5:25 PM
🚀 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
bitdrift - sign up
Your mobile application deserves a great observability solution. See every edge case, crash, and slow screen without waiting for another release.
bitdrift.io
October 28, 2025 at 3:09 PM
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 👇
October 24, 2025 at 11:06 PM
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:
Beyond the Noise: Signals, Stories, and Spicy Takes
Podcast · bitdrift · Hosted by Matt Klein, creator of Envoy and co-founder of bitdrift, Beyond the Noise goes inside the minds of the engineers, founders, and technical leaders defining the next era…
open.spotify.com
October 21, 2025 at 1:12 PM
🚨 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.
Funnel cake: sweet insights with bitdrift funnels - bitdrift Blog
Learn how to instrument a bitdrift funnel in the Wikipedia iOS app and analyze user drop-off in the donation flow in this hands-on guide.
blog.bitdrift.io
October 20, 2025 at 8:33 PM
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.
October 17, 2025 at 11:06 PM
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 🔎 🐛
October 10, 2025 at 11:06 PM
Reposted by bitdrift
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 ...
October 2, 2025 at 12:19 AM
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-...
The danger of sampled RUM data: what you don’t see can hurt you - bitdrift Blog
Sampling real-user monitoring (RUM) data can mask issues, skew metrics, and hurt debugging. Explore sampling pitfalls, mitigation strategies, and how bitdrift provides a better full-coverage…
buff.ly
September 30, 2025 at 10:45 PM
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 👇
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…
blog.bitdrift.io
September 22, 2025 at 8:33 PM
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? 👀
September 19, 2025 at 11:06 PM
🚨 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👇
Crashes are loud. Leaks are quiet. - bitdrift Blog
Welcome to the second post in our bitdrift hands-on series! In today’s post, we’ll be talking about memory leaks; those insidious issues that don’t always crash your app, but can make for a janky…
buff.ly
September 16, 2025 at 10:45 PM
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 👇
Instrumenting bitdrift in the Wikipedia app: A step-by-step guide for Android Devs - bitdrift Blog
Welcome to the first post in our bitdrift hands-on series!
blog.bitdrift.io
September 15, 2025 at 8:33 PM
When did bitdrift first click for you?
September 9, 2025 at 10:45 PM
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 👇
bitdrift turns 2: a retrospective - bitdrift Blog
Recently, bitdrift turned 2! It’s hard to believe that only 2 years have gone by. Startup years are odd; sometimes it feels like it’s been only 6 months. Other times it feels like it’s been 10 years!…
blog.bitdrift.io
September 8, 2025 at 8:33 PM
Workflows > a complex query language
September 6, 2025 at 12:13 PM
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 👇
No(more)QL - bitdrift Blog
Observability can be hard to adopt—and bespoke query languages don’t make it any easier. This post explores the hidden cost of relying on complex syntax and how bitdrift’s NoQL approach helps teams…
buff.ly
September 5, 2025 at 11:06 PM
Reposted by bitdrift
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...
bitdrift turns 2: a retrospective - bitdrift Blog
Recently, bitdrift turned 2! It’s hard to believe that only 2 years have gone by. Startup years are odd; sometimes it feels like it’s been only 6 months. Other times it feels like it’s been 10 years! ...
blog.bitdrift.io
August 18, 2025 at 3:15 PM
Reposted by bitdrift
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 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...
blog.bitdrift.io
July 28, 2025 at 3:03 PM
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
July 28, 2025 at 9:12 AM
Reposted by bitdrift
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...
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...
blog.bitdrift.io
July 21, 2025 at 3:01 PM
Reposted by bitdrift
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...
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 ...
blog.bitdrift.io
July 9, 2025 at 8:31 PM
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 👉
Favor Delivery Case Study - bitdrift
How Favor Delivery transformed mobile observability with bitdrift
buff.ly
July 9, 2025 at 4:59 PM
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
July 8, 2025 at 3:19 PM