Urgent.News

What's breaking now, across thousands of outlets.

Tech

What iOS Developers Need to Change in their Apps to prepare for the iPhone Duo

With the upcoming introduction of the foldable iPhone Duo, iOS developers will need to adapt their apps to ensure they work correctly across the new device's outer display, larger inner display, and partially folded states. Developers will also need to account changes to navigation and toolbars, camera behavior, and new reserved regions. By Sergio De Simone

As Apple prepares to unveil the foldable iPhone Duo, iOS developers must make adjustments to their applications to ensure compatibility across the device's outer display, inner display, and partially folded states. This includes addressing navigation and toolbars, camera behavior, and new reserved regions. Developers are advised to use Xcode 27.1, avoid fixed screen dimensions, and instead size views relative to their containers.

Standard layout containers, such as SwiftUI stacks, navigation, and split views, should be utilized, along with size classes to adapt to different screen sizes. Custom navigation and toolbars created with UIToolbar, UINavigationBar, or UITabBar may require modifications to adapt properly. iPhone Duo also introduces new reserved regions, which include screen folds and areas occluded by hardware elements like the camera.

Developers can utilize reservedRegions(kind:options:layoutDirectionBehavior:) in SwiftUI and reservedRegions(kind:options:) in UIKit to handle these regions. Finally, developers should be prepared for the fact that iPhone Duo supports multiple camera configurations, which can change based on device orientation and camera usage.

Written by urgent.news from InfoQ's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at infoq.com →

More in Tech

Cutting a Video Clip Without Touching the Original: Four Workflows Compared

Shortening a long recording into a focused snippet looks simple until you actually try it. The original file is large, you may be working on a machine without a heavy editor installed, and the moment…

  • Workflow 1 uses desktop editors like Premiere Pro or Shotcut for visual feedback and precise cuts.
  • Workflow 2 employs FFmpeg command-line tool with -c copy flag to preserve original video bytes.
  • Workflow 4 utilizes browser-based tools that trim videos locally without altering the original file.

More from Thursday 24 September →