Apple Gives iOS 28 More Early Coding Time

Apple has shifted its iOS 28 development schedule to allow six weeks of feature coding in its M1 milestone.

Updated on Nov. 8, 2026 in Remote Work

Apple Gives iOS 28 More Early Coding Time

Apple has adjusted its development schedule for iOS 28, iPadOS 28, and macOS 28 to give engineers six weeks of coding in the M1 milestone instead of the usual four. Reporting by Gurman in his Power On newsletter described the change, which shortens the convergence phase from four weeks to two.

Why it matters

Annual operating system updates depend on tightly planned development stages, and giving early-stage engineers more time changes how features are built before they are locked down. The adjustment also reflects an internal effort to improve feature quality.

Each development stage normally runs eight weeks, split into four weeks of coding and four weeks of convergence. The adjusted M1 stage allocates six weeks to coding and two weeks to convergence, and the schedule covers three milestones per annual cycle.

The players

Apple

Apple is a technology company best known for its iPhone, Mac computers, and the iOS and macOS operating systems.

Mark Gurman

Mark Gurman is a Bloomberg journalist who covers Apple and writes the Power On newsletter.

The details

The change applies to iOS 28, iPadOS 28 (internal name Bell), and macOS 28 (internal name Poppy). Convergence, the stage where new features are integrated into the operating system, was shortened in M1 so engineers have more time to develop and refine ideas early.

The M1 milestone of the iOS 28 cycle has already passed.
Gurman reported the schedule change in his Power On newsletter on Sunday.

Market Landscape

Apple's annual cycle of three milestones (M1, M2, M3) sets the pace for its operating system releases each year. Shifting more time into early-stage coding alters that established rhythm without changing the overall structure of the cycle.

For iPhone and Mac owners, the change may mean features are refined more before release, though the extraction does not state how it will affect update timing. Users waiting on specific features should watch for the next milestone announcements.

The takeaway

Giving engineers more early development time reflects a shift toward building features with greater care before they are finalized. This approach may matter most for the quality of features that ship in later stages of the cycle.