Apple said its development cycle for iOS 28 and macOS 28 will now feature a six‑week coding phase followed by a two‑week convergence period, giving engineers extra time to build and polish new features.

Apple announced a tweak to its upcoming iOS 28 and macOS 28 development timeline, extending the coding window to six weeks and adding a two‑week convergence phase for integration and polishing.

What the new timeline looks like

The revised schedule splits the development cycle into a six‑week “coding” period, during which engineers write and test new code, followed by a two‑week “convergence” stage that focuses on integrating features, fixing edge‑case bugs, and ensuring a smooth hand‑off to quality assurance.

Why Apple made the change

Apple’s engineering teams cited the growing complexity of cross‑platform features as the primary driver. By allocating dedicated time for convergence, developers can address compatibility issues between iOS and macOS earlier, reducing last‑minute patches.

Potential impact on developers

Third‑party developers may see a more stable beta environment, as Apple’s internal polishing should surface fewer critical bugs before public releases. The extra convergence window also gives external teams a clearer timeline for feature finalization.

  • Six‑week coding phase for core feature development
  • Two‑week convergence phase for integration and polishing
  • Earlier internal testing to catch cross‑platform issues

For more context on Apple’s development strategy, see the Apple page on Momentum and explore related stories in the Product Design section.

Apple’s updated process reflects a broader industry trend toward longer integration periods, aiming to deliver more reliable operating system updates.

Read the full report on MacRumors coverage of Apple tweaks iOS 28 development process.