Apple is changing how its engineers develop major operating system updates. The company has adjusted its early development schedule for iOS 28, iPadOS 28, and macOS 28.
The new approach gives engineers more time to explore ideas before integrating features into the software.
Moreover, the changes could improve the quality of future updates while encouraging greater creativity within Apple’s development teams.
Apple Extends Coding Time for iOS 28
Apple traditionally organizes its operating system development around three major milestones: M1, M2, and M3.
Each milestone normally lasts eight weeks. Engineers spend four weeks developing features, followed by four weeks integrating their work.
However, Apple has introduced a different schedule for the first milestone of its upcoming operating systems.
Under the revised plan, engineers receive six weeks for coding and feature development. Meanwhile, the integration period drops to two weeks.
This adjustment gives developers an additional two weeks to refine ideas before finalizing their work.
Changes Affect iPadOS 28 and macOS 28
The revised schedule covers several major software projects.
Apple internally refers to iOS 28 and iPadOS 28 as “Bell,” while macOS 28 carries the codename “Poppy.”
According to reports, the company has already completed the first development milestone under the new schedule.
Furthermore, employees have reportedly welcomed the adjustment because it provides greater freedom during the creative process.
Engineers can now spend more time experimenting with features before preparing them for integration.
As a result, Apple hopes to improve the overall quality of its upcoming software.
Why Apple Is Changing Its Development Process
Software development becomes increasingly complex as projects move closer to completion.
During later milestones, engineers must manage existing features alongside newly developed additions.
Consequently, software integration requires greater attention as the development cycle progresses.
However, the earliest milestone involves fewer completed features, making it easier to dedicate additional time to coding.
Apple appears to be taking advantage of this flexibility without extending the overall eight-week milestone.
What This Means for Future Apple Updates
The schedule change reflects Apple’s effort to balance creativity with software reliability.
Additionally, giving engineers more time to develop ideas could lead to better-designed features and fewer rushed decisions.
However, Apple has not confirmed whether the revised approach will produce noticeable improvements for users.
For now, the adjustment applies to the early development stage of its next-generation operating systems.
Ultimately, Apple’s experiment could influence how the company organizes future software updates if the new schedule proves successful.
