Building and running

What your agent writes

A normal Expo project with Expo Router. The navigation, providers and tab bar come from an app shell we test on both platforms; your screens are yours.

What the export handles

The details a hand-built screen often misses, written into every screen that needs them:

• Forms. A password field hides what you type, and on iOS offers a strong password. An email field brings up the email keyboard, Return moves to the next field, and the form moves out of the keyboard’s way.
• Header buttons. A button in a screen’s header becomes a native bar button on iOS and a top app bar action on Android.
• The floating button. It floats in the corner above the tab bar instead of scrolling away with the list.
• Dates. A date field opens the system picker: Apple’s compact date picker on iOS, Material 3’s date and time dialogs on Android.

See them on an iPhone and an Android phone on How it works.

Run it

Run npx expo run:ios or npx expo run:android once to make a development build. After that the usual Expo workflow applies. You need a Mac with Xcode 26 to build the iOS app. Android needs only the Android SDK. Expo Go cannot run the app, because several components use real native controls, so it needs a development build.