James Ide

Expo’s Series B lets us build + More developer success for our world-class customers + More products to unlock that success + More capacity to meet the demand for our products and services We are also excited to continue collaborating with other great companies, and for the Expo SDK and services to work well with even more libraries, products, and integrations from others. We care and work to be a great partner to great partners. I’m proud of what we’ve built, from what started in a room w/@ccheever and is now a global team over 60 people strong. This is an energizing time to be at @Expo!

Opus 5 is insanely good at building @expo apps. Here's @_poolday_ app, rebuilt fully in expo. Everything is real native UI There hasn't been a better time to build apps.

@BenjDicken I suspect this question won't matter so much in the future as GPT, Claude, etc. become more than "only" language models.

To those on the "yes" side of this debate, I have news for you. No.

@bygregorr @expo Developers are definitely taking on more scope. The idea is to add freedom to where you work and the devices you use x.com/tchayen/status…

@expo The 'more grass' half is the part I'd probe. Every DX improvement I've hit just gets absorbed into scope creep, not leisure. Is this actually cutting steps in the build loop, or something different coming?

Soon you'll be able to touch more grass and ship more code with Expo.

@wwwjim I think you should tessellate it and make a pattern out of it for fabrics, wallpapers, etc.

Wow you gonna do our studio logo in Seattle times three, you must really love INTDEV, flattered, really

Literally build in public

🔜 Text your agent anything - screenshots, videos, voice recordings… for anything - native apps, backends, debugging… on the go

@davidmokos_ @ccheever @_poolday_ @expo 🎈

I've been obsessed with @_poolday_ details. Recreated the balloon font so you can use it in your @expo app or generate your own. > npx expo install pink-balloon-font > npx pink-balloon-font generate

@AdhyaayK This is a higher-order agent, codename: Tuft. Tuft connects your agents to your chat apps to the services you use. It is like a bundle of threads, a tuft if you will! Join the waitlist tuft.dev

@JI Yeah so can u explain what this is and how I can use it

Everyone can make software from any device, anywhere, any time

@aidenybai This model works well for certain types of development work, including shipping to production. Looking to add two engineers, one focused on going to market and one infrastructure and ops. x.com/JI/status/2080…

the current way cloud agents are done is wrong i dont want new ephemeral sandboxes per PR (chores) i want a persistent machine with creds and context that i run agents and create PRs on (primary work)

@aryan49041 Make sure you are using Expo Router, or React Navigation with the native navigators. Should be solid 60fps. Expo Router + RNScreens (@swmansion) also support subtleties like interruptible navigation on iOS: multiple screens animate like if you tap the Back button twice quickly.

@JI Navigation

From every angle Expo is making it easier to build beautiful apps

@rsStats_ @expo Are you using WebGPU in a webview or @wcandillon’s WebGPU native module?

first time playing with three.js, surely not the last. Testing new stuff with WebGPU inside @expo source code: rselmi.com/lab/motion-fos…

The way I think about this is doing native development w/Expo vs. native development w/out Expo. “Expo vs. native” is a false dichotomy. In either case the end user experience features truly native UI and device capabilities if a developer invests in that choice. It’s also not entirely binary. We’ve made it easier to adopt Expo in an existing native app that doesn’t yet use it with expo-brownfield (not my favorite name but is an established term): docs.expo.dev/versions/lates… At Expo, we’re also continuously making it easier to use the native features of the OS and devices, like Home Screen widgets and Live Activities (iOS supported today, Android soon). Expo Router is the only way to get deep linking automatically in an app where every screen is native. Expo Modules 2 (sneak peek!) will feel extremely familiar to developers who write Kotlin and Swift, and is agent-optimized for LLMs trained on those syntaxes. Meta’s significant contributions to React Native over the years have also significantly changed the library: The Hermes engine runs Hermes bytecode or even (experimentally) compiles to ARM64 machine code. React Native no longer has a bridge: Hermes and C++ (and other languages) can directly call each other, synchronously. The Fabric UI renderer supports concurrent rendering: this groundwork paves the way for extremely responsive UI that prioritizes continuous user gestures (dragging your finger) over discrete ones (tapping) over non-interactive updates (finished fetching data). This is another example of how React can elevate native development compared to doing native development without React. And many more improvements from the New Architecture, for which the migration is done. There is much more to be done from the Expo dev tools to the runtime to the APIs to the cloud services that can make it even smoother to make even better apps with the latest coding models and harnesses. On this last note, at Expo we are making a new way to do work with your agents, anywhere. Build any software, run any service, do any work, anywhere at any time. Close your laptop whenever you need. Get preview deployments and native builds to your phone. And much more. We’ll have more to share soon and I would love to add two engineers to come work at Expo on this frontier product!

Very sad to see mobile engineers fighting so desperately to prove that they can use AI to build an RN clones in “nAtIvE” languages to reassure themself. Oh how the tables have turned 😂, we used to question: Can It Be Done In React Native. And now they are questioning themself, can we do it in “nAtIvE” Amazing work @nater02 🔥

@aryan49041 What part is slow?

@JI But a little slow.

@charlieholtz @Baconbrix Let us at Expo know if there is anything we can help with. Our AI infra team works on optimizing our software for agents and related tools.

this app is starting to look pretty good

Ok well this was a fun project that took forever, even with AI. Sol helped a lot towards the end. This is a conversion of our Agent Manager from Vite/React to an Expo app. I made a massive comparison harness to help agents with the conversion. It took a lot of iterations to make sure the harness was able to find every single little dissimilarity, but I think we found it all. Next up is a proper mobile app (finally) and a desktop app (exciting!!)

Coming to Chain React: The future of mobile development with Expo ⚡ The distance between an idea and a shipped app is shrinking. @ccheever from @expo explores how AI is changing the way mobile apps are built, what that means for React Native teams, and where Expo goes next as more of the development process becomes automated. 🔗 chainreactconf.com/speakers/charl… 🎟️ Get tickets: chainreactconf.com #ChainReact2026 #ReactNative #Expo #Portland #MobileDev

Building mobile apps with AI essentially comes down to three tools. Most of the rest is just noise. Skills, MCP servers, and one habit that keeps your agent sharp: context discipline. @rami__maalouf made a great video with advice for how to use skills, MCPs and an ideal workflow for managing context. There is real gold in this blog/video ↓

What if @expo had hardware? I built my dream app dev setup, where I can control multiple devices at once, tap for latest dev builds, and use physical buttons to reload, toggle theme & network, and more.