AI News

Microsoft plans to use AI to make native WinUI app development easier

cnBetaUpdated Nov 16 18:57

AI summary

Microsoft is promoting WinUI 3 and simplifying the development process. Developers can create, build, and run native Windows apps via the command line without installing the bulky Visual Studio. Microsoft provides WinUI-oriented development capabilities for AI coding assistants; combined with GitHub Copilot, VS Code, and command-line tools, some basic apps can complete an initial build in about 30 minutes. Microsoft is also rebuilding Windows 11 system components with WinUI 3, and the Windows Search interface has begun testing the new version.

Body · AI translation

In an October 23 report, Windows Latest pointed out that Microsoft is promoting WinUI 3 and providing a more streamlined development process, allowing developers to create, compile, and run native Windows apps without relying on the massive Visual Studio development environment. Microsoft's goal is not simply to ban web technologies, but to ensure that when developers choose native development, they no longer have to bear the high learning costs and complex build processes of the past.

WinUI 3 is Microsoft's recommended native user interface framework for modern Windows desktop apps. It supports C# and C++, can use Windows' Fluent Design system, and integrates more closely with system windows, controls, and other platform features. Compared with embedding web interfaces into desktop windows, native apps have the opportunity to achieve better performance in startup speed, resource utilization, interaction responsiveness, and system consistency, but the actual results still depend on the design and implementation quality of the specific app.

For a long time, one problem facing Windows native app development has been the complexity of the toolchain. Developers usually need to install a relatively large development environment, master the XAML interface description language, and handle project configuration, app packaging, digital signing, and certificates. For small teams and independent developers hoping to launch products quickly, this extra work can make cross-platform solutions such as Electron more attractive.

Microsoft is now trying to simplify these steps. Developers can create WinUI projects via the command line, build and run apps directly, and do not always have to rely on the traditional graphical integrated development environment. The related tools can also simplify app packaging and registration processes, reducing the work developers must do manually for MSIX packages and signing configurations. Microsoft hopes in this way to make native app development closer to the convenience of modern web app development.

Artificial intelligence is another key component of this strategy. Microsoft is providing AI coding assistants with development capabilities specifically for WinUI, enabling them to help create interfaces, generate code, handle common development tasks, and find problems through code review and interface testing. Developers can use tools such as GitHub Copilot to describe requirements in natural language, and then have AI help set up the app framework and implement specific features.

Windows Latest previously also reported that Microsoft released a quick-start process for AI-assisted development. Developers can combine VS Code, Windows app development command-line tools, and AI coding assistants to create a WinUI 3 app starting from an empty directory. Microsoft claims that, when using the related tools and templates, some basic apps can complete an initial build in about 30 minutes, and Visual Studio does not need to be installed. This time mainly reflects the efficiency of the quick-start example and does not mean that complex apps can also be developed and tested within half an hour.

Microsoft is also improving the development experience of WinUI itself. In the past, some WinUI apps experienced issues such as screen tearing or black edges when resizing windows, affecting users' impression of native apps. Microsoft says it will continue to close feature gaps in the framework and improve stability, performance, and window interaction experience. For developers, if Microsoft cannot provide a sufficiently mature native framework, even if AI can quickly generate code, it will be hard to persuade them to abandon their existing development solutions.

At the same time, Microsoft is using WinUI for more reconstruction work on Windows 11 system components. Some system interfaces and tools are gradually moving away from older implementations toward a more modern native interface framework. The Windows search interface has begun testing a new version based on WinUI 3, and some traditional system dialogs and management tools are also being modernized. Microsoft also plans to continue addressing legacy interfaces so that different parts of the system are more consistent in appearance, interaction, and performance.

The Microsoft Weather app has become an example of the resource burden that web technologies may bring. Windows Latest previously found in testing that the app's memory usage in idle state reached about 1.2GB and that it runs multiple Chromium-related child processes. The report believes this reflects the unnecessary resource overhead that can occur in web-wrapped apps. However, this is only an observation of a specific app and test environment, and it cannot be used to conclude that all software developed based on WebView2 or Electron has the same problem. Microsoft's own development documentation also acknowledges that WebView2 can be a reasonable hybrid development solution, and that resource consumption largely depends on whether the web content and app implementation have been optimized.

Behind Microsoft's push for native development is also the consideration of maintaining the Windows developer ecosystem. Over the past few years, many developers have chosen cross-platform frameworks so that one codebase can support multiple operating systems; some AI app developers prefer Mac computers or Linux development environments. Microsoft hopes that through more complete native tools, AI-assisted programming, and more convenient packaging and testing processes, Windows can once again become an attractive platform for developing modern desktop software.

However, AI lowering the cost of code generation does not mean software quality will automatically improve. AI may quickly generate apps that can run, but it may not be able to ensure that their architecture is reasonable, resource usage is low, and security is reliable, nor can it necessarily solve interaction problems in complex scenarios. If developers rely heavily on AI-generated code but ignore performance optimization and testing, the result may ultimately be merely transferring the problems of web-wrapper apps to native apps.

Therefore, the key to Microsoft's plan is not only to make WinUI apps easier to create, but also to make the native framework itself sufficiently stable, the tools sufficiently complete, and to ensure that AI-generated software undergoes the necessary testing and optimization. Only when developers can produce reliable, lightweight, and easy-to-maintain native apps at lower cost will Windows 11 have a chance to gradually shed the problem some users criticize as the "proliferation of web-wrapper apps."

Judging from the current direction, Microsoft is not completely rejecting web technologies, but hopes to change the development cost gap between native apps and web-wrapper apps. As AI programming tools, command-line development processes, and the WinUI framework continue to improve, the barrier to Windows native app development is expected to be further lowered. But whether this strategy can ultimately improve the experience of ordinary users still depends on the progress of Microsoft's own optimization of system components and on whether third-party developers are willing to truly invest in native Windows app development.

Source

cnBeta