I Asked Craig Federighi Why iPhone Still Can’t Swipe Back from the Right

Main technological concepts & product features discussed

Foldable iPhone “Duo” — display continuity & animation goal

• The outer screen is described as a translucent window that shows inner display content as the phone folds/unfolds.
• The intent is a subconscious, automatically perceived transition—so the screen feels like it reveals what is underneath.
• Core concept: continuity of experience between the closed and unfolded states.

New developer API — hinge angle / device opening state

• Developers can access a hinge angle reading.
• Accuracy is stated as within ~5 degrees, and values are smoothed.
• Recommended developer approach:
  • Frameworks provide a standard “device state” so apps can adapt without dealing with raw degree values.
  • Examples of framework states include:
    • Book mode
    • Tent mode
    • Device resting on a table
  • Goal: consistent behavior via framework-level state rather than bespoke angle handling.

Gesture & interaction model — swipe-back behavior

• The discussion references complaints about iOS swipe-back consistency.
• Change noted in iOS 26:
  • Instead of only swiping from the leading edge (left), users can swipe from anywhere on the display in non-ambiguous situations.
• Gesture reservation:
  • The edge gesture remains reserved for unambiguous “back” behavior (where confusion with scrolling or other interactions would be likely).
• For the Duo split view, there are:
  • Touch controls/buttons along edges
  • Edge swipe gestures
• Rationale against making both sides behave as “back”:
  • It would break spatial consistency
  • It would remove the ability to navigate forward, because one edge must map to forward navigation and the other to back navigation.

Dual-workspace split-screen model — two independent “desktops”

• When open, the Duo split view is described as two independent workspaces (left and right).
• Each side includes:
  • its own home screen
  • its own app switcher
• Users can pin the split (treating it as a single set), and unpin to temporarily move away and later return to the same configuration.
• Design goal: enable fast, natural switching between tasks while keeping spatial perception intuitive.

Developer adoption / app adaptation strategy

• Developer concern: adaptation may require more work due to large-screen and foldable layout complexity.
• Apple’s argument for manageability:
  • Many apps rely on high-level frameworks like UIKit / SwiftUI, which abstract layout complexity.
  • Higher-level constructs increasingly auto-adapt.
• AI-assisted tooling mentioned:
  • Providing skill definitions/documentation so Xcode coding models can help update apps for new formats.
  • WWDC work reportedly included resizing support, and developers can adapt apps with AI tools largely automatically.

Cross-platform framework concern (React Native / Flutter, etc.)

• The content acknowledges that many developers (including large internet companies) may not use only Apple frameworks.
• Examples cited: React Native, Flutter, and other cross-platform approaches.
• Comparison to Android:
  • Foldables exist there too, but adaptation has been an ongoing challenge.
• Apple’s claim:
  • Apple’s platform has historically handled form-factor adaptation better (example given: iPad apps generally look and behave appropriately rather than appearing as stretched phone UIs).
• Goal from the start:
  • Establish a high standard example so Duo apps demonstrate the best possible experience.

Reviews / guides / tutorials

• No direct “review” or step-by-step tutorial content is included.
• The content functions more as a developer-focused technical explanation, covering:
  • APIs
  • accuracy and smoothing behavior
  • framework device-state behavior
  • gesture model
  • developer tooling approach

Main speakers / sources

• Craig Federighi (the interviewee, referenced in the video title)
• An Apple interviewer / Apple representative (the other speaker who asks questions and discusses iOS 26, gestures, and developer APIs)