In order to deliver Bugsnag’s error reporting SDK for React Native, we combine multiple error reporting libraries for the underlying platforms. We need them to work together, coordinate the flow of data, and perform as a cohesive, logical unit.
In this session, Ben Gourley, Software Engineer at Bugsnag, will take you through some of the observations, lessons and techniques learned while developing our React Native error reporting library, so that you can apply and practice them while building your own applications. We’ll go over topics like abstractions, synchronization, where logic lives, where we choose to locate Bugsnag’s features and why, JS reuse, and React Native’s quirks.
In order to deliver Bugsnag’s error reporting SDK for React Native, we combine multiple error reporting libraries for the underlying platforms. We need them to work together, coordinate the flow of data, and perform as a cohesive, logical unit.
In this session, Ben Gourley, Software Engineer at Bugsnag, will take you through some of the observations, lessons and techniques learned while developing our React Native error reporting library, so that you can apply and practice them while building your own applications. We’ll go over topics like abstractions, synchronization, where logic lives, where we choose to locate Bugsnag’s features and why, JS reuse, and React Native’s quirks.
What you'll learn
In order to deliver Bugsnag’s error reporting SDK for React Native, we combine multiple error reporting libraries for the underlying platforms. We need them to work together, coordinate the flow of data, and perform as a cohesive, logical unit.
In this session, Ben Gourley, Software Engineer at Bugsnag, will take you through some of the observations, lessons and techniques learned while developing our React Native error reporting library, so that you can apply and practice them while building your own applications. We’ll go over topics like abstractions, synchronization, where logic lives, where we choose to locate Bugsnag’s features and why, JS reuse, and React Native’s quirks.
In order to deliver Bugsnag’s error reporting SDK for React Native, we combine multiple error reporting libraries for the underlying platforms. We need them to work together, coordinate the flow of data, and perform as a cohesive, logical unit.
In this session, Ben Gourley, Software Engineer at Bugsnag, will take you through some of the observations, lessons and techniques learned while developing our React Native error reporting library, so that you can apply and practice them while building your own applications. We’ll go over topics like abstractions, synchronization, where logic lives, where we choose to locate Bugsnag’s features and why, JS reuse, and React Native’s quirks.
In order to deliver Bugsnag’s error reporting SDK for React Native, we combine multiple error reporting libraries for the underlying platforms. We need them to work together, coordinate the flow of data, and perform as a cohesive, logical unit.
In this session, Ben Gourley, Software Engineer at Bugsnag, will take you through some of the observations, lessons and techniques learned while developing our React Native error reporting library, so that you can apply and practice them while building your own applications. We’ll go over topics like abstractions, synchronization, where logic lives, where we choose to locate Bugsnag’s features and why, JS reuse, and React Native’s quirks.
Get started for free.
Try all features for 14 days · No credit card required.
