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:
Yay new @bitdrift.io Beyond the Noise episode with @p-y.wtf. You will not want to miss this one!
We believe so strongly that real mobile observability is the future that we are now giving away crash reporting for free. Check out our blog post and also we would love an upvote on ProductHunt as well! 🎉 🚀
www.producthunt.com/products/bit...
Hi everyone! Today we are thrilled to launch or revamped free tier for @bitdrift.io. For too long crash reporting has been synonymous with mobile observability, which is unfortunate because 99.9% of sessions are crash free.
blog.bitdrift.io/post/announc...
Do they not match because there is no data or because the match conditions are wrong? Our live debugging experience removes that problem entirely. Check out the embedded video in the blog! 🚀
Today @bitdrift.io we are super duper excited to launch when of the coolest features we have ever released: workflow debugging. Our workflows (finite state machines sent dynamically to mobile devices) are extremely powerful but also hard to debug.
blog.bitdrift.io/post/announc...
Guess what? I started a podcast! I'm not going to lie: I like being a podcast host. 😂 Check out the first two episodes on your platform of choice and there is a lot more to come!
Boise no kings protest
Big turnout in Boise.
Not going to lie that I'm lazy and much less inclined to go to a protest than I was in my 20s, but the "I hate America" BS is getting me off my ass and then some. See you out there tomorrow!
Enter the workflow debugger. This is the culmination of a ton of work, tying together our various systems into a unified real-time debugging experience driven directly from the browser. Just watch the video. Your 🧠 will explode. Shipping shortly. 🚀
It is extremely frustrating to deploy a workflow only to have no matches due to a typo or not fully understanding the shape of logs that are actually generated on the device.
is the difficulty of understanding whether workflows (the finite state machines we send to clients) are actually going to match the expected event sequence once deployed.
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 ...
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...
Picturesque lake and mountain scenic shot.
It's been an absolutely epic summer here in Idaho. Sad that it's coming to a close but also starting to get excited for winter!
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...
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...
Friday treat: coming soon to @bitdrift.io Capture: fully custom dashboards! Because mobile observability can be both awesome and beautiful at the same time. Amazing, right? 🎉
Sorry I don't. :(
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...
As part of our crash reporting launch we refreshed the @bitdrift.io website, and if I do say so myself, it looks amazing. "Because mobile observability shouldn't suck" pretty much says it all. Check it out!
bitdrift.io
If you are struggling to solve your non-crashing app issues with a legacy solution that was never built to scale to 100% of sessions, just the 0.01% of crashing sessions, Capture is a one-stop shop and has got you covered. Let's talk! 🚀
Starting today, Capture has you covered for ALL of your mobile obs needs, from the 0.01% of crashing sessions, to the 99.99% of sessions that are crash free but not converting due to app bugs, performance issues, and who knows what else.
Capture's lack of built-in crash reporting has meant that though customers love the product, it requires an additional solution to provide crash reporting capabilities. And let's be real, no one likes multiple tools.
Yet, up until recently, crash reporting *was* the lingua franca of mobile obs, even though in mature apps over 99.99% of sessions are crash free! This is because, frankly, mobile obs is ridiculously hard, and without local storage and real-time control I would argue impossible to do well.
When we launched Capture 1.5 years ago, we fundamentally changed mobile observability by coupling local storage with real-time control. As we like to say, get 1000x the data when you need it and none when you don't!
Today we are thrilled to launch built-in app crash reporting capabilities inside @bitdriftio Capture! 🚀 You can read more about it in the linked blog, but a short 🧵 on why this launch makes existing mobile observability tools obsolete. 🌶️
blog.bitdrift.io/post/announc...
This is an important reminder that the red/blue state maps that everyone likes to show are a ridiculous simplification of the people that live all throughout the US. Boise is a fantastic city. Come and visit!
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...
