We invite creators, developers, and companies big and small to join us in shaping a future where going from idea to app is faster and more accessible than ever.

We aim to enable a sea change of new creators, and level up experienced developers, by providing the Expo framework and EAS as the best foundation for AI-assisted creator tools to run and distribute their users' apps.

Expo's open AI strategy is to democratize app creation through many-company collaboration. For us, this is also a movement.

But we're aware the proliferation of new tools may create feelings of AI fatigue in some. Like the JS ecosystem, which had times of high growth, AI-assisted dev tools will mature. Our role in the AI ecosystem is to provide Expo & EAS as a dependable foundation for both human developers & AI agents.

@vercel.com has published docs on using their AI SDK within apps made with Expo. We've also published llms.txt to better inform AI-assisted tools like Cursor about the Expo APIs and services. You can expect more to come in this rapidly evolving space, both from other companies and from us at Expo.

Several companies already interoperate with the Expo framework to begin making this a reality. In the last few weeks, Replit, @bolt.new, Rork, a0.dev, Appacella, and Makeway.app launched AI agents that use Expo to enable creators to prompt from "idea to app store".

By including AI agents as first-class users of Expo's software and services, we'll help other companies making AI-assisted tools to swiftly adopt Expo and EAS, and ultimately make it easier for creators to deliver beautiful, universal native apps.

Also, @stackblitz.com's WebContainers have been a promising way to run Expo CLI and the dev server in the web browser, making the Expo framework more accessible to browser-using agents like OpenAI's Operator.

There is early prior art like @anthropic.com's Model Context Protocol (MCP) to define programmatic interfaces for AI agents and @biilmann.blog's writing about agent experience (AX) as an analogue to UX.

To this end, we'll expand the audience of the Expo framework and EAS to include both human developers and AI agents. We'll need to think about what it means to design CLIs & UIs for agents. For instance, topics like HCI & a11y will have analogues for AI agents, like A(gent)CI & agent accessibility.

Our open strategy is to build an app-creator ecosystem made up of many companies working on AI-assisted creator tools. Expo's main role here is to provide the best app framework for these tools to target & run the apps they create, and the best infra to build + test + deploy native apps & websites.

Like writing, where everyone writes even if they're not professional writers, many more people will build the apps they want for themselves, their friends, and their communities. Generative AI is a catalyst for this transformation, and we are positioning Expo to be near its center.

One way React Native helps engineers grow their skillset is with native modules. I’ve found many of the best developers using RN will write Kotlin/Swift and use the platform’s native UI components and APIs when needed. They still learn parts of traditional native development, but on demand.