Thanks Austin! ✨ Great evening with the mobile community at the Mobile Engineering Summit: lightning talks, a panel on performance, reliability & AI, and the kind of energy that makes it worth doing again. Stay tuned for our next Summit in a city near you! 🙌

The Capture SDK is now running in 1B real-world environments! 🎉 Traditional observability tools send large volumes of data to centralized systems. Capture stores data on-device, giving mobile teams control over what gets sent and when. Read how we got here:

🎙️ New Beyond the Noise: our first two-guest episode. Lauren Darcey & Eric Kuck (Infinite Retry Labs, ex-Reddit) on mobile at scale: why your team is already on-call without knowing it, the systemic issues you only uncover at millions of users, and so much more: buff.ly/zCtX1uM

🎙️New episode of Beyond the Noise! Matt Klein brings on Kelsey Hightower. Kelsey talks through what AI is doing to developer salaries, what he tells junior engineers wondering if they picked the wrong field, and why open source is the only realistic check on what's being built today: buff.ly/VUD6ktX

Most mobile teams know when a critical flow is degrading. They just can't tell you why. bitdrift follows that journey on-device, without sampling, and surfaces the full context when something fails. Learn more about Critical User Journeys: blog.bitdrift.io/post/critica...

Most mobile teams log for the crash and stay blind to the jank. Frame drops and silent failures damage ratings quietly. We wrote about which UX signals to log, and how to measure them without wrapping your code in complex stopwatches or shipping a new release. Read more: buff.ly/dPYBxPt

Zuper went from stitching together crash and analytics tools to full on-device visibility across complex mobile workflows. With bitdrift, they now catch issues before they reach customers. Read the full case study:👇

The bitdrift team is hosting the Mobile Engineering Summit on March 26 in Austin! 📍 Join us for lightning talks, a Q&A panel with bitdrift CTO Matt Klein and Favor Delivery CTO Steve Romney, food and drinks, and the chance to connect with fellow mobile engineers. Save your spot now:

📣 Announcing wide availability of bitdrift's Bring Your Own Cloud (BYOC) for AWS! Enterprise teams can now choose from 3 deployment options depending on data ownership and compliance needs. 🔗 blog.bitdrift.io/post/announc... #MobileObservability

🎙️ New episode of Beyond the Noise! Chick-fil-A's volume doesn't just stress the kitchen it stresses the tech stack. Brian Chambers (Chief Architect) built the answer: Kubernetes inside of 3,500+ restaurants – one of the industry's largest edge computing deployments. 🎧 Listen now: buff.ly/WwGszFj

If you've built an Android app in the last decade, you've almost certainly shipped Jesse Wilson's code to your users. 🎙️Our newest Beyond the Noise episode with @swank.ca just dropped – tracing the open-source decisions that shaped modern Android! 🎧 Listen today:

Your app is 99% crash-free. Great… but are users happy? Slow checkouts, hanging searches, stuttering playback – p99 issues often invisible to dashboards but obvious in churn. 🔗 Check out our new post on the gap between crash-free rates and actual user experience:

Is OpenTelemetry the foundation for mobile observability? Not really. 🔍 OTel standardizes telemetry, but mobile has unique constraints. bitdrift stores telemetry on-device, retrieves only what matters, correlates with backend traces when investigation requires it. ⚡ blog.bitdrift.io/post/what-is...

🚩 New in bitdrift Capture: feature flag support! See which flags and variants were exposed when crashes occurred. Filter issues by experiment. Build workflows that match on specific feature flag states. Full details: blog.bitdrift.io/post/announc...

🎙️ New Beyond the Noise episode alert! Hear Gabriel Savit, Co-founder & CEO of Runway, on why mobile releases stay painfully manual, why checklists don’t fix release chaos, and a surprising “automation paradox". Listen here (or wherever you get your podcasts!) bitdrift.io/podcast/beyo...

A traditional mobile crash tool shows you how your app crashed. bitdrift: shows you why it crashed. Mobile crash reporting is free on bitdrift. Full context included: everything you need to track and debug crashes. Try it today! #MobileCrashReporting

🎙️New episode alert! Hear @tysmith.me, Principal Engineer at Uber, talk his career path, the coming validation/observability crunch, and the rise of AI-driven development. Check it out here, or wherever you get your podcasts👇 bitdrift.io/podcast/beyo...

🎙️ New Beyond the Noise ep! @smileykeith.bsky.social (“Bazel Keith"), talks Bazel, iOS tooling, and his journey from CocoaPods ➡️ Lyft ➡️ Modular. Catch war stories of compiler bugs, dealing w/large Swift codebases, plus, why Apple/Google don’t solve many DX problems 👀 bitdrift.io/podcast/beyo...

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