The Error Tracking Space Is Heating Up
A plethora of crash reporting and error tracking tools have sprouted up in the past couple of years. But why is this so?
Join the DZone community and get the full member experience.Join For Free
Years ago, technologies like Adobe Flash, Flex, and Microsoft Silverlight used to be the standard for creating visually pleasing, interactive web experiences. The term “single-page application” was more of a buzzword, and while employed by smaller ventures, larger companies were nowhere near adopting such approach.
What’s a SPA?
We all know that the present-day user gets easily distracted. Our attention span is getting shorter and shorter. Providing a snappy, enjoyable user experience to web visitors today is a key factor in achieving business goals.
Similarly, it’s not news for anyone that mobile traffic’s been growing faster than traditional desktop traffic, and mobile device users by default expect the look and feel of native mobile apps.
With single-page applications, organizations can mimic the native app-like experience (and performance!) within the browser. This provides an answer to the common question a lot of companies are facing nowadays: app or website? Saving the costs and effort to upload and maintain an app on the app stores is not negligible. On top, you can update your web application as many times as you want, this way shortening time to market.
The single-page model also supports more elaborate user interactions which can be harder to implement with server-side rendering: Pinterest’s deep linking, Artsy’s fade between pages, infinite scroll, just to name a few (i.e. Rise of the SPA by Dan Pupius).
What’s more, adding more logic to the client side of the SPA and allowing the app to handle separation of data and view layers help radically improve performance by reducing the number of client-server loops.
The numbers speak for themselves:
A continuous cycle of growth in the enterprise. Source: Salesforce Developers Blog.
The Explosive Growth of Error Tracking Tools
The past few years saw the vigorous development of crash reporting and error tracking tools to fill an increasing need to understand, reproduce and debug application problems, both on the server- and the client-side.
Furthermore, with the growing popularity of SPAs, where a substantial part of the app logic gets added to the client, the debugging challenges for developers are multiplying. The application client-side gets more dynamic and complex and developers struggle to replicate the errors that occurred in user browsers.
The increasing popularity of hosted software and the fact that these tools managed to freeride the SaaS wave helped them quickly secure traction and user base.
There’s a lot of similar solutions in the space, and competition is heating up. In the past few years, tools like Rollbar and Bugsnag also managed to secure funding and the interest of VC and angels investors alike.
The New Frontier
A new concept has started to gain traction in the past year: tools that help developers get the context in which an error happened in order to reproduce the issue and debug faster. These tools get plugged into the web app, CPAs including, to collect data on how users interact with it. When a user runs into an error (something breaks, a network request fails, etc.), the tool recreates the collected data as a video in which developers can see every step the user took to get the error.
A SessionStack user session recording. All user actions and tech details can be expanded on the left.
Published at DZone with permission of , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.