🙌 𝝠 Expo SDK 58 beta is out. Built for iOS 27 on React Native 0.88 RC, with 𝚎𝚡𝚙𝚘-𝚊𝚙𝚙-𝚒𝚗𝚝𝚎𝚗𝚝𝚜 for Siri, @𝚎𝚡𝚙𝚘/𝚊𝚐𝚎𝚗𝚝-𝚌𝚕𝚒 for coding agents, and Expo Modules 2.0 in beta....and tons more. 𝚗𝚙𝚡 𝚎𝚡𝚙𝚘 𝚒𝚗𝚜𝚝𝚊𝚕𝚕 𝚎𝚡𝚙𝚘@𝚗𝚎𝚡𝚝 --𝚏𝚒𝚡 Tons of delicious details in the changelog: expo.dev/changelog/sdk-58-be…

Native Jetpack Compose carousels, straight from @expo UI 🎠 Get the code below 🧶

The new meta for every devtool: a self-improving loop. Watch @davidmokos_ explain how we’re building one at Expo 👇

Agents make up a large share of our docs traffic. They don't always know the URL, but they know what they want. Jev lands them on the right page.

Cool to see my Expo UI examples auto-magically adapting to the iPhone Duo without any code changes. Hard not to love React Native + @expo when stuff like this just works. Repo below 👇

🍎 Mobile devs in NYC: Expo, @infinite_red, and @Chime are hosting a meetup on September 24. The topic is how mobile teams are putting coding agents to work on real apps, with demos from all three teams and a roundtable to argue about what's working and what's not. ◆ Doors at 5:30 PM ET at the Chime office in Manhattan ◆ Demos from Expo, Infinite Red, and Chime at 6:00 ◆ Roundtable Q&A at 7:00, wrap by 8:00 ◆ Food and drinks covered Registration is approval based, so request a spot. Bring the person on your team who reviews the agent's pull requests - this night is for them. Request a spot: luma.com/fegsycpl

great breakdown by @betomoedano, as always 🙌

iPhone Duo, in the cloud! 📱 Soon your agents can test the Duo without needing Xcode or a Mac.

Expo UI components automatically adapt to different Duo poses.

Agents ship better when the stack is built for them.

My AI Tattoo app running on iPhone Duo 👀 Pretty cool considering all I did was upgrade to Expo SDK 58 :) Stay close to the native apis kids

@expo app on iPhone Duo:)

Regressions happen. But you don't want to find out from app store reviews or spicy reddit comments. With our Observe service you can see which release caused a regression and what kind of devices are experiencing it. And then you can hand your agent a prompt with the data to fix it. It's good to ship and touch grass. It's more relaxing with Observe: try.expo.dev/observe-regress…

A simple agentic workflow we love: Feedback comes in. An agent reproduces it. Writes the fix. Runs it on a simulator. Opens the PR. You stay focused on the product. The loop handles the busywork. expo.dev/services/simulators

I absolutely love Apple SDKs. My first language was Objective-C, I won a scholarship to WWDC, and I started my career as an iOS dev. I firmly believe the best apps feel native to the OS, using platform primitives and human interface guidelines. But we need to stop it with the class wars. Apple's tooling has atrophied and practices have become hostile. Developers expect web-like iteration speed, and want to ship the same high-quality apps on multiple platforms with small teams. I love my toolchain. We use React Native because I feel like it allows our teams to ship the level of polish and quality I've come to expect from excellent mobile apps at a fraction of the effort. I might not have the same opinion in 6 months, and you don't have to agree, but I'm tired of the tool being the measure of the developer. Use the best tool for the job, build a great app and let your work speak for itself.

We're seeing a lot of CI bottlenecks. Change is coming. Here is a pattern we like: TestFlight note → repro on a cloud simulator → issue → fix → sim again → PR. expo.dev/services/simulators

.@expo crew at AgentConf @reactuniverse_ 🔥 Come to our booth to talk about simulators, emulators, and mobile AI infra of the future 🚀