@erkamyaman/capacitor-foldable 8.3.3 → 8.4.0

package/README.md

@@ -145,6 +145,8 @@ npx skills add erkamyaman/capacitor-foldable@capacitor-foldable
 
 It is one skill with the platform detail split out: laying out around the crease in CSS, the full API, Ionic specifics, iPhone Duo, Android foldables, and how to test on both. It is beta, so tell me if any of it steers you wrong. It also ships inside the npm package under [`skills/`](skills/capacitor-foldable), so an agent working in a project that depends on the plugin can find it in `node_modules`.
 
+The same skill is published on its own at [iphone-duo-capacitor-skills](https://github.com/erkamyaman/iphone-duo-capacitor-skills), which is where it sits next to the iPhone Duo skills for SwiftUI and UIKit.
+
 ## Guides
 
 - [Examples](docs/examples.md)

package/dist/esm/definitions.d.ts

@@ -203,6 +203,18 @@ export interface BarPlacement {
      */
     inset: number;
 }
+type ThemeConsumedFoldState = {
+    state: 'flat' | 'half-opened' | 'closed';
+    hingeBounds?: {
+        x: number;
+        y: number;
+        width: number;
+        height: number;
+    };
+};
+type StaysAssignableTo<Shape, T extends Shape> = T;
+type FoldStateStaysThemeCompatible = StaysAssignableTo<ThemeConsumedFoldState, FoldState>;
+export type { FoldStateStaysThemeCompatible };
 export interface FoldablePolyfillOptions {
     /**
      * Take over hiding Ionic's tab bar while the keyboard is open. iPhone Duo

package/dist/esm/definitions.js.map

@@ -1 +1 @@
-{"version":3,"file":"definitions.js","sourceRoot":"","sources":["../../src/definitions.ts"],"names":[],"mappings":"","sourcesContent":["import type { PluginListenerHandle } from '@capacitor/core';\n\nexport interface FoldState {\n  /**\n   * Posture of the fold. `'closed'` is never reported today: a device shut on\n   * its cover display reports `'flat'`.\n   *\n   * @since 7.0.0\n   */\n  state: 'flat' | 'half-opened' | 'closed';\n\n  /**\n   * Whether the fold splits the web view into two areas: `true` when\n   * half-opened, or when the hinge has a physical gap.\n   *\n   * @since 7.0.0\n   */\n  isSeparating: boolean;\n\n  /**\n   * How the device is held: `'tabletop'` when half-opened with a horizontal\n   * hinge, like a laptop, `'book'` when half-opened with a vertical hinge, and\n   * `'flat'` otherwise.\n   *\n   * @since 7.0.0\n   */\n  posture: 'flat' | 'tabletop' | 'book';\n\n  /**\n   * Direction of the hinge relative to the window, so it flips when the device\n   * rotates. Omitted when there is no fold.\n   *\n   * @since 7.0.0\n   */\n  hingeOrientation?: 'horizontal' | 'vertical';\n\n  /**\n   * Position of the fold in CSS pixels, relative to the web view. Zero wide (or\n   * zero tall) on a seamless fold. Omitted when there is no fold.\n   *\n   * @since 7.0.0\n   */\n  hingeBounds?: { x: number; y: number; width: number; height: number };\n\n  /**\n   * Area of the web view the hinge covers, in CSS pixels. Only present on\n   * devices with a physical gap.\n   *\n   * @since 7.0.0\n   */\n  occludedBounds?: { x: number; y: number; width: number; height: number };\n\n  /**\n   * Which display is showing the app, on a device with an inner and an outer\n   * display such as iPhone Duo. Reported on iPhone Duo (iOS 27.1 or later) and\n   * omitted elsewhere.\n   *\n   * @since 7.0.0\n   */\n  activeDisplay?: 'inner' | 'outer';\n\n  /**\n   * Areas of the web view something covers, in CSS pixels. On Android these are\n   * the display cutouts. On iPhone Duo these are the active occlusion regions:\n   * the camera in use, and the strip the system keeps for the vertical status\n   * bar. Use `getReservedRegions()` when you need to tell them apart. Omitted\n   * when there are none.\n   *\n   * @since 7.0.0\n   */\n  cameraBounds?: { x: number; y: number; width: number; height: number }[];\n\n  /**\n   * Space the system asks you to keep clear around the fold, in CSS pixels.\n   * `hingeBounds` covers the crease plus these margins, so the crease itself is\n   * `hingeBounds` shrunk by them. iPhone Duo reports 20 on each side of a\n   * vertical fold. Omitted on Android and where there is no fold.\n   *\n   * @since 8.2.0\n   */\n  hingeMargins?: { top: number; right: number; bottom: number; left: number };\n}\n\nexport interface ReservedRegion {\n  /**\n   * `'division'` is the fold itself. `'occlusion'` is something covering the\n   * display, such as a camera or the vertical status bar area.\n   *\n   * @since 8.2.0\n   */\n  kind: 'division' | 'occlusion';\n\n  /**\n   * Whether the region applies right now. An inactive division is a flat fold,\n   * and an inactive occlusion is a camera that is not in use.\n   *\n   * @since 8.2.0\n   */\n  isActive: boolean;\n\n  x: number;\n  y: number;\n  width: number;\n  height: number;\n\n  /**\n   * Space to keep clear around the region, in CSS pixels.\n   *\n   * @since 8.2.0\n   */\n  margins: { top: number; right: number; bottom: number; left: number };\n}\n\n/**\n * How far open the hinge is, as the system sees it. Note that it can lag the\n * angle: iOS keeps reporting `'closed'` for a moment after the phone opens.\n *\n * @since 8.2.0\n */\nexport type HingeStatus = 'closed' | 'partiallyOpen' | 'fullyOpen';\n\nexport interface SizeClass {\n  /**\n   * Width size class of the window: `'compact'` on a phone and on the outer\n   * display of a foldable, `'regular'` on the inner display, tablets and wide\n   * windows. On Android and web `'regular'` starts at 600 CSS pixels.\n   *\n   * @since 7.0.0\n   */\n  horizontal: 'compact' | 'regular';\n\n  /**\n   * Height size class of the window: `'compact'` on a phone in landscape. On\n   * Android and web `'regular'` starts at 480 CSS pixels.\n   *\n   * @since 7.0.0\n   */\n  vertical: 'compact' | 'regular';\n\n  /**\n   * Material window width class, from the window width in CSS pixels:\n   * `'compact'` below 600, `'medium'` below 840, `'expanded'` below 1200,\n   * `'large'` below 1600 and `'extraLarge'` from 1600.\n   *\n   * @since 7.0.0\n   */\n  widthClass: 'compact' | 'medium' | 'expanded' | 'large' | 'extraLarge';\n\n  /**\n   * Material window height class, from the window height in CSS pixels:\n   * `'compact'` below 480, `'medium'` below 900 and `'expanded'` from 900.\n   *\n   * @since 7.0.0\n   */\n  heightClass: 'compact' | 'medium' | 'expanded';\n}\n\nexport type DisplayModeStatus = 'unsupported' | 'unavailable' | 'available' | 'active';\n\nexport interface DisplayModes {\n  /**\n   * Rear display mode moves the app to the outer display, so people can frame a\n   * photo with the rear cameras. Only on Android foldables that offer it.\n   *\n   * @since 7.0.0\n   */\n  rearDisplay: DisplayModeStatus;\n\n  /**\n   * Dual-screen mode shows a second page on the outer display while the app\n   * stays on the inner one. Only on Android foldables that offer it.\n   *\n   * @since 7.0.0\n   */\n  dualScreen: DisplayModeStatus;\n}\n\nexport interface BarPlacement {\n  /**\n   * The edge iPhone Duo moves tab bars and toolbars to when it lays them out\n   * vertically: `'leading'` or `'trailing'` in the reading direction, so\n   * `'leading'` is the left edge in left-to-right languages. `null` when bars\n   * stay horizontal, and always on Android, web and iOS before 27.1. An app\n   * built with an older Xcode still gets the edge: it is inferred from the\n   * safe-area inset the bar leaves, since the trait that names it is missing.\n   *\n   * @since 7.0.0\n   */\n  verticalBarEdge: 'leading' | 'trailing' | null;\n\n  /**\n   * How much room the vertical bar takes on its edge, in points, rounded to\n   * whole points. It is the same value the web view reports as a safe-area\n   * inset, so `env(safe-area-inset-*)` already covers simple layouts. Read it\n   * when you place your own chrome and need the number itself, and do not\n   * assume it stays at 84: it differs when the bar is disabled, and Apple can\n   * change it. `0` when no vertical bar is reported, and always on Android and\n   * web.\n   *\n   * @since 8.3.3\n   */\n  inset: number;\n}\n\nexport interface FoldablePolyfillOptions {\n  /**\n   * Take over hiding Ionic's tab bar while the keyboard is open. iPhone Duo\n   * reports a keyboard on every fold, and Ionic waits for the window to return\n   * to the height it had when the keyboard first opened, so its tab bar can\n   * disappear until the device is folded back. With this on, the keyboard events\n   * never reach Ionic, and a `foldable-keyboard-open` class on `<html>` marks\n   * when a text field really has the keyboard. `ionic-tabs.css` hides the tab\n   * bar with it.\n   *\n   * @default false\n   * @since 8.0.2\n   */\n  ionicKeyboard?: boolean;\n}\n\nexport interface FoldablePlugin {\n  /**\n   * Whether the device has a fold at all, and whether it can be propped half\n   * open like a laptop. Both `false` on web, and on iOS except on iPhone Duo\n   * (iOS 27.1 or later).\n   *\n   * @since 7.0.0\n   */\n  isDeviceFoldable(): Promise<{ foldable: boolean; supportsTabletop: boolean }>;\n\n  /**\n   * Read the current fold state. Resolves to\n   * `{ state: 'flat', isSeparating: false, posture: 'flat' }` when there is no\n   * fold information.\n   *\n   * @since 7.0.0\n   */\n  getFoldState(): Promise<FoldState>;\n\n  /**\n   * Read the angle between the two halves of the device, in degrees: `0` when\n   * closed, `180` when flat. Resolves to `{ angle: null }` on devices without a\n   * hinge angle sensor, on web, and on iOS before 27.1.\n   *\n   * @since 7.0.0\n   */\n  getHingeAngle(): Promise<{ angle: number | null; status: HingeStatus | null }>;\n\n  /**\n   * Read every region the system reserves on this display: the fold and\n   * anything covering the screen, active or not. iPhone Duo reports the fold,\n   * the vertical status bar area and the under-display camera. Resolves to an\n   * empty list on Android, on web and on iOS before 27.1.\n   *\n   * @since 8.2.0\n   */\n  getReservedRegions(): Promise<{ regions: ReservedRegion[] }>;\n\n  /**\n   * Choose whether iPhone Duo may move this app's bars to the side of the\n   * display. `'disabled'` keeps everything horizontal, including the status\n   * bar. Resolves to `{ applied: false }` when the app does not use\n   * `FoldableBridgeViewController`, on Android, on web and on iOS before 27.1.\n   * See the iPhone Duo guide for the one-line storyboard change.\n   *\n   * @since 8.2.0\n   */\n  setVerticalBarBehavior(options: { behavior: 'automatic' | 'disabled' }): Promise<{ applied: boolean }>;\n\n  /**\n   * Read the window's size classes: Apple's compact and regular, the signal its\n   * iPhone Duo guidelines recommend for telling the outer display from the inner\n   * one, and Material's width and height classes. On iOS `horizontal` and\n   * `vertical` are UIKit's size classes; everything else comes from the window\n   * size.\n   *\n   * @since 7.0.0\n   */\n  getSizeClass(): Promise<SizeClass>;\n\n  /**\n   * Read which of the foldable display modes the device offers right now. Both\n   * are `'unsupported'` on iOS and web.\n   *\n   * @since 7.0.0\n   */\n  getDisplayModes(): Promise<DisplayModes>;\n\n  /**\n   * Read where native bars go. Native tab bars and toolbars move to the side of\n   * the display on iPhone Duo, but HTML ones stay put, so use this to move your\n   * own tab bar too.\n   *\n   * @since 7.0.0\n   */\n  getBarPlacement(): Promise<BarPlacement>;\n\n  /**\n   * Move the app to the outer display. Android asks the user to confirm first,\n   * and the promise resolves once the app has moved. Rejects when rear display\n   * mode is not `'available'`. Only on Android.\n   *\n   * @since 7.0.0\n   */\n  startRearDisplay(): Promise<void>;\n\n  /**\n   * Move the app back to the inner display.\n   *\n   * @since 7.0.0\n   */\n  stopRearDisplay(): Promise<void>;\n\n  /**\n   * Show a page on the outer display while the app stays on the inner one. A\n   * relative `url` resolves against the app's own URL, so `'cover.html'` loads a\n   * page bundled with the app. The page runs in its own web view without access\n   * to Capacitor plugins. Calling this again while dual-screen mode is active\n   * replaces the page. Only on Android.\n   *\n   * @since 7.0.0\n   */\n  startDualScreen(options: { url: string }): Promise<void>;\n\n  /**\n   * Close the page on the outer display.\n   *\n   * @since 7.0.0\n   */\n  stopDualScreen(): Promise<void>;\n\n  /**\n   * Listen for fold state changes. On a foldable this also fires when the\n   * device rotates, because `hingeOrientation` and `hingeBounds` rotate with\n   * the window.\n   *\n   * @since 7.0.0\n   */\n  addListener(eventName: 'foldStateChange', listenerFunc: (state: FoldState) => void): Promise<PluginListenerHandle>;\n\n  /**\n   * Listen for hinge angle changes. On Android the hinge sensor only runs while\n   * at least one of these listeners is registered. On iOS it fires on iPhone\n   * Duo (iOS 27.1 or later). Never fires on web.\n   *\n   * @since 7.0.0\n   */\n  addListener(\n    eventName: 'hingeAngleChange',\n    listenerFunc: (event: { angle: number }) => void,\n  ): Promise<PluginListenerHandle>;\n\n  /**\n   * Listen for size class changes, such as unfolding the device, rotating it or\n   * resizing the window. On iOS this fires when UIKit's size classes change\n   * (iOS 17 or later) or the device rotates, so a resize that keeps the same\n   * size classes may not update `widthClass` and `heightClass` until then.\n   *\n   * @since 7.0.0\n   */\n  addListener(\n    eventName: 'sizeClassChange',\n    listenerFunc: (sizeClass: SizeClass) => void,\n  ): Promise<PluginListenerHandle>;\n\n  /**\n   * Listen for changes to the display modes, including a mode ending because\n   * the user folded or unfolded the device. Never fires on iOS and web.\n   *\n   * @since 7.0.0\n   */\n  addListener(\n    eventName: 'displayModeChange',\n    listenerFunc: (modes: DisplayModes) => void,\n  ): Promise<PluginListenerHandle>;\n\n  /**\n   * Listen for the device being folded or unfolded. `folding` turns `true` as\n   * soon as the hinge starts moving and `false` about half a second after it\n   * stops, so an app can pause animations or heavy work while the screen is in\n   * motion. Only fires where a hinge angle is available: Android foldables with\n   * a hinge sensor, and iPhone Duo on iOS 27.1 or later.\n   *\n   * @since 8.2.0\n   */\n  addListener(\n    eventName: 'foldingChange',\n    listenerFunc: (event: { folding: boolean }) => void,\n  ): Promise<PluginListenerHandle>;\n\n  /**\n   * Listen for bar placement changes, such as opening or rotating iPhone Duo.\n   * Only fires on iOS 27.1 or later.\n   *\n   * @since 7.0.0\n   */\n  addListener(\n    eventName: 'barPlacementChange',\n    listenerFunc: (placement: BarPlacement) => void,\n  ): Promise<PluginListenerHandle>;\n}\n"]}
+{"version":3,"file":"definitions.js","sourceRoot":"","sources":["../../src/definitions.ts"],"names":[],"mappings":"","sourcesContent":["import type { PluginListenerHandle } from '@capacitor/core';\n\nexport interface FoldState {\n  /**\n   * Posture of the fold. `'closed'` is never reported today: a device shut on\n   * its cover display reports `'flat'`.\n   *\n   * @since 7.0.0\n   */\n  state: 'flat' | 'half-opened' | 'closed';\n\n  /**\n   * Whether the fold splits the web view into two areas: `true` when\n   * half-opened, or when the hinge has a physical gap.\n   *\n   * @since 7.0.0\n   */\n  isSeparating: boolean;\n\n  /**\n   * How the device is held: `'tabletop'` when half-opened with a horizontal\n   * hinge, like a laptop, `'book'` when half-opened with a vertical hinge, and\n   * `'flat'` otherwise.\n   *\n   * @since 7.0.0\n   */\n  posture: 'flat' | 'tabletop' | 'book';\n\n  /**\n   * Direction of the hinge relative to the window, so it flips when the device\n   * rotates. Omitted when there is no fold.\n   *\n   * @since 7.0.0\n   */\n  hingeOrientation?: 'horizontal' | 'vertical';\n\n  /**\n   * Position of the fold in CSS pixels, relative to the web view. Zero wide (or\n   * zero tall) on a seamless fold. Omitted when there is no fold.\n   *\n   * @since 7.0.0\n   */\n  hingeBounds?: { x: number; y: number; width: number; height: number };\n\n  /**\n   * Area of the web view the hinge covers, in CSS pixels. Only present on\n   * devices with a physical gap.\n   *\n   * @since 7.0.0\n   */\n  occludedBounds?: { x: number; y: number; width: number; height: number };\n\n  /**\n   * Which display is showing the app, on a device with an inner and an outer\n   * display such as iPhone Duo. Reported on iPhone Duo (iOS 27.1 or later) and\n   * omitted elsewhere.\n   *\n   * @since 7.0.0\n   */\n  activeDisplay?: 'inner' | 'outer';\n\n  /**\n   * Areas of the web view something covers, in CSS pixels. On Android these are\n   * the display cutouts. On iPhone Duo these are the active occlusion regions:\n   * the camera in use, and the strip the system keeps for the vertical status\n   * bar. Use `getReservedRegions()` when you need to tell them apart. Omitted\n   * when there are none.\n   *\n   * @since 7.0.0\n   */\n  cameraBounds?: { x: number; y: number; width: number; height: number }[];\n\n  /**\n   * Space the system asks you to keep clear around the fold, in CSS pixels.\n   * `hingeBounds` covers the crease plus these margins, so the crease itself is\n   * `hingeBounds` shrunk by them. iPhone Duo reports 20 on each side of a\n   * vertical fold. Omitted on Android and where there is no fold.\n   *\n   * @since 8.2.0\n   */\n  hingeMargins?: { top: number; right: number; bottom: number; left: number };\n}\n\nexport interface ReservedRegion {\n  /**\n   * `'division'` is the fold itself. `'occlusion'` is something covering the\n   * display, such as a camera or the vertical status bar area.\n   *\n   * @since 8.2.0\n   */\n  kind: 'division' | 'occlusion';\n\n  /**\n   * Whether the region applies right now. An inactive division is a flat fold,\n   * and an inactive occlusion is a camera that is not in use.\n   *\n   * @since 8.2.0\n   */\n  isActive: boolean;\n\n  x: number;\n  y: number;\n  width: number;\n  height: number;\n\n  /**\n   * Space to keep clear around the region, in CSS pixels.\n   *\n   * @since 8.2.0\n   */\n  margins: { top: number; right: number; bottom: number; left: number };\n}\n\n/**\n * How far open the hinge is, as the system sees it. Note that it can lag the\n * angle: iOS keeps reporting `'closed'` for a moment after the phone opens.\n *\n * @since 8.2.0\n */\nexport type HingeStatus = 'closed' | 'partiallyOpen' | 'fullyOpen';\n\nexport interface SizeClass {\n  /**\n   * Width size class of the window: `'compact'` on a phone and on the outer\n   * display of a foldable, `'regular'` on the inner display, tablets and wide\n   * windows. On Android and web `'regular'` starts at 600 CSS pixels.\n   *\n   * @since 7.0.0\n   */\n  horizontal: 'compact' | 'regular';\n\n  /**\n   * Height size class of the window: `'compact'` on a phone in landscape. On\n   * Android and web `'regular'` starts at 480 CSS pixels.\n   *\n   * @since 7.0.0\n   */\n  vertical: 'compact' | 'regular';\n\n  /**\n   * Material window width class, from the window width in CSS pixels:\n   * `'compact'` below 600, `'medium'` below 840, `'expanded'` below 1200,\n   * `'large'` below 1600 and `'extraLarge'` from 1600.\n   *\n   * @since 7.0.0\n   */\n  widthClass: 'compact' | 'medium' | 'expanded' | 'large' | 'extraLarge';\n\n  /**\n   * Material window height class, from the window height in CSS pixels:\n   * `'compact'` below 480, `'medium'` below 900 and `'expanded'` from 900.\n   *\n   * @since 7.0.0\n   */\n  heightClass: 'compact' | 'medium' | 'expanded';\n}\n\nexport type DisplayModeStatus = 'unsupported' | 'unavailable' | 'available' | 'active';\n\nexport interface DisplayModes {\n  /**\n   * Rear display mode moves the app to the outer display, so people can frame a\n   * photo with the rear cameras. Only on Android foldables that offer it.\n   *\n   * @since 7.0.0\n   */\n  rearDisplay: DisplayModeStatus;\n\n  /**\n   * Dual-screen mode shows a second page on the outer display while the app\n   * stays on the inner one. Only on Android foldables that offer it.\n   *\n   * @since 7.0.0\n   */\n  dualScreen: DisplayModeStatus;\n}\n\nexport interface BarPlacement {\n  /**\n   * The edge iPhone Duo moves tab bars and toolbars to when it lays them out\n   * vertically: `'leading'` or `'trailing'` in the reading direction, so\n   * `'leading'` is the left edge in left-to-right languages. `null` when bars\n   * stay horizontal, and always on Android, web and iOS before 27.1. An app\n   * built with an older Xcode still gets the edge: it is inferred from the\n   * safe-area inset the bar leaves, since the trait that names it is missing.\n   *\n   * @since 7.0.0\n   */\n  verticalBarEdge: 'leading' | 'trailing' | null;\n\n  /**\n   * How much room the vertical bar takes on its edge, in points, rounded to\n   * whole points. It is the same value the web view reports as a safe-area\n   * inset, so `env(safe-area-inset-*)` already covers simple layouts. Read it\n   * when you place your own chrome and need the number itself, and do not\n   * assume it stays at 84: it differs when the bar is disabled, and Apple can\n   * change it. `0` when no vertical bar is reported, and always on Android and\n   * web.\n   *\n   * @since 8.3.3\n   */\n  inset: number;\n}\n\ntype ThemeConsumedFoldState = {\n  state: 'flat' | 'half-opened' | 'closed';\n  hingeBounds?: { x: number; y: number; width: number; height: number };\n};\n\ntype StaysAssignableTo<Shape, T extends Shape> = T;\n\ntype FoldStateStaysThemeCompatible = StaysAssignableTo<ThemeConsumedFoldState, FoldState>;\n\nexport type { FoldStateStaysThemeCompatible };\n\nexport interface FoldablePolyfillOptions {\n  /**\n   * Take over hiding Ionic's tab bar while the keyboard is open. iPhone Duo\n   * reports a keyboard on every fold, and Ionic waits for the window to return\n   * to the height it had when the keyboard first opened, so its tab bar can\n   * disappear until the device is folded back. With this on, the keyboard events\n   * never reach Ionic, and a `foldable-keyboard-open` class on `<html>` marks\n   * when a text field really has the keyboard. `ionic-tabs.css` hides the tab\n   * bar with it.\n   *\n   * @default false\n   * @since 8.0.2\n   */\n  ionicKeyboard?: boolean;\n}\n\nexport interface FoldablePlugin {\n  /**\n   * Whether the device has a fold at all, and whether it can be propped half\n   * open like a laptop. Both `false` on web, and on iOS except on iPhone Duo\n   * (iOS 27.1 or later).\n   *\n   * @since 7.0.0\n   */\n  isDeviceFoldable(): Promise<{ foldable: boolean; supportsTabletop: boolean }>;\n\n  /**\n   * Read the current fold state. Resolves to\n   * `{ state: 'flat', isSeparating: false, posture: 'flat' }` when there is no\n   * fold information.\n   *\n   * @since 7.0.0\n   */\n  getFoldState(): Promise<FoldState>;\n\n  /**\n   * Read the angle between the two halves of the device, in degrees: `0` when\n   * closed, `180` when flat. Resolves to `{ angle: null }` on devices without a\n   * hinge angle sensor, on web, and on iOS before 27.1.\n   *\n   * @since 7.0.0\n   */\n  getHingeAngle(): Promise<{ angle: number | null; status: HingeStatus | null }>;\n\n  /**\n   * Read every region the system reserves on this display: the fold and\n   * anything covering the screen, active or not. iPhone Duo reports the fold,\n   * the vertical status bar area and the under-display camera. Resolves to an\n   * empty list on Android, on web and on iOS before 27.1.\n   *\n   * @since 8.2.0\n   */\n  getReservedRegions(): Promise<{ regions: ReservedRegion[] }>;\n\n  /**\n   * Choose whether iPhone Duo may move this app's bars to the side of the\n   * display. `'disabled'` keeps everything horizontal, including the status\n   * bar. Resolves to `{ applied: false }` when the app does not use\n   * `FoldableBridgeViewController`, on Android, on web and on iOS before 27.1.\n   * See the iPhone Duo guide for the one-line storyboard change.\n   *\n   * @since 8.2.0\n   */\n  setVerticalBarBehavior(options: { behavior: 'automatic' | 'disabled' }): Promise<{ applied: boolean }>;\n\n  /**\n   * Read the window's size classes: Apple's compact and regular, the signal its\n   * iPhone Duo guidelines recommend for telling the outer display from the inner\n   * one, and Material's width and height classes. On iOS `horizontal` and\n   * `vertical` are UIKit's size classes; everything else comes from the window\n   * size.\n   *\n   * @since 7.0.0\n   */\n  getSizeClass(): Promise<SizeClass>;\n\n  /**\n   * Read which of the foldable display modes the device offers right now. Both\n   * are `'unsupported'` on iOS and web.\n   *\n   * @since 7.0.0\n   */\n  getDisplayModes(): Promise<DisplayModes>;\n\n  /**\n   * Read where native bars go. Native tab bars and toolbars move to the side of\n   * the display on iPhone Duo, but HTML ones stay put, so use this to move your\n   * own tab bar too.\n   *\n   * @since 7.0.0\n   */\n  getBarPlacement(): Promise<BarPlacement>;\n\n  /**\n   * Move the app to the outer display. Android asks the user to confirm first,\n   * and the promise resolves once the app has moved. Rejects when rear display\n   * mode is not `'available'`. Only on Android.\n   *\n   * @since 7.0.0\n   */\n  startRearDisplay(): Promise<void>;\n\n  /**\n   * Move the app back to the inner display.\n   *\n   * @since 7.0.0\n   */\n  stopRearDisplay(): Promise<void>;\n\n  /**\n   * Show a page on the outer display while the app stays on the inner one. A\n   * relative `url` resolves against the app's own URL, so `'cover.html'` loads a\n   * page bundled with the app. The page runs in its own web view without access\n   * to Capacitor plugins. Calling this again while dual-screen mode is active\n   * replaces the page. Only on Android.\n   *\n   * @since 7.0.0\n   */\n  startDualScreen(options: { url: string }): Promise<void>;\n\n  /**\n   * Close the page on the outer display.\n   *\n   * @since 7.0.0\n   */\n  stopDualScreen(): Promise<void>;\n\n  /**\n   * Listen for fold state changes. On a foldable this also fires when the\n   * device rotates, because `hingeOrientation` and `hingeBounds` rotate with\n   * the window.\n   *\n   * @since 7.0.0\n   */\n  addListener(eventName: 'foldStateChange', listenerFunc: (state: FoldState) => void): Promise<PluginListenerHandle>;\n\n  /**\n   * Listen for hinge angle changes. On Android the hinge sensor only runs while\n   * at least one of these listeners is registered. On iOS it fires on iPhone\n   * Duo (iOS 27.1 or later). Never fires on web.\n   *\n   * @since 7.0.0\n   */\n  addListener(\n    eventName: 'hingeAngleChange',\n    listenerFunc: (event: { angle: number }) => void,\n  ): Promise<PluginListenerHandle>;\n\n  /**\n   * Listen for size class changes, such as unfolding the device, rotating it or\n   * resizing the window. On iOS this fires when UIKit's size classes change\n   * (iOS 17 or later) or the device rotates, so a resize that keeps the same\n   * size classes may not update `widthClass` and `heightClass` until then.\n   *\n   * @since 7.0.0\n   */\n  addListener(\n    eventName: 'sizeClassChange',\n    listenerFunc: (sizeClass: SizeClass) => void,\n  ): Promise<PluginListenerHandle>;\n\n  /**\n   * Listen for changes to the display modes, including a mode ending because\n   * the user folded or unfolded the device. Never fires on iOS and web.\n   *\n   * @since 7.0.0\n   */\n  addListener(\n    eventName: 'displayModeChange',\n    listenerFunc: (modes: DisplayModes) => void,\n  ): Promise<PluginListenerHandle>;\n\n  /**\n   * Listen for the device being folded or unfolded. `folding` turns `true` as\n   * soon as the hinge starts moving and `false` about half a second after it\n   * stops, so an app can pause animations or heavy work while the screen is in\n   * motion. Only fires where a hinge angle is available: Android foldables with\n   * a hinge sensor, and iPhone Duo on iOS 27.1 or later.\n   *\n   * @since 8.2.0\n   */\n  addListener(\n    eventName: 'foldingChange',\n    listenerFunc: (event: { folding: boolean }) => void,\n  ): Promise<PluginListenerHandle>;\n\n  /**\n   * Listen for bar placement changes, such as opening or rotating iPhone Duo.\n   * Only fires on iOS 27.1 or later.\n   *\n   * @since 7.0.0\n   */\n  addListener(\n    eventName: 'barPlacementChange',\n    listenerFunc: (placement: BarPlacement) => void,\n  ): Promise<PluginListenerHandle>;\n}\n"]}

package/ios/Sources/FoldablePlugin/Foldable.swift

@@ -58,6 +58,10 @@ struct UnsupportedFoldProvider: FoldProvider {
         if #available(iOS 27.1, *) {
             return ReservedRegionFoldProvider(source: UIKitFoldSource())
         }
+        #elseif !targetEnvironment(macCatalyst)
+        if #available(iOS 27.1, *) {
+            return MainActor.assumeIsolated { ReservedRegionFoldProvider(source: RuntimeFoldSource()) }
+        }
         #endif
         return UnsupportedFoldProvider()
     }

