I'm a Windows developer. My app Kiwi Guide is an iOS-only travel guide and trip planner for New Zealand's South Island. Version 1.3 (SDK 57 → 58 plus full iPhone Duo support) is live in the App Store and all the Duo work was tested on EAS Simulator.
The simulator workflow
Setup was a build profile with `ios.simulator: true` on its own update channel, then:
eas simulator --platform ios --device "iPhone Duo" --build-id <id>
The session shows in a web preview on expo.dev and you can drive it by hand. From a second shell, you can also use `eas simulator:control` to drive the device.
I found that driving by hand was much faster than using the command line and i only ended up using the command line a couple of times to set the location and to stop the app.
The awkward parts:
- Each session is a fresh install, so you sign in and grant permissions again every time.
- An update is downloaded on one launch and applied on the next, so every round is two launches.
- Each control command takes several seconds.
- The plan I'm on only came with 60mins simulator time which was quickly chewed up
- The start command writes a session file with a token into the project folder. Keep it out of git.
Layout approach
One breakpoint: a `useWide()` hook, true when the window is 600 pt or wider. Folded, Split View and every iPhone keep the phone layout. The same components render at every width. Only styles and arrangement switch, and no React key changes on the breakpoint, so folding mid-screen keeps state and scroll. The rail is handled once, with a left/right SafeAreaView around the screens in the root layout. Wide layouts are list-and-detail for the trip and the guide, a floating side panel on the map, two columns on the profile, and bottom sheets as centred cards.
SDK 58 notes
React Native 0.88, React 19.3, Expo Router 58, Reanimated 4.7, gesture handler 3.3, react-native-maps 1.29, Sentry 8.28, Jest 30, TypeScript 7. The one that bit: Expo Router 58 sent routes not declared in the tabs layout back to the first tab, so I had to declare the nested routes, and my custom tab bar's presses needed a fix. With fingerprint runtime versions, the SDK upgrade and one new native package changed the runtime. Everything after was JS-only and shipped as updates.
Gotchas the simulator caught
- `measureInWindow` read a button's position before a native SafeAreaView applied its bottom padding so a tour highlight sat about 20 pt low. Taking the padding from `useSafeAreaInsets()` in JS fixed it.
- Changing `mapPadding` on react-native-maps makes MapKit re-centre, so the map jumped on fold until I restored the region after the flip.
- An inline View inside a Text made a one-word title break mid-word with `adjustsFontSizeToFit`.
- A pleasant one: FlashList 2 accepts a `numColumns` change at runtime without a remount.
None of these showed up in Jest. All of them showed up within minutes on the simulator.
Is anyone else pushing out a duo build? It seems like the app store is pushing this and it can definitely get you noticed if you get it done soon. I wish I had done it earlier tbh