Recent reports have revealed a strategic change in Apple's methodology for developing its upcoming operating systems, specifically iOS 28 and macOS 28. According to the information provided, the company has decided to adjust the structure of the development phases it follows annually, which traditionally relied on an equal split between the programming and integration phases.
What has changed in the development process?
Previously, Apple divided the development cycle into phases consisting of four weeks for coding, followed by four weeks for what is known as the "Convergence" phase, which is the period dedicated to integrating new features into the system and ensuring their stability. In the current iOS 28 development cycle, this equation has been adjusted to six weeks dedicated to programming, exploration, and feature development, compared to only two weeks for the integration phase.
Why does this change matter?
This adjustment comes in response to software engineers' desire for more time to innovate. According to sources, employees have welcomed this move, noting that it gives them greater flexibility to propose and test ideas before needing to finalize features in the system. This approach reflects an attempt by Apple to reduce time pressures that may limit technical creativity in the early stages of the system's lifecycle.
What does this mean for users?
Although Apple has not yet revealed specific features for iOS 28, this change indicates a greater focus on the conceptualization and initial development phase. The company is expected to follow its usual schedule, with beta versions expected to be released in June, and the official public launch scheduled for September of next year. The open question remains whether shortening the integration period will affect system stability or performance quality at launch, which the coming months will reveal.