My initial reaction to the latest Copilot update from the Microsoft Store was one of disbelief. Anticipating an innovative enhancement, I was met instead with an app that has been redesigned yet again to function as a WebView-based application. This recurring theme of Microsoft attempting to redefine Copilot for Windows has become frustratingly familiar.
Before delving deeper into my distaste for web-based applications, let’s clarify what constitutes a true ‘native’ app. Essentially, a native app is one that does not rely on technology such as Microsoft Edge-based WebView, JavaScript, or Electron for its operation.
In the context of Windows, native applications are ideally developed using frameworks like WinUI or the traditional Win32 architecture. To summarize, anything that possesses a modern appearance and isn’t web-dependent can be considered native as we move through 2026.
The Hybrid Nature of Copilot for Windows 11

After testing the Copilot update from the Insider Program, I can confirm it operates as a web application. This assertion is reinforced by the Task Manager, which reveals various background processes, including Renderer, GPU Process, and Utility: Network Service.

Many of these processes are integral to Microsoft Edge, indicating a structure reminiscent of web apps like WhatsApp when viewed in Task Manager. Notably, if you navigate to the Copilot settings, you’ll discover the version number aligns closely with that of Microsoft Edge.

According to information from Windows Latest, the revised Copilot might present as a sophisticated web app encapsulated within a desktop environment using Edge/WebView components. This suggests that while it has a native-looking shell, the application itself still accesses copilot.microsoft.com.
Interestingly, this new iteration of Copilot runs as swiftly as its predecessor. In fact, it opens more quickly than earlier native versions, raising questions about the current efficacy of WinUI. Despite this speed, the fundamental nature of Copilot remains web-based, prompting criticism that Windows should prioritize native apps over web applications.
The Ongoing Struggle with Native vs. Web Frameworks
Copilot’s evolution on Windows has been tumultuous, not from an emotional standpoint, but due to its integration within Windows 11 and Windows 10. Initially announced on May 23, 2023, as a sidebar accessible from the taskbar or via Win + C, it was later revealed to be a new interface for Bing Chat delivered through Edge/WebView2, rather than a truly native Windows experience.

By March 2024, Microsoft introduced an updated Copilot that could toggle between the previous docked mode and a flexible, resizable application window. This marked the shift from a classic sidebar to a more comprehensive Progressive Web App (PWA) format.

Following user feedback, Microsoft attempted to deploy a ‘native’ Copilot version, but it turned out to be merely a web-based solution operating within a native shell. This adaptation consumed more memory and sparked user outrage, prompting the company to respond with a more legitimate native app.
Transition to a Native Copilot App in 2025
Under the leadership of Mustafa Suleyman, who took the reins from Mikhail Parakhin, Microsoft pivoted towards developing a genuinely native Copilot app in 2025.
Tests from Windows Latest confirmed that this new native version does not leverage web components at all.

This truly native Copilot app began distribution in March 2025. Although some portions of the app, like the ‘Pages’ feature, employed a web shell, the majority of Copilot’s functionality remained firmly native, which placated users for a time.
However, developments have transpired recently. Windows Latest now observes that the Copilot for Windows 11 is reverting to a full web experience, effectively eliminating the native application altogether.
This modification is set to rollout to non-Insiders shortly, leaving little hope for reverting back to a fully native experience.
Leave a Reply