iFynx Integrated Solutions

Posted on Oct 17 Originally published at ifynx.com

iPhone Duo Apps: Arabic RTL, Banking & Super-App Readiness Checklist (Xcode 27.1, Vertical Tab Bars, Screenshots)

#mobile #swift #ux #ios

The short answer

iPhone Duo apps have six days to get ready. Apple opened iPhone Duo pre-orders on Friday 16 October 2026 (5 a.m. PT, which was 4 p.m. in Dubai and 3 p.m. in Riyadh), and the first foldable iPhone reaches customers from Friday 23 October 2026. The UAE is in Apple's first wave, and on 17 October apple.com/sa also showed "Available starting 23/10". Every existing app will run, but only apps rebuilt with the iOS 27.1 SDK in Xcode 27.1 (released 15 October) use the full display. On the outer display, and in landscape on the inner one, toolbars and tab bars move to a vertical column on the side. For Arabic-first products, the detail that matters most is in Apple's Human Interface Guidelines: that vertical column stays on the same physical side in right-to-left languages. This article turns Apple's primary documentation into a checklist for MENA banking, government-ID, super-app and e-commerce teams. Wherever Apple does not document Arabic behaviour, we flag it as something to test, not a promise.

Key facts, with dates and primary sources

9 September 2026, unveiling: Apple introduced iPhone Duo as "the first foldable iPhone". It has a 7.6-inch inner display and a 5.4-inch outer display (7.58 and 5.36 inches measured as rectangles), and both displays share the same aspect ratio. It runs on A20 Pro, has Touch ID in the side button for unlocking open or closed, uses an eSIM-only design worldwide, ships with iOS 27.1, and starts at US$1,999 (256GB to 2TB). (Apple Newsroom: Apple unveils iPhone Duo)
18 September 2026, tools: Xcode 27.1 beta arrived with an iPhone Duo simulator, along with Figma and Sketch design kits in Apple Design Resources. (Apple Developer News: Build for iPhone Duo with new resources)
5 October 2026, submissions open: Apple said apps optimised for iPhone Duo can be submitted now. Apps that submit iPhone Duo screenshots get an "optimized for iPhone Duo" badge on the App Store, and from April 2027 submissions will need iPhone Duo screenshots. (Apple Developer News: Prepare and submit your apps for iPhone Duo)
15 October 2026, Xcode 27.1 (27A9275) released: It includes Swift 6.4 and the iOS 27.1 SDK and needs macOS Tahoe 26.6 or later. Known issues: the iPhone Duo simulator runtime doesn't support StandBy or running and debugging most app extensions, and the first simulator launch can take several minutes. (Apple Developer Releases; Xcode 27.1 Release Notes)
16 October 2026, pre-orders: More than 70 countries and regions, including the UAE, could pre-order from 5 a.m. PT. Availability starts 23 October, and 28 more countries and regions follow from 30 October. (Apple Newsroom, 15–16 Oct)
Gulf store pages (checked 17 October 2026): apple.com/ae listed iPhone Duo "From AED 8,499" and apple.com/sa listed "From SAR 9,499". Both showed "Pre-order iPhone Duo. Available starting 23/10." Prices can change, so check the store before you quote them. (Apple UAE; Apple Saudi Arabia)
Screenshot sizes: the outer display takes 1398 × 2034 (or 2034 × 1398) and the inner display takes 2007 × 2853 (or 2853 × 2007). (App Store Connect: Screenshot specifications)

Do existing iPhone apps work on iPhone Duo without an update?

Yes, they run, but how well depends on the SDK you build with. Apple's "Prepare" page describes three tiers:

iOS 26 SDK or earlier: the app runs but does not adapt. On the open inner display it sits in the centre with empty space around the window. On the closed outer display, content appears to the left of the status bar and camera.
iOS 27 SDK: the app fills most of the inner display but still avoids the status bar on the right edge.
iOS 27.1 SDK or later: the app is optimised. It extends to the full display, and toolbars and tab bars appear vertically below the status bar. Apple warns that before you ship a 27.1 build, you must make sure your content adapts to the bars becoming vertical.

