What’s New at Bugfender?
Welcome to the Bugfender summer newsletter. Over the past few months you may noticed a few improvements to Bugfender’s web app, if not, we’ve summarised them here and you should go and check them out.
- We’ve added a new dashboard, with improved metrics for each application, these include active devices, crashes, issues and user feedback.
- We’ve also added an alert to the dashboard for new SDK versions, so you can always stay up to date.
- And finally we’ve added more log levels, to give you better control of the logs displayed (e.g. trace, debug, info, warning, error, fatal etc)
How to Gather Data for Machine Learning
The machine learning algorithm, which solves problems without requiring detailed instructions, is one of the most exciting technologies on the planet. Since I began writing this post, Facebook and Microsoft have announced major additions to their own machine learning programmes.
But machine learning is deeply misunderstood – and not just by those who think it’s the dawn of a terrifying rise of the robots. In this article we’re going to demystify the concept, by cutting right to its core: the way we gather data for our machine learning algorithm, following a clearly defined process.
Firebase Crashlytics and Bugfender: a Step-by-Step Integration Guide
Crashlytics is extremely popular for its UI, and the depth of its crash reports. But one thing it doesn’t do is log the user actions that lead up to a crash. It’s great at showing you when there’s a problem, but can’t always show you why it happened.
Bugfender, in contrast, will log every single action your users perform, even when the device is offline. Integration of the two products will give you the best of both worlds.
Debugging from Zero: How to Build Breakpoints
Ok first of all, what’s a breakpoint? To answer this question, let’s take a little trip down memory lane. In my first-ever computer programming tutorial, we wrote an algorithm in Pascal to perform a series of simple operations, like printing the sum of two numbers to the console.
As the algorithms became more complex, I began getting unexpected outcomes. The output of the console started coming up incorrect. Then it hit me. I was writing my first bugs.
At that moment I barely knew what the word ‘debug’ even meant, so I did what all programmers do. I added some logs to my code to understand what was happening.
How to Fix Crashing Apps on iPhone and Android: A (Non) Developer’s Guide
If you’ve got an app that keeps going down for no apparent reason, don’t worry: this quick and easy guide will give you the tools to get it up and running smoothly.
If you’re not from the tech world yourselves, you probably think programmers get everything right all the time. That everything in our world is so cutting-edge it can slice through ice, and app crashes are practically an alien concept for us. Well, that’s not quite true. Whether you’re in the business of building apps or you’re a regular user with little technical knowledge, you’re just as likely to experience a crash.