package/ios/Sources/FoldablePlugin/RuntimeFoldSource.swift

@@ -0,0 +1,104 @@
+import ObjectiveC
+import UIKit
+
+#if !canImport(UIKit, _underlyingVersion: 9127.0.85) && !targetEnvironment(macCatalyst)
+@MainActor
+final class RuntimeFoldSource: @preconcurrency FoldSource {
+    private weak var view: UIView?
+    private var interaction: NSObject?
+    private var status: Int?
+    private var radians: Double?
+
+    private let divisionKind: AnyObject?
+    private let occlusionKind: AnyObject?
+    private let available: Bool
+
+    nonisolated init() {
+        let respondsToRegions = UIView.instancesRespond(to: Selector(("reservedRegionsOfKind:options:")))
+        let kindClass: AnyClass? = NSClassFromString("UIViewReservedRegionKind")
+        let interactionClass: AnyClass? = NSClassFromString("UIHingeInteraction")
+
+        available = respondsToRegions && kindClass != nil && interactionClass != nil
+        divisionKind = kindClass.flatMap { RuntimeFoldSource.kind($0, "divisionRegionKind") }
+        occlusionKind = kindClass.flatMap { RuntimeFoldSource.kind($0, "occlusionRegionKind") }
+    }
+
+    var hasFold: Bool {
+        guard available else { return false }
+        if let status = status, status != 0 { return true }
+        guard let view = view else { return false }
+        return !regions(kind: divisionKind, in: view).isEmpty
+    }
+
+    var hingeStatus: HingeStatus? {
+        switch status {
+        case 1: return .closed
+        case 2: return .partiallyOpen
+        case 3: return .fullyOpen
+        default: return nil
+        }
+    }
+
+    var hingeAngle: Double? {
+        guard let radians = radians, status != nil, status != 0 else { return nil }
+        return radians * 180 / .pi
+    }
+
+    func reservedRegions(in view: UIView) -> [ReservedRegion] {
+        return regions(kind: divisionKind, in: view).map { read($0, as: .division) }
+            + regions(kind: occlusionKind, in: view).map { read($0, as: .occlusion) }
+    }
+
+    func observe(_ view: UIView, onChange: @escaping () -> Void) {
+        self.view = view
+        guard available, let interactionClass = NSClassFromString("UIHingeInteraction") as? NSObject.Type else { return }
+
+        let handler: @convention(block) (AnyObject?, AnyObject?) -> Void = { [weak self] _, update in
+            MainActor.assumeIsolated {
+                self?.read(update)
+                onChange()
+            }
+        }
+        let allocated = interactionClass.perform(Selector(("alloc")))?.takeUnretainedValue() as? NSObject
+        let interaction = allocated?
+            .perform(Selector(("initWithUpdateHandler:")), with: handler)?
+            .takeUnretainedValue() as? NSObject
+        guard let interaction = interaction else { return }
+
+        view.perform(Selector(("addInteraction:")), with: interaction)
+        self.interaction = interaction
+    }
+
+    private func read(_ update: AnyObject?) {
+        guard let hinge = update?.value(forKey: "hinge") as AnyObject? else {
+            status = nil
+            radians = nil
+            return
+        }
+        status = (hinge.value(forKey: "status") as? NSNumber)?.intValue
+        radians = (hinge.value(forKey: "angle") as? NSNumber)?.doubleValue
+    }
+
+    private func regions(kind: AnyObject?, in view: UIView) -> [AnyObject] {
+        guard available, let kind = kind else { return [] }
+        let selector = Selector(("reservedRegionsOfKind:options:"))
+        typealias Call = @convention(c) (AnyObject, Selector, AnyObject, UInt) -> AnyObject?
+        guard let method = view.method(for: selector) else { return [] }
+        let call = unsafeBitCast(method, to: Call.self)
+        return call(view, selector, kind, 1) as? [AnyObject] ?? []
+    }
+
+    private func read(_ region: AnyObject, as kind: ReservedRegion.Kind) -> ReservedRegion {
+        let frame = (region.value(forKey: "frame") as? NSValue)?.cgRectValue ?? .zero
+        let margins = (region.value(forKey: "margins") as? NSValue)?.uiEdgeInsetsValue ?? .zero
+        let isActive = (region.value(forKey: "isActive") as? NSNumber)?.boolValue ?? false
+        return ReservedRegion(kind: kind, frame: frame, margins: margins, isActive: isActive)
+    }
+
+    nonisolated private static func kind(_ owner: AnyClass, _ name: String) -> AnyObject? {
+        let selector = Selector((name))
+        guard owner.responds(to: selector) else { return nil }
+        return (owner as AnyObject).perform(selector)?.takeUnretainedValue()
+    }
+}
+#endif