For a Gulf bank or a Saudi super-app, tier 1 looks old the moment a customer unfolds the phone, and tier 3 is where the RTL work starts. Apple's own advice is to rebuild, and the screenshot rule makes that unavoidable by April 2027. (Apple Developer: Three steps to make your app shine on iPhone Duo)

What Apple tells every team to fix first

Apple's checklist is short and very concrete. Its Xcode coding assistant has a resizability skill: ask it to "get my app ready for iPhone Duo". Teams using another agent can export the skill with xcrun agent skills export. Apple says the skill "finds most issues, but not all of them", so review its findings against this list:

Stop sizing from the main screen. Replace UIScreen.main.bounds with view.bounds or window.bounds, or use GeometryReader / onGeometryChange in SwiftUI. Create windows with UIWindow(windowScene:).
Re-read size when it changes. A fold can resize your app in the middle of a session. Put size-dependent layout in layoutSubviews or viewDidLayoutSubviews, and use viewWillTransition(to:with:) for work that has to run when the size changes.
Don't use orientation for layout. Remove layout logic based on UIDevice.current.orientation, statusBarOrientation or interfaceOrientation, and compare width with height instead.
Don't treat "regular width" as "iPad". With iPhone Duo, an iPhone app can have any combination of size classes. Code that shows an iPad-only layout whenever horizontalSizeClass == .regular will now run on an iPhone.
Remove device-size checks such as bounds.height == 844.
Check full-bleed media. Hero images set to aspect-fill "can lose important content on wider displays". Choose between fill and fit, or set a focal point.

Test in the resizable simulator in Device Hub, in iPhone Mirroring on macOS 27 (resize the window to extremes), and in the iPhone Duo simulator in Xcode 27.1. Apple calls the Duo simulator "the best way to test the full native experience".

How do vertical tab bars behave in Arabic RTL on iPhone Duo?

This is the section MENA teams can't skip. Apple's HIG page "Designing for iPhone Duo" (new on 9 September 2026) and the developer article "Preparing your app for iPhone Duo" say the following:

On iPhone Duo, toolbars, tab bars and navigation controls move to the side, except on the inner display in portrait, which keeps standard horizontal bars.
The side column holds the Dynamic Island, the status bar, the toolbar (including navigation buttons) and the tab bar, from top to bottom.
Controls on the vertical axis "stay aligned with the hardware", so they "stay on the same side in right-to-left languages". Apple's tech talk "Raise the bar with iPhone Duo" says the same thing: the bar stays fixed and the content adapts around it.
In Split View multitasking, each app puts its controls along its outer edge, so "the left app has controls on the left".
In a split view, bars stay horizontal for the sidebar or content column and go vertical for the detail column. On the inner display, sheets get a horizontal toolbar for centred or leading placements and a vertical one for trailing placements.
A toolbar item with a title but no icon, or with a custom view, is not shown vertically. The system uses icons in the vertical column.

