News

Uno Platform Survey: Windows Usurps Android as Most Important Target

Uno Platform, a close Microsoft partner that cooperates with Redmond on developer tooling, published a community survey that, among other things, finds Windows has supplanted Android as the most important target for developers.

The company offers a namesake, open source dev platform that "allows for creating pixel-perfect, single-source C# and XAML apps that run natively on Windows, iOS, Android, macOS, Linux, and Web via WebAssembly," while featuring Figma integration for design-development handoff and extensions to bootstrap projects.

It earlier this month published results from a survey of 220 community developers.

Platforms that Apps Need to Run On
[Click on image for larger view.] Platforms that Apps Need to Run On (source: Uno Platform).

A key takeaway from the survey, the company said, is that "Windows as a target platform has gained importance at 'the expense' of macOS and Linux. Also, it took over Android as the most important target platform."

In describing the most important targets for cross-platform development, the company examined year-over-year patterns and found the same top three platforms were listed, though with some changes in popularity:

  • Windows: 77 percent in 2022 vs. 67 percent in 2021
  • Android: 72 percent vs. 69 percent in 2021
  • Web: 64 percent in both 2022 and 2021

"It is also worth noting that macOS dropped from 36 percent to 28 percent, and Linux dropped from 31 percent to 26 percent year-over-year when looking at the 'must run on' platforms," the company said. "Coincidentally this drop seems to correspond with the spike Windows received."

In mobile-specific results, Android rose from 69 percent to 72 percent in 2022, while iOS dipped slightly from 58 percent to 57 percent in 2022, a 15 percent difference in Android's favor, though Uno Platform noted that this year's survey question differed from last year's, "so we take these results lightly."

Other results from the survey unsurprisingly found that the top IDEs were Visual Studio, Visual Studio for Mac and Visual Studio Code, with the top non-Microsoft IDE being Rider from JetBrains.

Top IDEs If Restricted to One
[Click on image for larger view.] Top IDEs If Restricted to One (source: Uno Platform).

"The #2 spot for VS Code claim was further confirmed by asking developers to hypothetically chose ONLY ONE IDE they could use for their development," the company said. "We introduced this hypothetical question in 2022 to see preferences. Looking at the results below, a portion of Visual Studio developers (Windows and Mac) could be willing to use VS Code as their only tool if it had some additional IDE-like features they needed."

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube