Apple has reportedly revised its software development process for iOS 28, iPadOS 28 and macOS 28, giving engineers additional time to experiment with features before integrating them into the operating systems. The changes come as the company explores a more ambitious AI strategy that could turn Siri into a more capable autonomous assistant.
Apple is reportedly making significant changes to how it develops its next-generation operating systems, providing software engineers with additional time to explore new features and ideas.
According to Bloomberg journalist Mark Gurman, the company has adjusted the first major development stage for iOS 28, iPadOS 28 and macOS 28.
Under Apple’s usual development schedule, each milestone reportedly consists of four weeks of coding followed by four weeks of feature convergence, during which new software components are integrated into the operating system.
For the initial development stage of its 2027 software updates, however, Apple reportedly extended the coding and experimentation period to six weeks while reducing the convergence phase to two weeks.
The change preserves the overall eight-week milestone but shifts more time toward early feature development.
Gurman reported the changes in his November 8, 2026, Power On newsletter, which also discusses Apple’s interest in making Siri more agentic.
The broader AI ambition reportedly involves turning Siri into an assistant capable of completing more complex tasks on behalf of users.
However, Bloomberg has not identified specific iOS 28 features in the supplied reporting, and Apple has not publicly confirmed that the revised development schedule is directly tied to a particular Siri upgrade.
Apple Revises iOS 28 Software Development Process
Apple reportedly divides the development of its major annual operating system releases into three primary milestones.
These stages are known internally as M1, M2 and M3.
Each milestone generally follows a structured process designed to balance the development of new features with the work required to integrate and stabilise them.
According to Gurman, Apple’s traditional milestone schedule consists of eight weeks.
Four weeks are typically dedicated to coding, exploration and feature development, followed by another four weeks of convergence.
Convergence refers to the process of bringing separately developed features into the wider operating system.
This can involve integrating code, addressing compatibility issues and ensuring that different components work together.
For the first milestone of iOS 28 and related updates, Apple reportedly changed that arrangement.
Engineers were given six weeks for development and experimentation, followed by two weeks of convergence.
The adjustment gives the team two additional weeks for early-stage feature work without increasing the milestone’s overall length.
Also Read: Apple Reportedly Cuts AI Spending Limits for Engineers as Company Seeks to Control CostsiOS 28 Development Schedule: What Changed?
The reported shift can be summarised through a comparison of Apple’s traditional process and the revised M1 schedule.
| Development phase | Traditional milestone | Revised iOS 28 M1 |
|---|---|---|
| Coding and feature development | 4 weeks | 6 weeks |
| Feature convergence | 4 weeks | 2 weeks |
| Total milestone duration | 8 weeks | 8 weeks |
| Share dedicated to development | 50% | 75% |
| Share dedicated to convergence | 50% | 25% |
Source: Bloomberg’s November 8, 2026, Power On reporting. The change is specifically reported for M1; the same adjustment has not been confirmed for M2 or M3.
The revised schedule increases the time available for coding and feature exploration by 50 percent relative to the traditional four-week allocation.
At the same time, the convergence window is reduced by 50 percent.
This does not mean that Apple’s overall software development cycle has been shortened.
Instead, the company appears to be reallocating time within an existing milestone.
ALso Read: iPhone 18e Leak Tips A20 Chip and Possible 24MP Selfie Camera, but 60Hz Display May StayWhat Are Apple’s M1, M2 and M3 Milestones?
According to Gurman, Apple organises its annual operating system development around three major milestones.
These milestones provide internal checkpoints for developing, integrating and refining software features.
M1: Early Feature Development
M1 is the initial major stage in the process.
It provides engineers with an opportunity to explore new ideas, develop functionality and begin bringing features into the operating system.
The reported change for iOS 28 occurred during this stage.
By extending the development period, Apple gave engineers more time to experiment before the first major integration deadline.
M2: Continued Development and Integration
M2 represents a later stage in the software development cycle.
By this point, engineers may need to manage functionality developed during the earlier milestone while continuing work on additional features.
The supplied reporting does not confirm a change to M2’s usual schedule.
M3: Further Integration and Refinement
M3 is another major milestone in Apple’s annual development process.
As the cycle progresses, the need to integrate features, resolve bugs and improve stability becomes increasingly important.
However, the supplied information does not disclose the precise current schedules for M2 and M3.
It would therefore be premature to assume that Apple has adopted the six-week coding structure for every milestone.
Also Read: XRP Ledger Activates Security Fix for Token Minting Vulnerability, Native XRP UnaffectedApple Engineers Reportedly Welcome the Schedule Change
According to Bloomberg, employees have responded positively to the revised M1 development schedule.
The additional coding period reportedly gives engineers more time to explore ideas before committing them to the operating system.
Under the traditional structure, developers had four weeks to complete initial feature work before moving into convergence.
Extending that window to six weeks may create more opportunities for experimentation.
Engineers can potentially explore alternative implementations, refine early concepts and resolve technical issues before features are integrated more broadly.
The reported employee response suggests that some staff consider the change beneficial for creative software development.
However, this does not establish that the new schedule will automatically produce more features or higher-quality releases.
The outcome will depend on execution, engineering resources and the complexity of the software being developed.
Why Apple May Benefit From a Longer Coding Window
Large operating systems require coordination across numerous software components.
New functionality may depend on application frameworks, system services, hardware capabilities and security mechanisms.
Integrating features too early can create challenges when important technical decisions are still being evaluated.
Providing engineers with additional time during the earliest milestone could allow more ideas to be tested before becoming part of the wider operating system.
The timing is also relevant.
Early in a development cycle, there are generally fewer newly introduced features requiring integration than during later stages.
As work progresses, engineers must account for software already added during previous milestones.
That can increase the importance of convergence and stability testing.
Apple’s reported adjustment appears to take advantage of the relative flexibility available at the beginning of the cycle.
However, shortening an integration period can also create pressure if newly developed features are not sufficiently mature.
The benefits will depend on how carefully Apple balances experimentation with engineering discipline.
Also Read: WhatsApp for Android Could Soon Let Users Preview Chats Without Opening ConversationsiOS 28 and iPadOS 28 Reportedly Carry the Codename Bell
The supplied reporting identifies Bell as the internal codename associated with Apple’s iOS 28 and iPadOS 28 development.
Apple uses internal project identifiers during software development, although these names do not necessarily appear in public product announcements.
The codename is relevant mainly as a reference to the development programme discussed by Bloomberg.
It does not reveal the software’s interface, feature set or final capabilities.
Apple has not officially detailed the consumer-facing features of iOS 28 in the information supplied.
macOS 28 Reportedly Uses the Codename Poppy
The same reporting identifies Poppy as the internal codename for macOS 28.
Like iOS 28 and iPadOS 28, the Mac operating system is reportedly part of the revised early development process.
This indicates that the scheduling changes extend beyond Apple’s smartphone software.
However, the supplied report does not establish that identical features are being developed for iPhone, iPad and Mac.
The three operating systems serve different device categories and may require distinct implementations of shared technologies.
No specific macOS 28 feature has been confirmed in the source excerpt.
Apple Is Also Exploring a More Agentic Siri
The development changes come amid separate reporting about Apple’s ambitions for Siri.
According to Bloomberg’s Power On coverage, Apple’s leadership wants a more capable AI assistant that can perform tasks rather than simply respond to isolated commands.
The concept is often described as agentic AI.
An AI agent can potentially interpret a user’s objective, coordinate supported tools and complete multiple steps toward a result.
For example, a future assistant might be designed to organise information from several applications and prepare actions based on a broader request.
Such examples illustrate the general capabilities of agentic AI rather than confirmed features for Siri.
The supplied reporting does not specify which applications Siri would be able to control or which actions it could perform autonomously.
It also does not establish whether the feature will launch as part of iOS 28.
Also Read: Lumio Adds Flix to TLDR, Brings YouTube Shorts Feed for Movies, Shows and Music DiscoveryWhat Would Make Siri More Agentic?
Traditional digital assistants are generally designed around specific commands.
Users may ask for information, set timers, create reminders or open applications.
Agentic systems aim to handle more complex instructions involving several related steps.
For Siri, the shift could potentially involve stronger contextual understanding, improved application integration and more sophisticated task management.
Traditional Siri vs a Potential Agentic Siri
| Capability | Traditional assistant approach | Agentic AI approach |
|---|---|---|
| User interaction | Individual commands | Broader user objectives |
| Task execution | Predefined supported actions | Potentially coordinated multi-step actions |
| Context handling | Depends on feature | Greater emphasis on context |
| App integration | Existing supported interfaces | Could involve deeper tool integration |
| Follow-up actions | Often require additional requests | May coordinate supported steps |
| User permissions | Existing operating system controls | Would require appropriate authorisation and safeguards |
The agentic column describes general AI-agent capabilities, not features confirmed for Apple’s next Siri release.
A more capable assistant would also need to manage privacy, security and user permissions carefully.
Tasks involving messages, personal files, financial information or account settings would require appropriate safeguards.
The supplied report does not explain how Apple intends to implement those controls.
Is Apple’s New iOS 28 Schedule Linked to Siri Development?
The revised development schedule and reported agentic Siri ambitions are discussed in the same Bloomberg newsletter.
However, that does not establish a direct causal relationship.
The schedule change concerns the early engineering process for several operating systems.
The Siri strategy concerns Apple’s broader direction in artificial intelligence.
The additional coding period could potentially provide flexibility for complex software projects, including AI-related functionality.
Nevertheless, Bloomberg has not identified a specific Siri feature that resulted from the revised M1 schedule in the supplied reporting.
It is therefore more accurate to describe the developments as occurring within Apple’s wider software strategy rather than claiming that the schedule was changed specifically to accelerate Siri.
When Will Apple Release iOS 28?
Based on Apple’s expected annual software cycle, iOS 28 is anticipated to enter public or developer beta testing around June 2027.
A stable release is expected around September 2027.
These dates reflect the schedule described in the supplied reporting and should be treated as expectations rather than officially announced deadlines.
Apple has not confirmed an exact iOS 28 release date in the available source material.
The company also has not disclosed the complete list of compatible iPhones or the update’s final features.
Expected Apple Software Timeline
| Software | Reported development status | Expected availability |
|---|---|---|
| iOS 28 | Early M1 milestone completed | Beta around June 2027; release around September 2027 |
| iPadOS 28 | Early development under Bell | Exact dates not confirmed |
| macOS 28 | Early development under Poppy | Exact dates not confirmed |
| More advanced Siri | Reportedly under strategic consideration | No confirmed release date |
The revised milestone schedule should not be interpreted as evidence of an earlier public release.
Will iOS 28 Introduce Major New AI Features?
The supplied Bloomberg report does not reveal specific iOS 28 features.
Although Apple is reportedly pursuing a more ambitious AI strategy, the source does not confirm a full agentic Siri rollout with the next operating system.
The company could introduce new AI functionality through different updates or release phases.
However, assigning particular features to iOS 28 without supporting evidence would be speculative.
The most reliable conclusion is that Apple is adjusting its software development process while exploring more advanced AI capabilities.
What the Changes Mean for iPhone and Mac Users
For consumers, the revised development process is primarily an internal engineering change.
Users are unlikely to notice the milestone structure directly.
Its importance lies in how it may influence the features and software quality of future releases.
Additional experimentation time could help engineers develop and refine new functionality before integration.
However, the result will ultimately be judged through the final software’s reliability, usability and capabilities.
The reported Siri initiative could have a more visible effect if Apple successfully introduces a system capable of carrying out complex user requests.
For now, neither the revised schedule nor the broader AI ambitions establish a confirmed list of new features.
Also Read: Hackers Exploited Chrome and Qualcomm GPU Flaws to Target Android Phones, Sekoia ReportsWhat Happens Next?
Apple’s revised approach suggests the company is reassessing how much time engineers should spend creating features during the earliest stage of an operating system’s development.
The shift from a four-week development window to six weeks gives engineers more flexibility without extending the total M1 milestone.
The reported positive response from employees indicates that some consider the change helpful for experimentation.
At the same time, Apple’s leadership is reportedly pushing for a more ambitious Siri capable of moving toward agentic AI.
The confirmed distinction in the supplied reporting is that Apple’s M1 schedule has changed, while specific iOS 28 features and the release timing of an agentic Siri remain unannounced.
Further details may emerge as Apple progresses through its software milestones and approaches its expected 2027 developer conference.
TechLayers will continue following Apple’s AI strategy, iOS development and upcoming software announcements.
Have a story tip or feedback? Contact [email protected].
© TechLayers. Original editorial content.