package/package.json

@@ -1,10 +1,20 @@
 {
   "name": "@erkamyaman/capacitor-foldable",
-  "version": "8.3.3",
+  "version": "8.4.0",
   "description": "Fold-state and dual-display APIs for foldable devices in Capacitor apps",
   "main": "dist/plugin.cjs.js",
   "module": "dist/esm/index.js",
   "types": "dist/esm/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/esm/index.d.ts",
+      "import": "./dist/esm/index.js",
+      "require": "./dist/plugin.cjs.js"
+    },
+    "./ionic-tabs.css": "./ionic-tabs.css",
+    "./ionic-tabs-ios26.css": "./ionic-tabs-ios26.css",
+    "./package.json": "./package.json"
+  },
   "unpkg": "dist/plugin.js",
   "files": [
     "android/build.gradle",

package/skills/capacitor-foldable/references/ionic.md

@@ -21,6 +21,19 @@ That turns `ion-tabs` into a side pill exactly where native bars go, and only wh
 
 React and Vue import it from the entry file as usual, since their bundlers ship type shims for CSS.
 
+## Projecting Ionic controls into native UI
+
+Moving the tab bar with CSS is one answer. The other is [`@rdlabo/ionic-theme-ios27`](https://github.com/rdlabo-dev/ionic-theme-ios27), which brings SwiftUI-like UI rearrangement to Ionic apps: it repositions existing `ion-back-button`, `ion-buttons`, `ion-button` and `ion-tab-bar` controls, then projects them into native UI. An app can adopt its Vertical Bars while keeping its existing theme.
+
+The split is clean: this plugin provides device state, the theme handles rearrangement and rendering. The app passes what it reads here into the theme, and the theme decides what to draw.
+
+For setup, send the reader to the theme's own documentation rather than duplicating it here:
+
+- [iPhone Duo with your existing theme](https://docs.rdlabo.dev/projects/ionic-theme-ios27/docs/iphone-duo-with-original-theme)
+- [Vertical Bars reference](https://docs.rdlabo.dev/projects/ionic-theme-ios27/docs/vertical-bars)
+
+Use the CSS stylesheet above when you want Ionic's own tab bar moved, and the theme when you want the controls rendered natively.
+
 ## A fold fires a keyboard event
 
 iPhone Duo sends a keyboard event when the device folds. Ionic's keyboard controller measures the app container's height the first time the keyboard opens and caches it, then waits for that exact height before showing the tab bar again. After a fold the height no longer matches, so the bar never comes back. Opt in to the fix: