Christoph Pader

The React Native community just got a new powerhouse of knowledge. 🚨 Margelo’s blog is now live. Expect deep dives into internals, performance, architecture, tooling, case studies, vision camera, and pixel-perfect mobile engineering. Built by engineers pushing the ecosystem forward. If you’re serious about React Native, check it out

The @discord app: New Arch unoptimized vs New Arch optimized ✨

@mrousavy Congrats on this hella big release ! 👏🏼🔥

It's finally done. I just released VisionCamera V5, the biggest update to VisionCamera ever, and my biggest open-source project ever (1/5) 🥳🎉🍾

@zoontek @RNLConf @expo congrats! 🎉

I announced it at @RNLConf, so I can share it here as well: I'm joining @expo starting next year 🎉

We're hosting the Mobileheads React Native meetup in our office in Vienna again! 🎡🇦🇹 Stop by on Thursday for some snacks and interesting talks about RN 🎙️

When your React Native build works after 8h of debugging

@Baconbrix @expo Thanks for your awesome work on this! 🙌🏼 @blazejkustra_

Started using React Compiler Marker with @Expo and there's no going back—I'm in LOVE 🚀 Shows you ✨ inline when a component is auto-memoized (useMemo, useCallback, etc) or when React Compiler 🚫 failed and you need to follow Rules of React. =blazejkustra.react-compiler-marker

Let me introduce you to new library 🚀 It's called hermesx! - 😎 Quickly run Typescript scripts in Hermes environment - 📦 Use 3rd party dependencies - 🏁Very useful for performance profiling of single function without need to build whole RN app Check it out 👇

Hire us if you are developing for iOS 6

At this year's Margelo offsite in Italy, we held a 2-day hackathon - the theme was 2010-style apps! 🏝️🇮🇹📱 Time for some throwbacks:

Introducing the @margelo_com design team. ✨ We spent the last year quietly assembling an S-tier crew and collaborating with a few select clients. Now, we’re ready for more! → hello@margelo.com

@swmansion good job on RNKC @ziusko!! 👏🏼

Debugging is no longer the biggest pain point in React Native development! It’s pretty obvious this survey and so many people sharing their opinions helped! 👏👏👏 Surprised to see keyboard handling in top 3, while there is a potential solution ➡️ the keyboard-controller by @ziusko & @margelo_io. Good news? Migration to New Architecture doesn’t seem to be that problematic, as it ranked way below top 10 biggest issues. 🎉 What’s the biggest pain point now? See it yourself 👇 results.stateofreactnative.com/en-US/

cuteee 🥰

@lauridskern wohoo! 🚀

@lauridskern cool idea! good luck with the auction 🙌🏼

Talks, team building, great food and a beautiful city🌟 — such an amazing weekend with @expensify & @margelo_io in Prague! Loved meeting the talented minds behind the Expensify App and sharing inspiring conversations 🙌 The @swmansion team can’t wait for the next meetup! 🚀

Margelo gang in london 🇬🇧

Rare gathering of the @margelo_io boys!

@birch_js @o_kwasniewski @mrousavy I agree. The visualization is confusing and misleading imo. It would be better to have separate comparisons for C++ and Swift/Kotlin.

@o_kwasniewski @mrousavy I do think people are gonna read this and misunderstand that Nitro is “pure overhead” though, when in fact all you may be seeing is the cost of marshalling between C++ and Swift, which could be avoided by writing Nitro in C++. Nitro C++ vs. Swift benchmarks as well, please!

I got curious and decided to measure C++ Turbo Modules against Nitro Modules. I used @mrousavy benchmark and rewrote the Objective-C Turbo Module to C++ C++ Turbo modules are up to: - 2x faster than Nitro - 22x faster than the Objc module 🏎️