If you've built with React Native's Animated API, you've probably hit its rough edges: animations that somehow feel slower since the New Architecture, unexpected flickering during animations, or the confusing `useNativeDriver` flag that you're told to turn on. These bugs were baked into how animation worked under the hood. So we rebuilt it. We replaced React Native's four separate native animation implementations with a single cross-platform engine in C++, then used that foundation to fix a class of bugs that had frustrated developers for a long time. In this talk I'll show you the before-and-after โ demos of long-standing bugs that are finally gone โ and take you under the hood of how one shared engine made it possible.
Be the first to find out by subscribing to Chain React Insiders.
If you've built with React Native's Animated API, you've probably hit its rough edges: animations that somehow feel slower since the New Architecture, unexpected flickering during animations, or the confusing `useNativeDriver` flag that you're told to turn on. These bugs were baked into how animation worked under the hood. So we rebuilt it. We replaced React Native's four separate native animation implementations with a single cross-platform engine in C++, then used that foundation to fix a class of bugs that had frustrated developers for a long time. In this talk I'll show you the before-and-after โ demos of long-standing bugs that are finally gone โ and take you under the hood of how one shared engine made it possible.