The React Native Rewind

Catch the latest in our newsletter, The React Native Rewind 👇 thereactnativerewind.com Source: github.com/software-mansi…

If you have ever spent hours debugging a layout issue in React Native, you know that the standard inspector can sometimes feel like you are looking through a foggy window. You see the React components, but you cannot always see exactly how the underlying native views are behaving. 𝗥𝗮𝗱𝗼𝗻 𝗜𝗗𝗘 𝘃𝟭.𝟭𝟳.𝟬 just dropped, and it is designed to clear that window for good. This release from 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗠𝗮𝗻𝘀𝗶𝗼𝗻 turns the IDE into an even more powerful command centre for React Native development by bridging the gap between the JavaScript layer and the native platform. 𝗪𝗵𝗮𝘁'𝘀 𝗻𝗲𝘄 𝗶𝗻 𝘁𝗵𝗶𝘀 𝘃𝗲𝗿𝘀𝗶𝗼𝗻? ➡️ 𝗡𝗮𝘁𝗶𝘃𝗲 𝗩𝗶𝗲𝘄 𝗛𝗶𝗲𝗿𝗮𝗿𝗰𝗵𝘆 𝗜𝗻𝘀𝗽𝗲𝗰𝘁𝗼𝗿 (𝗶𝗢𝗦) — You can now inspect the actual native view tree on iOS. This is a game-changer for debugging complex layouts, animations, or third-party libraries where the React hierarchy doesn't tell the full story. ➡️ 𝗘𝗻𝗵𝗮𝗻𝗰𝗲𝗱 𝗔𝗻𝗱𝗿𝗼𝗶𝗱 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗜𝗻𝘀𝗽𝗲𝗰𝘁𝗼𝗿 — The network inspector on Android has been upgraded to capture native traffic. It now monitors requests from 𝗢𝗸𝗛𝘁𝘁𝗽 and 𝗖𝗿𝗼𝗻𝗲𝘁, ensuring you see every byte leaving the device, even from native modules. ➡️ 𝗖𝗹𝗶𝗽𝗯𝗼𝗮𝗿𝗱 𝗦𝘆𝗻𝗰 — A small but massive quality-of-life improvement. You can now sync your computer's clipboard with your physical device or simulator, ending the era of manually typing long URLs or tokens. ➡️ 𝗥𝗲𝗮𝗰𝘁 𝗡𝗮𝘁𝗶𝘃𝗲 𝟬.𝟳𝟱 & 𝟬.𝟴𝟱 𝗦𝘂𝗽𝗽𝗼𝗿𝘁 — The IDE continues to stay ahead of the curve, adding official support for the latest React Native versions to ensure your environment stays stable as you upgrade. 𝗪𝗵𝘆 𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀? The goal of 𝗥𝗮𝗱𝗼𝗻 𝗜𝗗𝗘 is to reduce the "context switching tax." Usually, to get this level of insight, you would have to jump between 𝗫𝗰𝗼𝗱𝗲, 𝗔𝗻𝗱𝗿𝗼𝗶𝗱 𝗦𝘁𝘂𝗱𝗶𝗼, and your code editor. By bringing native inspection and deep network monitoring directly into the IDE, you can identify performance bottlenecks and layout bugs without ever leaving your workflow. Whether you are debugging a tricky native module or just trying to sync a login token to your test device, these updates make the development loop significantly tighter. #ReactNative #RadonIDE #SoftwareMansion #MobileDev #iOSDev #AndroidDev #DeveloperExperience #OpenSource #JavaScript #TypeScript #DevTools #Debugging

Catch the latest in our newsletter, The React Native Rewind 👇 thereactnativerewind.com Source: github.com/tddworks/bague…

If you’ve ever tried to scale an iOS CI/CD pipeline or build a remote device farm, you know how painful managing simulator instances can be. Usually, you’re stuck with laggy screen sharing or complex setups that break the moment you try to simulate a complex multi-finger gesture or a fast swipe. 𝗯𝗮𝗴𝘂𝗲𝘁𝘁𝗲 is a high-performance solution designed to solve this. It is a headless iOS Simulator manager and farm that brings host-side input injection and high-speed streaming directly to your web browser. 𝗪𝗵𝗮𝘁'𝘀 𝘂𝗻𝗱𝗲𝗿 𝘁𝗵𝗲 𝗵𝗼𝗼𝗱? ➡️ 𝗥𝗲𝗺𝗼𝘁𝗲 𝗜𝗻𝗽𝘂𝘁 𝗥𝗲𝗹𝗮𝘆: Unlike standard remote desktop tools, it uses a specialised host-side pipeline (SimInputBridge → GestureDispatcher → IndigoHIDInput) to inject native taps, swipes, and multi-finger gestures directly into the simulator with near-zero lag. ➡️ 𝟲𝟬 𝗙𝗣𝗦 𝗦𝘁𝗿𝗲𝗮𝗺𝗶𝗻𝗴: It leverages hardware-accelerated H.264 and H.265 encoding via 𝗩𝗶𝗱𝗲𝗼𝗧𝗼𝗼𝗹𝗯𝗼𝘅. It supports a hybrid streaming model (MJPEG for initial frames and AVCC/H.264 for high-speed delta updates), delivering a smooth 60 fps visual experience. ➡️ 𝗛𝗲𝗮𝗱𝗹𝗲𝘀𝘀 𝗙𝗮𝗿𝗺 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁: The CLI allows for full management (create, boot, shutdown) in a headless state. The /farm endpoint provides a grid/list view for managing multiple instances, making it the perfect backbone for automated testing. ➡️ 𝗪𝗲𝗯-𝗕𝗮𝘀𝗲𝗱 𝗜𝗻𝘁𝗲𝗿𝗳𝗮𝗰𝗲: Everything is accessible through a modern React-based dashboard (typically served at localhost:8421) including interactive device bezels, allowing you to interact with Mac-hosted simulators from any machine with a browser. 𝗪𝗵𝘆 𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀? The biggest hurdle for remote mobile development has always been the latency. If the touch response is slow or gestures don't register correctly, you can’t effectively debug UI interactions or perform manual QA. By moving the input handling to the host side and optimising the video pipeline for Apple Silicon, 𝗯𝗮𝗴𝘂𝗲𝘁𝘁𝗲 makes "Simulators-as-a-Service" a high-fidelity reality. Whether you’re building a centralised testing hub for your team or looking to optimise your automation infrastructure, this project provides the high-performance plumbing to bridge the gap between local development and remote scale. #iOSDev #MobileTesting #OpenSource #Simulator #DevOps #Swift #Golang #SoftwareEngineering #CICD #AppleSilicon #DevTools #MobileDev

There are three hard things in computer science. 1️⃣ Cache invalidation 2️⃣ Naming things 3️⃣ Getting your PR reviewed before the heat death of the universe We can't help with the first two. But we made 20 memes for the third one. They're in the latest issue of React Native Rewind, which landed in your inbox this morning. If you're not subscribed yet, that's a you problem we can fix. Sign up, and we'll send them over in your welcome email. Never again will you stare at a "requested changes" notification from three days ago, wondering if you've been ghosted by your own team. 👉 reactnativerewind.com

Catch the latest in our newsletter, The React Native Rewind 👇 thereactnativerewind.com Source: github.com/software-mansi…

Software Mansion just shipped 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗲𝗻𝗿𝗶𝗰𝗵𝗲𝗱 𝘃𝟬.𝟳.𝟬, and it closes a loop the library has been working toward for a while. 𝗘𝗻𝗿𝗶𝗰𝗵𝗲𝗱𝗧𝗲𝘅𝘁𝗜𝗻𝗽𝘂𝘁 lets users write rich text natively (bold, italics, lists, links, headings, checkboxes, images). What was missing was a way to render that content back out, natively, without a WebView or a heavyweight parser. That's what 𝗘𝗻𝗿𝗶𝗰𝗵𝗲𝗱𝗧𝗲𝘅𝘁 brings in 0.7.0. Instead of "converting" HTML, it maps elements to native components. No browser engine, no parser quirks, and smooth scrolling on large blocks of content. 𝗪𝗵𝗮𝘁'𝘀 𝗶𝗻𝗰𝗹𝘂𝗱𝗲𝗱? ➡️ 𝗘𝗻𝗿𝗶𝗰𝗵𝗲𝗱𝗧𝗲𝘅𝘁 (𝗻𝗲𝘄) Same styling primitives as EnrichedTextInput, same native view hierarchy. Content authored in one renders cleanly in the other, end to end, inside the native runtime. ➡️ 𝗘𝘅𝗽𝗲𝗿𝗶𝗺𝗲𝗻𝘁𝗮𝗹 𝘄𝗲𝗯 𝘀𝘂𝗽𝗽𝗼𝗿𝘁 Headings, blockquotes, codeblocks, lists, links, checkbox lists, onLinkDetected, removeLink, all now working on react-native-web. Same logic across iOS, Android, and web. ➡️ 𝗤𝘂𝗶𝗲𝘁𝗲𝗿 𝗳𝗶𝘅𝗲𝘀 𝗼𝗻 𝘁𝗵𝗲 𝗶𝗻𝗽𝘂𝘁 𝘀𝗶𝗱𝗲 Pasting screenshots on iOS, autocorrect stripping formatting, onLinkDetected firing multiple times on multi-word links, Backspace on empty input. 𝗪𝗵𝘆 𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀? If you're building anything with user-generated content, comments, notes, or CMS articles, the input and render paths usually live in different worlds. One is a native field, the other is a WebView or a parser that styles inconsistently. react-native-enriched is the first library we've seen seriously trying to make both halves the same system, with shared styling and native performance on both ends, now across platforms. Worth a look if you've ever shipped a comment box and then fought your own renderer. #ReactNative #SoftwareMansion #RichText #HTML #MobileDev #OpenSource #JavaScript #TypeScript #WebDev #CrossPlatform #SoftwareEngineering

Take a look if building AR/VR inside the ecosystem has ever been on your wishlist.

Catch the latest in our newsletter, The React Native Rewind 👇 thereactnativerewind.com Source: github.com/jingjing2222/r…

If you have ever built a location-aware app with high-frequency tracking, you know that not all native modules are created equal. The standard 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆/𝗴𝗲𝗼𝗹𝗼𝗰𝗮𝘁𝗶𝗼𝗻 package is the industry standard, but with location updates firing constantly, every call counts. A new library changes the game by rebuilding the geolocation engine on top of 𝗡𝗶𝘁𝗿𝗼 𝗠𝗼𝗱𝘂𝗹𝗲𝘀, the ultra-fast, next-generation native module framework. It offers a high-performance alternative without forcing you to rewrite your entire implementation. 𝗪𝗵𝗮𝘁 𝗺𝗮𝗸𝗲𝘀 𝗶𝘁 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁? ➡️ 𝗡𝗶𝘁𝗿𝗼-𝗣𝗼𝘄𝗲𝗿𝗲𝗱 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲: By leveraging Nitro, this library enables zero-copy data transfer between the native layer and JavaScript. This means lower latency and less CPU usage, which is critical for apps requiring high-frequency location tracking. ➡️ 𝗙𝘂𝗹𝗹 𝗖𝗼𝗺𝗽𝗮𝘁𝗶𝗯𝗶𝗹𝗶𝘁𝘆: It includes a compat API specifically designed to be a drop-in replacement for @𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆/𝗴𝗲𝗼𝗹𝗼𝗰𝗮𝘁𝗶𝗼𝗻. You can keep your existing logic and hooks while reaping the performance benefits of a modern backend. ➡️ 𝗧𝘆𝗽𝗲 𝗦𝗮𝗳𝗲𝘁𝘆: Since Nitro generates its own glue code, you get highly accurate TypeScript definitions and a more robust connection to native iOS and Android location services. 𝗪𝗵𝘆 𝘀𝗵𝗼𝘂𝗹𝗱 𝘆𝗼𝘂 𝗰𝗮𝗿𝗲? Geolocation is a "noisy" stream of data, and the cost of every update adds up fast. Nitro's zero-copy approach skips work that ordinary native modules still do on each call, so your app stays fluid even when processing constant GPS pings in the background. We covered the library, the one-line migration, and where it fits in the wider Nitro story in React Native Rewind #41 👇 #a-one-line-geolocation-migration" target="_blank" rel="nofollow noopener">reactnativerewind.com/issues/univers…

Worth a look if you've ever wanted to ship AR/VR without leaving the ecosystem.

Try Studio now for free: reactvision.xyz/studio/?utm_so…

If you have ever wanted to build AR or VR but bounced off the moment you saw Unity, C#, and the idea of leaving React Native behind, you are not alone. React Native has been quietly making moves into spatial computing. Meta shipped official Meta Quest support earlier this year, and expo-horizon-core from Software Mansion gives you the build pipeline to get a React Native app onto a headset. But once your app is running, you still have to author every scene by hand. There is no visual editor, no asset workflow, no shared layer between phone AR and headset VR. 𝗥𝗲𝗮𝗰𝘁𝗩𝗶𝘀𝗶𝗼𝗻 just filled that gap. They have launched 𝗦𝘁𝘂𝗱𝗶𝗼, a browser-based visual editor for AR and VR scenes, and shipped 𝗠𝗲𝘁𝗮 𝗤𝘂𝗲𝘀𝘁 𝘀𝘂𝗽𝗽𝗼𝗿𝘁. 𝗪𝗵𝗮𝘁'𝘀 𝗵𝗮𝗽𝗽𝗲𝗻𝗶𝗻𝗴? You design scenes in 𝗦𝘁𝘂𝗱𝗶𝗼 by dragging and dropping 3D objects in your browser, generating assets from text prompts, and previewing live on your phone. When you are ready to ship, one component (𝗦𝘁𝘂𝗱𝗶𝗼𝗦𝗰𝗲𝗻𝗲𝗡𝗮𝘃𝗶𝗴𝗮𝘁𝗼𝗿) drops the entire scene into your native app. ➡️ 𝗩𝗶𝘀𝘂𝗮𝗹 𝗦𝗰𝗲𝗻𝗲 𝗘𝗱𝗶𝘁𝗼𝗿: Compose AR and VR scenes in the browser with drag-and-drop, then load them into a React Native app with a single component. ➡️ 𝗔𝗜-𝗣𝗼𝘄𝗲𝗿𝗲𝗱 𝟯𝗗 𝗚𝗲𝗻𝗲𝗿𝗮𝘁𝗶𝗼𝗻: Text-to-3D and image-to-3D are built into Studio, so you can prototype with generated assets before bringing in a 3D artist. ➡️ 𝗠𝗲𝘁𝗮 𝗤𝘂𝗲𝘀𝘁 𝗦𝘂𝗽𝗽𝗼𝗿𝘁: The same project runs natively on Quest 2, Quest 3, and Quest Pro as a VR experience. One codebase, phone AR plus headset VR. ➡️ 𝗘𝘅𝗽𝗼 𝗖𝗼𝗺𝗽𝗮𝘁𝗶𝗯𝗹𝗲: Works inside Expo with the React Native stack you already know. ➡️ 𝗖𝗹𝗼𝘂𝗱 𝗮𝗻𝗱 𝗚𝗲𝗼𝘀𝗽𝗮𝘁𝗶𝗮𝗹 𝗔𝗻𝗰𝗵𝗼𝗿𝘀: Shared, persistent AR is included out of the box, so location-based and multiplayer experiences are first-class. 𝗪𝗵𝘆 𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀? The React Native spatial computing story has had real momentum building. What was missing was the authoring layer: the visual tooling that lets developers actually design scenes without writing them by hand. ReactVision is the first to give React Native developers a visual editor, AI asset generation, and a single codebase that ships to phones and Quest headsets together. The 8th Wall shutdown in February displaced thousands of AR developers, and this is the kind of tool that gives them somewhere to land. The SDK is MIT licensed, has 100K+ npm installs, and Studio is in public beta and free to try. Link in comments. #ReactNative #Expo #AR #VR #ReactVision #SpatialComputing #MetaQuest #MobileDev #OpenSource #JavaScript #TypeScript #XR

