While there’s room for debate in what constitutes sufficient monitoring for a mobile app, it’s no question that if you wait long enough for users to report issues, then soon you will have no users. For most mobile development teams, you are not measured against how many features you deliver or bugs you fix, but by how successful your app is and how much value it delivers to users. As a result, you need to know where the app is providing a subpar experience and why.

Trace is our new mobile monitoring add-on that has been in public beta since late February. It is also available to you if you have a Bitrise account, so if you want to dive into it, here's where you should start.

There is a great number of logging plugins for Kong, which might be enough for your needs. However, they have certain limitations: Most of them only work on HTTP/HTTPS traffic. They make sense in an API gateway scenario, with a single Kong cluster proxying traffic between consumers and services. Each log line will generally correspond to a request which is “independent” from the rest.

Colin Hemmings, Product Manager at Bitrise introduces Trace, the new application performance monitoring (APM) solution we are building here at Bitrise Trace is monitoring made specifically for mobile, helping you catch bugs before they reach your users. With Trace, you’ll be able to have a complete view of these issues with full context, so that you can assess, reproduce, and fix them as quickly as possible.

Finding slow JavaScript code can be a tricky problem to solve. Small code changes can have a big impact on the performance of your code. Fortunately, many different approaches can help you nail down the exact source of the problem. In this post, you’ll learn about three methods that’ll bring you the results you’re seeking. You can trust manual code inspection, but that has its disadvantages.