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.
React Native from an SDK's point of view
360iDev 2020
*If the form isn’t loading or submitting properly, please 1) disable ad blockers, 2) enable cookies, and 3) turn off any tracking protection features. Still can’t see the form? Reach out to events@bugsnag.com.
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.
Fill out the form on this page to gain access to the free on-demand talk.
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.
*If the form isn’t loading or submitting properly, please 1) disable ad blockers, 2) enable cookies, and 3) turn off any tracking protection features. Still can’t see the form? Reach out to sales@bugsnag.com.
.png)