Catch the latest in our newsletter, The React Native Rewind 👇 thereactnativerewind.com Source: github.com/software-mansi…

If you’ve ever managed custom icons in React Native, you know the frustration of choosing between performance and developer experience. Libraries like 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝘀𝘃𝗴 are flexible but heavy. Every icon creates its own React subtree. The alternative? Manual icon fonts that force you into a constant back-and-forth of using web tools like IcoMoon and syncing font assets every time a design changes. 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗠𝗮𝗻𝘀𝗶𝗼𝗻 𝗟𝗮𝗯𝘀 just released 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗻𝗮𝗻𝗼-𝗶𝗰𝗼𝗻𝘀 to solve exactly this. It’s a build-time icon font generator that gives you the performance of native fonts with the flexibility of simple SVG files. 𝗪𝗵𝗮𝘁’𝘀 𝗵𝗮𝗽𝗽𝗲𝗻𝗶𝗻𝗴? Instead of rendering complex vector paths at runtime, this library automatically converts your folder of SVGs into an optimized icon font during the build process. It essentially teaches your app to treat icons like standard text characters, which allows it to bypass React’s component tree and layout engine entirely. ➡️ 𝗕𝘂𝗶𝗹𝗱-𝘁𝗶𝗺𝗲 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻: It handles the entire pipeline—watching your icon folder, converting SVGs to .ttf files, and linking them to your native project automatically. ➡️ 𝗡𝗮𝘁𝗶𝘃𝗲 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲: Because icons render as native text glyphs, it is significantly faster than traditional SVG rendering, making it the ideal choice for long, scrollable lists or icon-heavy dashboards. ➡️ 𝗘𝘅𝗽𝗼 𝗖𝗼𝗻𝗳𝗶𝗴 𝗣𝗹𝘂𝗴𝗶𝗻: It features first-class support for Expo, automating the native plumbing like Info.plist updates and asset linking during the prebuild phase. ➡️ 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗰 𝗧𝘆𝗽𝗲 𝗦𝗮𝗳𝗲𝘁𝘆: The library generates TypeScript definitions for your icon set, providing full IDE autocomplete and ensuring you never break the UI with a misspelled icon name. 𝗪𝗵𝘆 𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀? In high-performance applications, small overheads add up. By shifting the heavy lifting from the mobile device to your build machine, 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗻𝗮𝗻𝗼-𝗶𝗰𝗼𝗻𝘀 ensures your UI stays buttery smooth while keeping your developer workflow modern. It’s another great example of how 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗠𝗮𝗻𝘀𝗶𝗼𝗻 continues to solve the "last mile" of performance friction in the ecosystem. Before you migrate your entire library, keep in mind: this is designed for the 𝗡𝗲𝘄 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 (Fabric) and requires React Native 0.74 or higher. #ReactNative #Expo #SoftwareMansion #Icons #MobileDev #Performance #DeveloperExperience #OpenSource #JavaScript #TypeScript #SVG #Fabric

