Kotlin Multiplatform apps are a great option for big projects. They allow us to unify the business logic under a Kotlin module while using the latest perks of each platform’s individual UI, significantly reducing development costs. Debugging in Kotlin Multiplatform is easy, as you can use typical tools like adding breakpoints and printing logs in the console – and in Bugfender. Continue reading for a full tutorial. KMM stands for Kotlin Multiplatform Mobile.

This quarter we’ve been working on many improvements that will make your life easier when catching those sneaky bugs, and expand Bugfender’s capabilities with some of the most requested features: We hope you find all these updates useful!

In this article, we explain how you can remotely debug and troubleshoot production errors in your React Native App. For this, we will use the Bugfender free integration to enable a real-time log and be able to follow what users are doing with your App.

Here we try to explain how to solve any bug or error that your App created with Angular may have and that may be affecting your users without them or yourself knowing it. For this we will use a remote debugger and logging for Angular using the Bugfender library.

By combining custom errors, named functions and Bugfender, you can create a robust error-handling process that allows you to immediately identify the defects of your JavaScript apps. Unhandled JavaScript errors will stop the execution of your script, leaving the application in an undesired state – or, even worse, in an unknown state. So you need a robust error-handling process to avoid unknown errors in your apps. But, why are errors thrown anyway?

Most of our blog posts are dedicated to Android, iOS and JavaScript development because those are the most interesting platforms for our users. However, from time to time, we also think it’s important to share what’s happening behind the scenes. In this post we’ll be highlighting some of the recent improvements we’ve made to Bugfender’s infrastructure.

Have you ever found yourself copy-pasting the same bits of JavaScript code between different projects? Well, when this situation happens two or three times in a row, it’s usually a good indicator that you have a piece of code that is useful and reusable. So, if you are already reusing your code across several different projects, why not go the extra mile and convert it into a library that allows you to optimize this code-sharing?

Node Package Manager, or npm (usually written in lower case) is one of the most commonly used package managers in JavaScript projects. It is built on top of Node and is so powerful that nearly everybody is using it.