Delighted to share I'm joining @expo later this month. Expo has done more than anyone to shorten the path from "I have an idea" to world-class app. And I believe it's best placed for a future where expectations on quality and distribution only increase. Getting to work in this space, with this team and with this community, is a privilege. Much to build 🚀

Today was my last day at Meta - 5 years with the React team has been incredible. Tomorrow is my first day at @expo - so excited to be putting 100% into building for the builders. Onward! 🚀

Faster, leaner Metro Metro 0.87 brings significant improvements to your dev flow, including: - 2x faster source map generation - Half the memory usage - Stable support for TypeScript and ESM config files - Resolver support for package self-resolve

If you're a react-native contributor, please read the following: Your personal fork of react-native might be locked and could prevent you from contributing further

Yesterday we relocated 🎉

The most important skill for a software engineer IMO is debugging. Writing code is easy. Willingness and ability to debug through layers of abstraction, through code you didn't write, perhaps deep into other areas of the stack (libraries, frameworks, the server, the browser engine, etc.) can prevent you from ever being "blocked". This is a skill I see lacking in a majority of developers these days. Too many people just stop as soon as they hit code they didn't write. They just report it to another team, file a GitHub issue, etc. And then complain when it isn't addressed for them immediately. Your dependencies are your code. You are responsible for them. You can't rely on other people to fix problems you run into all the time. Understand your stack deeply. Learn to debug. It'll help you immensely.

I’m hiring for the 𝝠 Expo Router project! We’re building: ◆ Universal file-based routing ◆ One-click native & web deployment ◆ Expo for web ◆ Server-driven UI Come build the universal React framework and push mobile dev to its absolute limits! 🚀 expo.dev/careers/software-en…

Glad to finally get this shipped! Credit @afoxman4 for kicking off the discussion back in 2022: github.com/microsoft/rnx-kit…

React Native 0.77 is now available! This release includes new styling features like display: contents, support for Android 16KB page sizes, upgrades the Community template to Swift, and much more: reactnative.dev/blog/2025/01…

Measuring a view in @reactjs is now consistent across React DOM and React Native: useLayoutEffect(() => { ref.current.getBoundingClientRect() }) You can even re-adjust your UI during the initial frame before the view is displayed. Zero frame delays. Coming in @Expo SDK 52.

Last week, Meta released brand-new Instagram and Facebook apps for Meta Quest, completely rebuilt using React and React Native. Check out how these apps, and more, were built with React and highlighted at Meta Connect: engineering.fb.com/2024/10/0…

Today we announced React Native DevTools, our next-gen + rewritten debugger stack for React Native, coming soon in 0.76.

This was fun to work on - let us know how you get on!

If you haven’t tried React Native, or if you tried it years ago, you really should check out @expo Expo is now the recommended way to create new apps and trust me, the developer experience is just glorious ⚛️

People are reading too much into this article. The compiler is released as experimental bc it’s genuinely not done yet. Many of the patterns here can be optimized and they are on our list to optimize.

Late to the party but I just caught up with this and it's really great overview and an enjoyable listen - if you're curious about Metro, don't miss it! (If anyone has follow up questions I can do my best here too!)

Sunday rant. For software engineering, my sense is that the phrase “premature optimization is the root of all evil” has massively backfired. Its from a book on data structures and mainly tried to dissuade people from prematurely write things in assembler. But the point was to free you up to think harder about the data structures to use, not leave things comically inefficient. This context is always skipped when it’s uttered. Not all fast software is world-class, but all world-class software is fast. Performance is _the_ killer feature. If you are in engineering, here is a fantastic anecdote. I refer to this account often. It’s a bit subtile, but the implications are massive- It’s an account of how SQLite became 50% faster, not by doing one specific thing but hundreds of small ones. SQLite is everywhere today because of this work. sqlite-users.sqlite.narkive.… We need the engineers in all companies fight for this more. Product leads are not the right owners of the end performance of the software. This needs to be encoded in the professional pride of the software engineering discipline. Leaders in companies need to encourage it and hold engineering accountable. It’s simply not ok to fritter away the performance of the products for random reasons. Every user of your products cares exactly as much about latency as engineers do when typing in their terminal. They just don’t have the words to describe what they don’t like about the experience and neither should they.

Super excited to be speaking at the @ReactNativeConn tomorrow. It is a great opportunity to talk about the advantages of using React Native, with a number of examples of its use in MSFT. @ReactNativeMSFT

Me finding that one web developer interested in learning React Native

Got the opportunity to talk about developing Expo Router, bundling, CNG, and web support! Great podcast ↓