A graphics library that draws nothing. No components. No . No pixels. And yet, it might be the reason your next animation stops dropping frames. 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗻𝗶𝘁𝗿𝗼-𝘃𝗲𝗰𝘁𝗼𝗿 by Gideon Chidi sits in a strange place in the stack. It's not a renderer. It doesn't compete with react-native-svg or Skia. It works alongside them. Think about a fitness app that traces your morning run on a map, the line drawing itself in as you scroll. Rendering that line is the easy part. Skia and SVG handle it natively. The hard part is everything that happens before the pixels. Measuring the total length of the path. Finding the exact coordinate at 47% progress. Computing the bounding box. All of that geometry almost always runs in JavaScript, on the same thread as your scroll, your gestures, and your state updates. When the dot stutters, that's where it's stuttering. 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗻𝗶𝘁𝗿𝗼-𝘃𝗲𝗰𝘁𝗼𝗿 moves the whole calculation off the JS thread entirely. The numbers come back ready to feed into whatever renderer you're already using. The benchmark is genuinely silly. I won't spoil it here. 95% of the repo is C++. For the breakdown, including the benchmark, how the API actually looks, it's covered in React Native Rewind #38: #the-maths-beneath-the-drawing" target="_blank" rel="nofollow noopener">reactnativerewind.com/issues/metro-m… #ReactNative #Performance #OpenSource #MobileDev #SoftwareEngineering #JavaScript #TypeScript #Cpp #Graphics #DevTools

Catch the latest in our newsletter, The React Native Rewind 👇 thereactnativerewind.com Source: github.com/margelo/react-…

If you've ever needed a smooth, animated line graph in a React Native app, the kind you see in crypto wallets and stock apps, where the line draws itself in, and you can drag your finger across to scrub through history, you've probably hit the same wall. SVG-based options are everywhere, but they get jittery the moment you ask them to animate, scrub, and re-render at the same time. 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗴𝗿𝗮𝗽𝗵 by Margelo is the answer most teams reach for once they've outgrown the SVG approach. It's narrow on purpose, line graphs only, no bar charts, no pie charts, and built on Skia for rendering and Reanimated for gestures. 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗱𝗼𝗲𝘀 ➡️ 𝗦𝗸𝗶𝗮-𝗿𝗲𝗻𝗱𝗲𝗿𝗲𝗱 𝗹𝗶𝗻𝗲𝘀 — Native path interpolation between data states, so transitions feel like they're happening on the GPU rather than fighting the JS thread. ➡️ 𝗦𝗰𝗿𝘂𝗯𝗯𝗮𝗯𝗹𝗲 𝗽𝗮𝗻 𝗴𝗲𝘀𝘁𝘂𝗿𝗲𝘀 — Drag along the line and a selection dot follows your finger. The dot itself is a slot you can replace with your own component if you want a custom look. ➡️ 𝗖𝘂𝘀𝘁𝗼𝗺 𝗿𝗮𝗻𝗴𝗲𝘀 𝗮𝗻𝗱 𝗮𝘅𝗶𝘀 𝗹𝗮𝗯𝗲𝗹𝘀 — Lock the graph to a fixed timeframe (1D, 1W, 1M) regardless of how much data you've got, and pin labels to the high and low points. ➡️ 𝗔 𝗹𝗶𝗴𝗵𝘁𝘄𝗲𝗶𝗴𝗵𝘁 𝗺𝗼𝗱𝗲 — Pass animated={false} and you get a stripped-down renderer optimised for showing dozens of small graphs in a list (think a portfolio screen with one sparkline per token). It was originally built for the Pink Panda Wallet, where it powers thousands of token graphs daily. That's the spec it was designed against. A lot of small, fast-rendering graphs, plus one big interactive one when you tap in. If you're building anything finance, fitness, or analytics flavoured in React Native, it's worth knowing about. #ReactNative #Skia #Reanimated #DataViz #MobileDev #OpenSource #JavaScript #TypeScript #Margelo