概要
公開日: 2026-06-05
翻訳生成に失敗したため、原文をそのまま保存しています。
原文
App.js 2026 wrapped last week in Kraków, hosted by Software Mansion. It's the largest React Native and Expo conference of the year, and this year more than 500 developers showed up for two full days of talks about the state of the ecosystem and where it's headed. We gave a few of those talks. This post pulls together some highlights for the millions of you who couldn't be in the room. Why React Native and Expo are doing well in the AI era Expo is growing AI changed who can build an app and how fast they can do it. React Native and Expo turned out to be well placed for that, mostly because of decisions made long before anyone was prompting a model to write an app. The first reason why AI likes Expo is the stack itself. Building on JavaScript, TypeScript, and React means models have an enormous amount of training data to learn from. When a model writes Expo code, it isn't working from a handful of examples. It's working from years of public React and TypeScript. Documentation is the second reason. Over the past year, the single largest source of commits to the Expo repo was docs. That work shows up directly in how well models write Expo apps, because the docs are part of what they learned from. Then there's universality. Type a prompt into one of those little app-builder boxes ("I want an app that plays the stream from my radio station") and the model doesn't need to know what phone or computer you have. It can reach for Expo, build once, and run everywhere. That makes Expo an easy default for tools generating apps on the fly. The last reason is the community, which is to say all of you. When you solve something hard in React Native and post about it, the next person stands on your work. So do the models reading those posts. It's a big part of why the ecosystem keeps compounding. Problems Expo is focused on solving So, here’s what we’re focusing on next. Agents need to be able to check their own work. When an agent can run an app, look at it, tap through it, and tell whether what it built actually works, it can usually figure the rest out on its own. Tools from teams like Software Mansion (Argent) and Callstack (Agent Device) that let agents inspect a running app, grab screenshots, and probe behavior are the foundation for that loop. Speed continues to matter. Now that writing code is faster for most people, the bottleneck moves to everything around it: builds, distribution, boot times. A lot of our effort this coming year will go into making those parts as fast as possible, so the only limit is how fast you can describe what you want. We also want the easy path to be the good one. Tools like Expo Router should make a polished, native-feeling app the thing you get by default. A year of shipping at Expo Here's the short version of what landed over the past year. - Expo’s support for TV apps extends the universal app idea to the living room. You can share around 85% of your code while targeting Apple TV and Android TV. - Expo UI is stable as of Expo SDK 56, with a default template. It drives real SwiftUI and Jetpack Compose widgets from a single JavaScript API, so you can use an operating system primitive without writing a native module to wrap it. - Expo Launch is a fast way to get an app to TestFlight, the App Store, and the web through a web-based flow, without hand writing configuration files. - The official Expo MCP server connects your agent to your project's SDK version, config, running dev server, and Expo's cloud services. It's now free and open to anyone with an Expo account. The local simulator integration is the part worth calling out: a multimodal agent can screenshot and tap through your running app, pull React Native DevTools data, and dig into why a build or workflow failed using TestFlight and crash data. - The Expo skills repo collects official skills for building, deploying, and debugging Expo apps, covering UI work, deployment, SDK upgrades, DOM components, and dev clients. With deep integration into Expo Route