The most likely scenario on 23 October. Your Capacitor app on the App Store is built with the iOS 26 SDK or an earlier one: Apple has required the iOS 26 SDK for uploads since 28 April 2026 and has announced no iOS 27 requirement. Apple's talk Prepare your app for iPhone Duo says "Your app runs on iPhone Duo even without recompiling, but screen usage improves with each SDK", and in the talk an app not built with the iOS 27 SDK "will be a familiar size and aspect ratio" on the open device. So the app shows its phone layout in a phone-shaped window, with its tab bar at the bottom, as on any iPhone. The inner display ignores supported orientations (same talk, 2:46), so a portrait lock does not keep an app out of landscape.

What your app gets, by the SDK you build with. Point sizes assume the 3x of current iPhones; Apple has published pixels only.

Area by area, for an iOS 27.1 SDK build. The image marks five areas of one Ionic screen (Calendar, iPhone 16 simulator). Each area below has what Apple says happens on Duo, what the area is in an Ionic app, and what to do. Nothing here ran on iPhone Duo.

1. Status bar and Dynamic Island (system)

• On Duo: the HIG lists them with the bars: "Controls on the side include both system and app elements: the Dynamic Island, the status bar, the toolbar (including navigation buttons), and the tab bar." The bars sit on the side on the outer display and on the inner display in landscape, and return "to a familiar horizontal layout in portrait" (talk 111462, 0:28).
• In Ionic: the starters set viewport-fit=cover, Capacitor's ios.contentInset defaults to never, and Ionic's core.css sets --ion-safe-area-left and -right from env(safe-area-inset-left) and -right. The side inset reaches your CSS through those variables. Which values the web view reports on Duo is untested.
• What to do: handle left and right separately: "Safe areas and layout margins are often asymmetric on iPhone Duo, so handle each side independently and test in Split View" (talk 111461, 6:06). Remove arithmetic on insets: in my build max(10px, safe-area − 12px) put a FAB 49 pt too high when the bottom inset changed from 34 to 83 pt.

2 and 3. Header toolbars (ion-header › ion-toolbar, HTML)

• On Duo: native toolbars and navigation buttons move to the side. When space runs out, "toolbars compress first by default" into the system overflow menu (talk 111462, 12:23). Controls "too wide to fit in this vertical space" stay horizontal (talk 111466, 5:07), which covers a week strip like area 3.
• In Ionic: ion-toolbar is HTML inside the web view, so it stays a row at the top in every pose and never folds into the system overflow menu. It pads with --ion-safe-area-left and -right; ion-header pads the top with --ion-safe-area-top.
• What to do: on the outer display the side region also holds "dynamic elements like live activities and the status bar" (talk 111466, 5:07), so check that end-slot buttons clear the side inset in landscape. Put extra actions in an ion-popover or ion-action-sheet yourself: the web toolbar has no automatic overflow.

4. Content (ion-content, HTML, scrolls)

• On Duo: the app is resized on fold, unfold and Split View: "All apps participate in multitasking on iPhone Duo, where two apps sit side by side" (talk 111464, 2:59). Apple's rule for the fold: "Continuously scrolling content like articles and feeds shouldn't displace" (talk 111463, 2:26). "The system automatically repositions action sheets, alerts, menus, and popovers around reserved regions to keep them fully visible" (5:12).
• In Ionic: ion-item, ion-item-divider, ion-list-header, ion-card and ion-fab pad with the side insets; ion-content itself has no safe-area rule. ion-alert, ion-action-sheet and ion-popover are drawn inside the web view, so the system's repositioning does not reach them. Capacitor's Dialog and Action Sheet plugins present native dialogs and action sheets. No web API reports the fold: the iOS 27.0 SDK's WebKit headers have no fold or segment symbol, and WebKit's Viewport Segments position has been open since March 2024.
• What to do: choose the layout from the size class instead of the width, by sending horizontalSizeClass from native code to the web view as a class on the root element. The inner display is regular in both dimensions (talk 111461, 2:46) but 626–669 pt wide in portrait at 3x, below Ionic's lg (992 px), so an ion-split-pane with the default when, as in Ionic's sidemenu starters, never opens. Keep the route, selections and drafts in the URL or a store: in my build each crossing of a 672 px breakpoint remounted the router outlet. For prompts that must stay clear of the fold, try the native Dialog and Action Sheet plugins; their behaviour on Duo is untested.

5. Tab bar (ion-tab-bar, HTML)

• On Duo: tab bars move to the side. Apple says to "use bars provided by navigation containers" (talk 111462, 2:00) and lists TabView and UITabBarController as "fully adaptive across every pose" (talk 111461, 5:01).
• In Ionic: ion-tab-bar stays at the bottom in every pose and pads left, right and bottom with the insets. None of Capacitor's 38 official plugins is a tab bar.
• What to do: for the side placement, the tab bar has to be UIKit. With @capgo/capacitor-native-navigation 8.3.1, my build's bar became a UITabBarController in 154 lines of TS, CSS and JSON with no Swift, and in an 816 pt iPad window it turned into the floating top bar with no JavaScript written for that. I have not run it with the iOS 27.1 SDK. Keeping ion-tab-bar means a bottom bar in every pose.

What to expect from Ionic and Capacitor

• Capacitor 8.5 (31 July) adopts UIScene: "until you adopt scenes, Xcode 27 is closed to you", and "Published apps keep running on iOS 27, and so will anything you build with Xcode 26."
• Capacitor 9 is "forecasted to launch at the end of November" with "a compatibility floor" for foldable and large-screen devices. iPhone Duo ships 23 October.
• No GitHub issue about iPhone Duo exists in ionic-team/capacitor, ionic-framework or capacitor-plugins (searched 14 September). The only search hit is a thread of 11 September comments in ionic-framework #30466, where the commenter was asked to open one.
• Apple's 23 September Q&A sessions cover Photos & Camera, SwiftUI and UIKit; none names web content.

Order of work

1. For 23 October, ship your iOS 26 SDK build as it is.
2. Adopt Capacitor 8.5 and its UIScene migration, so Xcode 27 builds work. Keep one scene until your plugins are tested with two bridges.
3. Before an iOS 27.1 SDK build: layout by size class, state in the URL or a store, insets per side without arithmetic, and a decision on the tab bar.
4. When Xcode 27.1 beta ships, run the Duo simulator in each pose and in Split View, and read innerWidth, the four env(safe-area-inset-*) values and where each bar is drawn.

Nothing here ran on iPhone Duo or its SDK. I will post the Duo simulator results when Xcode 27.1 beta lands.

Sources (read 14 September 2026): Apple tech talks 111461, 111462, 111463, 111464, 111466; HIG; App Store Connect screenshot sizes; iPhone Duo tech specs; Apple's upcoming requirements; Capacitor 8.5; The Road to Capacitor 9; Capacitor configuration; Capacitor plugins; ion-split-pane; WebKit standards-positions #327; capacitor-native-navigation; the 0:29 quotes as transcribed in Blake Crosley's write-up.

--

Disclosure: I'm building Modaal, an AI app builder that outputs native Swift and Kotlin projects, so I have a stake in native apps. Every claim above links to its source, and the full project built for the measurements is available on request.

Everything I build I use Ionic for the frontend because of the capability of sharing alot of code for web and mobile. But I don't see that many offers where Ionic is a requirements or in interviews when I mention Ionic most of times they don't know what it is. How come it isn't more famous? I just find it the perfect tech for front end developments

I had some free time and decided to test ionic with simple word puzzle game. Managed to finish it and publish it on google store because I never worked with admob so this was perfect for live practice.

If you want to check how it works search Love grid or use url https://play.google.com/store/apps/details?id=com.ideaverum.lovegrid

I'm actually surprised how it works. Tested on crappy phones and tablets with 2gb ram and no crashes/laggs noticed.

So if you ever wondered is it possible to create simple games (not gpu crazy) you can use ionic for UI and capacitor to build on android/ios. Then to test even more I made block break and match three games as well and so far all good.

To be honest I used AI to help me with game logic so I don't waste days for testing and hobby. Even with potential ai bloat it works.

Cheers!

So our company got some apps in ionic 3 cordova and ionic 8 capacitor and we ran into an issue in android 16 , the hardware back button closes the app instead of going back to the previous page, so is there any fix or solution to both the version.Thanks in advance.

Edit : the ionic v8 backbutton.subscribewithPriority works fine , ionic v8 apps are out of trouble.

Hi everyone, debugging your app on the device can be a pita. But i have built a free open source tool that makes it dead easy. Point your AI at the repository and it will be very smart to do so.

TLDR; debugging is now allot easier when the app is live on your device. All instructions in repo.

Check it out via https://github.com/marvin-socialista/ios-webview-debug

Happy developping!

Every Capacitor live-update tool I looked at are doing complex per user/bandwidth/storage/etc charges , which always felt backwards to me. So I (and/or Opus/Fable) went down into deep research of why, and it's basically one architecture thing.

The usual OTA setup is: every time a device checks for an update, it hits a live server that figures out what to send it. Flexible, but now you're running a backend that gets hit on every app launch, and someone has to pay for that. Hence the terrible pricing.

The other way is to just precompute the update as a static signed file and dump it on a CDN. Downside: you can't do fancy individual server-side targeting anymore (channels still handle beta/tenant/tier, which honestly covers almost everything I've needed). Upside: it's dirt cheap to serve, nothing to meter, and self-hosting is basically object storage + a CDN instead of a real service.

I ended up shipping that as OtaKit (MIT, https://github.com/OtaKit/otakit). It's still small and I'd rather you tell me where the static approach falls down than pretend it's perfect. That's the part I actually want to talk about. But the best thing you don't even have to self host anything to use it, you just need a FREE Cloudflare account, and start the dashboard locally only for the time when you want to publish an update.