What this means for Arabic products (our analysis, not Apple's wording): in an LTR app, the side column sits on the trailing edge. In Arabic, the column doesn't flip, so it ends up on the side where Arabic reading starts. Right-aligned Arabic titles, list rows, back affordances and price labels will meet the control column on the same edge. If you used leading/trailing constraints and safe-area insets, the system should handle the spacing. If your Arabic build uses hard-coded left/right offsets, mirrored custom bars or semanticContentAttribute hacks, expect overlaps. Treat these as tests to run, not outcomes we've seen on a device:

Run every primary flow in ar-SA / ar-AE and in English on the closed outer display, in landscape on the inner display, and in Split View on both the left and right side.
Check that the Arabic Back control at the top of the vertical column uses the system glyph and direction. Don't ship a custom mirrored chevron.
Give every toolbar action an SF Symbol plus an Arabic title. Text-only items, such as Arabic "Done" or "Cancel" labels with no icon, stay in a horizontal bar, and the overflow menu shows the icon and title together.
Set visibilityPriority so that "Transfer", "Pay" or "Add to cart" stay visible when the column compresses, and choose the compression behaviour: a minimised tab bar for task flows, an overflow toolbar for navigation-heavy screens.
In SwiftUI, GeometryProxy.reservedRegions(kind:options:layoutDirectionBehavior:) takes a layout-direction parameter. Test it in Arabic for any custom view that avoids the fold or camera, rather than assuming mirrored frames.
Keep amounts, IBANs, card numbers and OTP codes in LTR isolation inside RTL text, and recheck them at every width. Truncation moves when the side column takes space.

Our earlier guides on multilingual product design and the Figma code layers RTL checklist cover the general RTL basics. iPhone Duo adds a fixed, non-mirroring hardware edge to the list.

What should banking and government-ID apps test on a foldable?

Gulf and Egyptian fintech flows include steps that break easily: OTP entry, app switches to Nafath or UAE Pass, card and ID scanning, and biometric prompts. iPhone Duo touches each of them in ways Apple documents:

Biometrics are Touch ID. Apple's press release puts Touch ID in the side button, working whether the device is open or closed. If your Arabic or English copy, onboarding illustrations or settings toggles say "Face ID" without checking LABiometryType, they will be wrong on iPhone Duo. Make the strings come from the biometry type you detect.
Mid-session resizing. Apple says a fold can resize your app mid-session. Open the device on the OTP screen, on the transfer-confirmation screen and while a 3-D Secure web view is loading. Check that entered digits, the timer and the focused field survive, and that the keyboard doesn't hide the Confirm button at either width.
App switch in Split View. iPhone Duo allows two apps side by side for the first time on iPhone. A customer can open the bank app next to Nafath, UAE Pass or an authenticator. Test that universal links and callbacks return to the correct window and that your session timeout doesn't fire while the other app is in front. Our Nafath and UAE Pass onboarding guide lists the return-path failures to look for.
Camera direction can flip. Apple notes that when someone opens, closes or rotates the phone, "the camera you're using may point in the opposite direction". Card, Emirates ID, Iqama and passport scanning should choose the camera by the direction it faces and keep the capture frame clear of the fold.
eSIM-only. iPhone Duo is eSIM-only worldwide. Remove "insert your SIM" steps and support articles that mention SIM trays from Arabic and English onboarding, and check any device-binding logic that assumed a physical SIM.
Tap to Pay and payments UI still use the same system sheets. Re-test them at both widths. Our SAMA Tap to Pay on iPhone article covers the mada trust cues that need to stay visible.

Super-app and e-commerce layouts on the 7.6-inch inner display

Catalogue-heavy apps in the region, including grocery, fashion, electronics retail and ride-hailing super-apps, get the most from the larger screen and have the most to break:

Even-column grids. The HIG recommends an even number of columns "so content divides cleanly" at the fold. A 3-column product grid will put the fold through the middle card.
Arrangement views. The new ArrangementView (SwiftUI) and UIArrangementViewController (UIKit) offer split and overlay styles. In an overlay arrangement on a partially open device, Apple puts the primary view in the trailing or bottom part relative to the fold. Check which pane Arabic users see first. A map with a ride-request card or a product image with a buy box is a natural fit.
Banners with baked-in Arabic text. Promo artwork set to aspect-fill will crop on wider displays, and Arabic headline text inside images is the first thing to disappear. Use live text over images, or set focal points per locale.
Two windows. Apple says users can open two windows of the same app, like Safari, for comparison shopping. If your app supports multiple scenes, a "compare two products" or "two accounts" view is a real feature, not a gimmick.
Siri AI is English-first. Apple says Siri AI is rolling out in beta in English with iOS 27, and Arabic isn't in its current Apple Intelligence language list. Don't build Arabic marketing around Siri onscreen awareness on iPhone Duo yet. See our Siri AI and iOS 27 article.

Are iPhone Duo screenshots required on the App Store?

They aren't required yet, but they are already worth adding:

Now: submitting iPhone Duo screenshots adds a badge to your product page. App Store Connect has a new preview tool that shows your screenshots, product page headers and metadata on iPhone Duo. You can also send a featuring nomination saying the app is optimised for iPhone Duo, "including support for all device poses".
April 2027: Apple's news post says submitted apps "will need to include screenshots for iPhone Duo". The screenshot-specifications page frames it as apps using the iOS 27.1 SDK or later. Plan for both readings.
Arabic storefronts: prepare ar-SA / ar-AE screenshot sets at 1398 × 2034 (outer) and 2007 × 2853 (inner), and show the Arabic UI with the vertical column on its real side. Apple's design templates include the new product page headers and search result assets.

A one-week plan before 23 October

Day 1: install Xcode 27.1 (macOS Tahoe 26.6+), rebuild on the iOS 27.1 SDK, and run "get my app ready for iPhone Duo".
Day 2: fix UIScreen.main, orientation and idiom checks. Move layout into viewDidLayoutSubviews and size-class logic.
Day 3: audit the bars. Use system containers (NavigationStack, TabView, UINavigationController), add icons and titles, and set visibility priorities.
Day 4: run the Arabic RTL matrix in the Duo simulator across all six poses Apple illustrates (closed, tent, open wide, partially folded, open tall, laptop), in Split View left and right, with Dynamic Type at the largest size.
Day 5: run the fintech regressions (OTP, 3-D Secure, Nafath/UAE Pass return, ID scanning, Touch ID copy), then record EN + AR screenshots and preview them in App Store Connect.

If your design system already separates leading/trailing tokens, as we recommended in fintech design systems and product engineering and the Material 3 and Liquid Glass dual-compile guide, most of this week is testing rather than rewriting.

Frequently asked questions

When can customers in the UAE and Saudi Arabia get iPhone Duo?

Apple opened pre-orders on 16 October 2026 at 5 a.m. PT (4 p.m. UAE, 3 p.m. KSA), with availability from 23 October 2026. The UAE is named in Apple's first-wave list, and apple.com/sa showed "Available starting 23/10" on 17 October. Store prices started from AED 8,499 and SAR 9,499 on that date.

Do existing apps work on iPhone Duo without an update?

They run, but apps built with the iOS 26 SDK or earlier appear centred with empty space on the inner display. Apps built with the iOS 27 SDK fill most of it. Only apps built with the iOS 27.1 SDK in Xcode 27.1 use the full display with vertical toolbars and tab bars.

Which Xcode version do I need to build iPhone Duo apps?

You need Xcode 27.1 (build 27A9275, released 15 October 2026). It includes the iOS 27.1 SDK, Swift 6.4 and the iPhone Duo simulator, and requires macOS Tahoe 26.6 or later. The Duo simulator runtime doesn't support StandBy or debugging most app extensions.

How do vertical tab bars behave in Arabic on iPhone Duo?

Apple says controls on the vertical axis stay aligned with the hardware and stay on the same side in right-to-left languages. The bar doesn't mirror and the content adapts around it. Arabic layouts that use leading/trailing constraints and safe areas should adapt, but hard-coded left/right offsets and custom mirrored bars need testing.

Are iPhone Duo screenshots required on the App Store?

Not yet. Submitting them now adds an "optimized for iPhone Duo" badge. Apple says that starting April 2027, submissions will need iPhone Duo screenshots: 1398 × 2034 for the outer display and 2007 × 2853 for the inner display, in portrait or landscape.

Sources

Originally published on iFynx.

DEV Community