Developer Discusses the Reason Behind Windows 11 Favoring Web Apps Over Native Applications

After WhatsApp controversially transitioned its native Windows application to a web-based format, widespread backlash was directed at Meta. Criticism was warranted, as the change seemed half-hearted, resulting in a resource-hungry downgrade that stripped away any semblance of a native experience for Windows users.

However, this situation exposes a more complex reality. Meta’s motivation to maintain a native Windows app was limited; the company seldom updated the app, failed to offer feature parity, and ultimately opted for the more practical web version. The underlying factor at play is the economic advantage of web apps compared to native ones. Developers face challenges in securing long-term support from Microsoft’s UI frameworks, which remains precarious.

A recent insight from Alexander Ovchinnikov, a developer and longtime reader of Windows Latest, highlights the prevalent sentiments among developers. Unlike macOS—where native applications are consistently developed despite a smaller user base—developer enthusiasm for web apps on Windows stems from a profound lack of trust in the platform.

Microsoft’s introduction of various so-called “future”frameworks has been inconsistent, often abandoning them after limited use. From WPF and Silverlight to UWP and now WinUI 3, this pattern has led developers to question the longevity of each new framework. As Ovchinnikov notes, many developers now perceive that the current framework may not endure long enough to merit investment.

For decades, Microsoft has lacked a coherent GUI strategy. The broad array of frameworks available puts Windows developers in a difficult position without clear guidance on which framework to adopt for app development.

From Clarity to Confusion: The Evolving Landscape of Windows Development

Once upon a time, Windows app development had a straightforward approach; developers relied predominantly on Win32. This singular API provided a solid foundation, resulting in a consistent and reliable development experience.

Charles Petzold’s seminal work, “Programming Windows”, was pivotal in this regard—it demystified Windows app development, allowing developers to invest knowing that the platform’s stability was not in question. This environment fostered trust, thereby facilitating ecosystem growth.

Rather than evolving Win32, Microsoft continuously introduced new alternatives. MFC entered as a C++ wrapper, followed by WinForms for. NET enthusiasts. The arrival of WPF brought XAML and hardware acceleration, while Silverlight aimed at cross-platform potential. Over the years, WinRT and UWP were marketed as unified solutions during the Windows 8 and 10 phases, yet none fully achieved industry-wide adoption. Now, WinUI 3 promises modernization but struggles to inspire the confidence developers once had in earlier frameworks.

The cycle of introducing a new framework, motivating developers to invest time in it, only to shift focus again, has eroded commitment. Developers today respond with skepticism—if past frameworks have not endured, why should the current one?

Today’s developers face a confusing landscape. Recommendations vary widely based on individual preference, with some advocating for Win32 or WPF for stability, while others lean towards WinUI 3, which lacks broad trust. The existence of multi-platform solutions like MAUI and web options using Electron or PWAs contributes further to the indecision. Instead of clarity, developers are faced with overwhelming uncertainty.

The Rise of Web Apps in Windows Development

Many widely-used applications on Windows, including WhatsApp, Discord, and Zoom, are not genuinely native. Instead, they operate as web apps, leveraging components like WebView2, which integrates the Chromium engine for a more consistent experience.

The simplification in creating web applications is a game-changer. This model enables apps to be deployable across various operating systems without the need for separate codebases. Frameworks like Electron and Progressive Web Apps (PWAs) expedite distribution while mitigating maintenance costs. Businesses are increasingly attracted to these advantages.

However, this shift comes with drawbacks. Web apps tend to be resource-intensive, typically consuming more RAM and often feeling less responsive compared to their native counterparts. The experience suffers due to reduced integration with the operating system, with multiple Electron apps overwhelming system resources.

WhatsApp for Windows RAM usage — “WhatsApp” current version and “WhatsApp Beta” the older UPW/WinUI version

In contrast, on macOS and iOS, developers still prioritize creating native applications. Apple has maintained consistency in its frameworks, such as Cocoa and AppKit, providing developers with clarity and assurance that their tools will remain relevant.

Windows, unfortunately, lacks this level of clarity. This uncertainty prompts developers to opt for web solutions, accepting their inherent performance limitations to avoid the risk associated with fluctuating Microsoft strategies.

Microsoft’s Attempt to Rekindle Developer Trust

There are indications that Microsoft recognizes the challenges it faces. Recent initiatives signal a move towards enhancing performance while decreasing reliance on web components—building more native Windows experiences. Developer Rudy Huyn’s recent call to action for Windows devs to embrace native app-making has been received positively.

Yet, resolving the application issues represents only part of the challenge. Even if Microsoft enhances its native offerings, apprehension among developers is likely to persist. This caution stems not from the capabilities of WinUI 3 today, but from historical patterns of instability that make developers reluctant to engage.

To foster renewed developer confidence, Microsoft must commit to a single framework and present a clear, long-term direction for developers. Consistent support and mature development processes will become indispensable in regaining developer faith.

Consistency: The Core Challenge

Microsoft possesses exceptional engineering talent and a strong legacy in creating development tools. The frameworks it has introduced have frequently showcased technical merit, yet they lack the vital consistency needed for developers to rely on them.

As highlighted in Rebecca Sutter’s analysis, internal decision-making has often led to rapid shifts in strategy, resulting in uncertainty for developers. The root concern is not the lack of options, but rather the absence of a trustworthy path forward—developers long for a framework that provides reliable support.

Web Apps: A Reflection of Developer Sentiment

Web applications are not dominating the Windows ecosystem due to their superior performance. Instead, they have gained traction as a fallback for developers seeking reliability in a landscape marked by shifting priorities.

Developers are making strategic choices based on historical experience and the unpredictability of Microsoft’s future decisions.

To elevate app quality on Windows, Microsoft’s approach must extend beyond fixing Windows 11 and prioritizing native applications. Rebuilding developers’ trust is critical, complemented by a commitment to maintaining consistent, reliable frameworks for the future.

Source & Images