Systems | Development | Analytics | API | Testing

We’ve all had this problem as developers. An app works perfectly fine in our own local environment, but as soon as it hits the real world it starts throwing glitches all over town. Why does this happen? Because the real world is messy and hard to predict. Some bugs are only triggered by real users, real devices, and real data. This makes them harder to diagnose – but not impossible.

Memory leaks are the bugs that really creep up on you. One minute your app is running perfectly, then suddenly it slows to a crawl or crashes. We don’t get a warning with memory leaks, so we need to prepare proactively and be ready when they hit. This means we need to: This guide is here for all of that.

Remote debugging using IntelliJ IDEA offers several benefits. Using this JetBrains IDE, you get interactive breakpoints, variable inspection, and debugging integrated directly with the IntelliJ editor. However you can also introduce configuration complexity and potential security risks if you don’t get it right. IntelliJ has become a favorite of the Bugfender team and in this post we’ll walk through the full setup, from the JVM flag to debugging inside a Docker container.

An app crash is one of the fastest ways to drain both users and rankings. Many users will uninstall an app after just one crash, and both the App Store and Google Play will penalize crash-prone or unstable apps. At Bugfender, we’ve been investigating app crashes since 2014. In this post we’re going to share all our key learnings, so you can: You’ll come away with a reliable, repeatable way to anticipate app crashes – wherever they happen. This post is generally platform-agnostic.

Progressive Web Apps (PWAs) combine the reach of the web with many native app capabilities. Users get an app-like experience without the traditional app-store download process, while developers can build and maintain experiences from a shared web codebase. This doesn’t mean PWAs are simple to build, however. They must provide a reliable experience across different browsers, devices and network conditions.

Debugging is an essential skill that allows software developers to prevent crashes and maintain reliable code. Virtually all applications run into bugs at some point, due to logic errors, unexpected inputs or system interactions. It’s vital that we have effective tools and processes to resolve them. This guide will give you a step-by-step guide to debuggging, highlighting common error types with practical means to resolve them.

Android app crashes will cost us users and damage our Play Store ranking. To prevent them from happening, we need to understand the most frequent causes of crashes, read the stack trace effectively, and have plans for common painpoints such as null values. This article will give you the tools to do that.