Questions, answered plainly.

An app builder for native mobile apps. You design in the browser: start from a template, drag blocks onto screens and draw arrows between them for tabs, pushed screens and pop-ups. Then your own coding agent turns the design into a real Expo project, one codebase for iOS and Android, and the code is yours.

You press Send app to agent and paste one line into your agent. It calls our tools to create an Expo project with your screens, install the components they use and wire the navigation into an app shell we have already tested on both platforms. Then verify_app checks the project against what it was told to write, so the agent knows when it is finished rather than guessing. You can keep asking it for changes afterwards, the same way you would in any codebase.

Claude Code, Cursor, Codex, VS Code and Gemini CLI each have a setup on the Connect your agent page, and any agent that can add a remote MCP server works the same way. We tested a full build with Claude Sonnet: no top-tier model needed, and our tools used about 2% of the agent’s context.

Yes. Designing in the App Builder is free, with no account and no install, and so are the lookup tools your agent can use to ask which component to use and what props it takes. You pay only to generate code.

For iOS, yes: a Mac with Xcode 26 and an iOS 26 simulator or device. Apple gives system controls Liquid Glass when an app is compiled against the iOS 26 SDK, so the toolchain matters, not just the phone. Android needs only the Android SDK and works on any computer.

Cloud build services can compile an iOS app without a Mac, and we still ask for one. Once you add your own database, sign-in, payments or push, you are installing native modules we do not ship, and that is where a Mac stops being optional.

Xcode 27 support is in progress: a project on Expo SDK 56 built with Xcode 27 crashes at launch on iOS 27, so stay on Xcode 26 until our exports move to Expo SDK 57 (expo 57.0.23 or later and expo-build-properties 57.0.20 or later) with ios.enableSceneSupport.

Yes. On Android every component draws Material 3 Expressive through Jetpack Compose, and where Android has a real control (buttons, switches, sliders, chips, the search field, the tab bar) you get that control. iOS gets Apple’s own controls with Liquid Glass on iOS 26. They are two different design languages on purpose, not one look copied onto the other.

Not yet. Verified on iOS 26 and on Android 16 with Material 3 Expressive. iOS 27 support is in progress.

One thing to know before you build: a project on Expo SDK 56 compiled with Xcode 27 installs and then dies at launch, because that SDK needs the UIKit scene life cycle and Expo SDK 56 cannot opt into it. Xcode updates itself from the Mac App Store, so this can happen without you changing anything. We are moving to Expo SDK 57 (expo 57.0.23 or later), which fixes it; until then verify_appchecks your toolchain and stops the build rather than letting you find out at launch.

The compatibility page shows what is verified on each version, and when. It is generated from our run records, so it changes when somebody runs something, not when somebody edits a page.

The same as on the newest. Material ships inside your app rather than coming from the phone, so an older phone gets the same controls. We run the starter apps on Android 16, 15 and 11.

Almost. The Material components ship inside your app and take their colours from your accent rather than the phone’s wallpaper, so skins like One UI do not restyle them. The context menu and the date picker use the phone’s own menu and dialogs, so they match the phone they run on, on purpose.

No. Expo Go cannot run the app, because several components use real native controls, so it needs a development build. Run npx expo run:ios or run:android once, and after that the usual development workflow applies.

No. opointo builds iOS and Android apps. The previews on this site are drawn in the browser to show the design; the real thing runs on a phone.

Yes, all of it. You get a normal Expo project in your own repo: your screens, the components and the app shell, as React Native source you can read and change. There is no runtime from us inside it and nothing that calls home.

Almost certainly one of two things. Native glass goes blank for good if you fade a view that contains it, or mount it on demand directly over another glass surface. Animate transform only, keep glass mounted and change its props instead of remounting. Our check_snippet tool catches both in your agent’s code.

Every app you generated keeps working, forever. The code is in your repo, has no licence check and never contacts us. Cancelling stops the paid parts: generating code with the build tools, pulling components from the registry, and the updates we ship as iOS and Android move. Designing in the App Builder stays free. See Cancellation and refunds.

Because staying correct is the hard part. iOS 26 brought Liquid Glass, Android brought Material 3 Expressive, and iOS 27 and Android 17 are next. Tracking two moving design systems is continuous work, and that is what the subscription pays for. You are not renting the code: what you generate is yours for good.

No. The price you subscribe at is locked for as long as your subscription stays active.

Yes. There is a full refund within 30 days of your first payment. See Cancellation and refunds for the details.

One seat per person who builds with it, at the same price however many you buy. A team shares one licence key.