We’re hosting a mobile engineering happy hour in SF next Tuesday, 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:

🚀 Crash Reporting is here… and it’s free. Stop chasing repro steps. See what actually happened before every crash. Signup: https://t.co/wNld80q4z3 Join on Product Hunt: https://t.co/DLuVsTTuiR #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 @mattklein123 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:

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.

🚨 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. https://t.co/z1a7WfB0WR

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 🔎 🐛

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:

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? 👀

Friends at @NSSpain, come say hi to us at the bitdrift booth! 👋

🚨 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: @bitdriftio 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! https://t.co/Acl2e810aa

Product overview: session timeline. Dive deep into any recorded session to understand exactly what went wrong and why. Scroll through logs, jump right to errors, investigate memory usage, battery, or jump into the session replay. Try it in the sandbox: https://t.co/9Y2JiAa1ld

Product overview: funnels. Plot data into funnels to understand how users are moving through your app. In this example, we've set up a workflow to track data at each stage of onboarding, and then displayed that data in a funnel. Try it yourself: https://t.co/9Y2JiAa1ld