Apple changed the development process of iOS 28

Apple changed the development schedule for iOS 28 and other next-generation operating systems. With this change, engineers will have more time to discover and develop new features.

Cupertino-based technology giant Apple has made a remarkable change in strategy in the development calendar of the mobile operating system that powers iPhone models. In the preparation phase of the highly anticipated iOS 28 release, the company decided to narrow down the integration phase where the codes are incorporated into the operating system, while giving software engineers more time to design and discover new capabilities.

New Time Distribution in the Eight-Week Cycle

Apple traditionally divided the eight-week development periods, which it named with codes such as M1, M2 and M3, into two equal parts. In this order, the first four weeks were devoted to basic code writing and discovery, and the remaining four weeks were devoted to the process known as "convergence", during which innovations were integrated into the main system. According to the shared information, this balance has changed significantly in the first stage of iOS 28. The company restructured the schedule without extending the total time, increasing the coding and discovery share to six weeks in the first phase; It reduced the integration period to two weeks. It is not yet clear whether this formula, which is currently only applied in the first development phase, will be permanent in the following stages.

User Experience and Implications for System Stability

The extra two weeks of thinking and prototyping space given to developers paves the way for the innovations to be introduced with iOS 28 to be processed in a much more mature and detailed manner. Although it is aimed for engineers to develop ambitious ideas early, it is emphasized that this table does not directly mean a more error-free or richer version. Because the integration window is compressed to two weeks, it may create new technical problems in bringing complex code blocks together in a stable structure. How the final picture will be shaped for users will be determined by the extent to which Apple can maintain system stability during the shrinking integration process.