[go: nahoru, domu]
Jump to content

Universal Windows Platform

From Wikipedia, the free encyclopedia
(Redirected from WinObjC)
See also: Universal Windows Platform apps

Universal Windows Platform
Developer(s)Microsoft
Operating systemWindows 10, Windows 10 Mobile, Windows 11, Xbox system software, Windows Mixed Reality
PlatformIA-32, x86-64, ARM32, ARM64
TypeComputing platform
Websitelearn.microsoft.com/en-us/windows/uwp/

Universal Windows Platform (UWP) is a computing platform created by Microsoft and introduced in Windows 10. The purpose of this platform is to help develop universal apps that run on Windows 10, Windows 10 Mobile (discontinued), Windows 11, Xbox One, Xbox Series X/S, and HoloLens without the need to be rewritten for each. It supports Windows app development using C++, C#, VB.NET, and XAML. The API is implemented in C++, and supported in C++, VB.NET, C#, F# and JavaScript.[1] Designed as an extension to the Windows Runtime (WinRT) platform introduced in Windows Server 2012 and Windows 8, UWP allows developers to create apps that will potentially run on multiple types of devices.[2]

UWP does not target non-Microsoft systems. Microsoft's solution for other platforms is .NET MAUI (previously "Xamarin.Forms"[3]), an open-source API created by Xamarin, a Microsoft subsidiary since 2016. Community solutions also exist for non-targeted platforms, such as the Uno Platform.

Compatibility

[edit]

UWP is a part of Windows 10, Windows 10 Mobile and Windows 11. UWP apps do not run on earlier Windows versions.

Apps that are capable of implementing this platform are natively developed using Visual Studio 2015, Visual Studio 2017, Visual Studio 2019, or Visual Studio 2022. Older Metro-style apps for Windows 8.1, Windows Phone 8.1, or for both (universal 8.1) need modifications to migrate to UWP.[4][5]

Some Windows platform features in later versions have been exclusive to UWP and software specifically packaged for it, and are not usable in other architectures such as the existing WinAPI, WPF, and Windows Forms. However, as of 2019, Microsoft has taken steps to increase the parity between these application platforms and make UWP features usable inside non-UWP software. Microsoft introduced XAML Islands (a method for embedding UWP controls and widgets into non-UWP software) as part of the Windows 10 May 2019 update, and stated that it would also allow UWP functions and Windows Runtime components to be invoked within non-packaged software.[6]

API bridges

[edit]

UWP Bridges translate calls in other application programming interfaces (APIs) to the UWP interface, so that applications written in these APIs would run on UWP. Two bridges are announced during the 2015 Build keynote for Android and iOS apps to be ported to Windows 10 Mobile.[7] Until January 2022, Microsoft maintained support for bridges for Windows desktop apps, progressive web apps, Microsoft Silverlight, and iOS's Cocoa Touch API.[8]

iOS

[edit]
Windows Bridge for iOS (WinObjC)
Developer(s)Microsoft
Initial releaseAugust 6, 2015; 9 years ago (2015-08-06)
Repositorygithub.com/microsoft/WinObjC
Written inObjective-C++, Objective-C, C, C++
TypeMiddleware
LicenseMIT License
Websitedeveloper.microsoft.com/en-us/windows/bridges/ios/

Windows Bridge for iOS (codenamed "Islandwood") is an open-source middleware toolkit that allows iOS apps developed in Objective-C to be ported to Windows 10 by using Visual Studio 2015 to convert the Xcode project into a Visual Studio project.[7][9][10] An early build of Windows Bridge for iOS was released as open-source software under the MIT License on August 6, 2015, while the Android version was in closed beta.[7]

This "WinObjC" project is open source on GitHub. It contains code from various existing implementations of Cocoa Touch like Cocotron and GNUstep as well as Microsoft's own code that implements iOS frameworks using UWP methods. It uses a version of the LLVM clang compiler.[11]

Android

[edit]

Windows Bridge for Android (codenamed "Astoria") was a runtime environment that would allow for Android apps written in Java or C++ to run on Windows 10 Mobile and published to Microsoft Store. Kevin Gallo, technical lead of Windows Developer Platform, explained that the layer contained some limitations: Google Mobile Services and certain core APIs are not available, and apps that have "deep integration into background tasks", such as messaging software, would not run well in this environment.[12][13]

In February 2016, Microsoft announced that it had ceased development on Windows Bridge for Android, citing redundancies due to iOS already being a primary platform for multi-platform development, and that Windows Bridge for iOS produced native code and did not require an OS-level emulator. Instead, Microsoft encouraged the use of C# for multi-platform app development using tools from Xamarin, which they had acquired prior to the announcement.[14][15][16] In 2021, Microsoft allowed Windows 11 to run Android apps with an OS-level emulator and allowed apps to be installed in the store.[17]

Deployment

[edit]

UWP provides an application model based upon its CoreApplication class and the Windows Runtime (WinRT).[1] Universal Windows apps that are created using the UWP no longer indicate having been written for a specific OS in their manifest build; instead, they target one or more device families, such as a PC, smartphone, tablet, or Xbox One, using Universal Windows Platform Bridges. These extensions allow the app to automatically utilize the capabilities that are available to the particular device it is currently running on.[18] A universal app may run on either a mobile phone or a tablet and provide suitable experiences on each. A universal app running on a smartphone may start behaving the way it would if it were running on a PC when the phone is connected to a desktop computer or a suitable docking station.[19]

Reception

[edit]

Games developed for UWP are subject to technical restrictions, including incompatibility with multi-video card setups, difficulties modding the game, overlays for gameplay-oriented chat clients, or key binding managers.[20] UWP will only support DirectX 11.1 or later, so games built on older DirectX versions will not work.[21] During Build 2016, Microsoft Xbox division head Phil Spencer announced that the company was attempting to address issues which would improve the viability of UWP for PC games, stating that Microsoft was "committed to ensuring we meet or exceed the performance expectations of full-screen games as well as the additional features including support for overlays, modding, and more." Support for AMD FreeSync and Nvidia G-Sync technologies, and disabling V-sync, was later added to UWP.[22][23]

Epic Games founder Tim Sweeney criticized UWP for being a walled garden, since by default UWP software may only be published and installed via Windows Store, requiring changes in system settings to enable the installation of external software (similarly to Android). Additionally, certain operating system features are exclusive to UWP and cannot be used in non-UWP software such as most video games. Sweeney characterized these moves as "the most aggressive move Microsoft has ever made" in attempting to transform PCs into a closed platform, and felt that these moves were meant to put third-party games storefronts such as Steam at a disadvantage as Microsoft is "curtailing users' freedom to install full-featured PC software and subverting the rights of developers and publishers to maintain a direct relationship with their customers". As such, Sweeney argued that end-users should be able to download UWP software and install it in the same manner as non-UWP software.[24]

Windows VP Kevin Gallo addressed Sweeney's concerns, stating that "in the Windows 10 November Update, we enabled people to easily side-load apps by default, with no UX required. We want to make Windows the best development platform regardless of technologies used, and offer tools to help developers with existing code bases of HTML/JavaScript, .NET and Win32, C++ and Objective-C bring their code to Windows, and integrate UWP capabilities. With Xamarin, UWP developers can not only reach all Windows 10 devices, but they can now use a large percentage of their C# code to deliver a fully native mobile app experiences for iOS and Android."[25]

In a live interview with Giant Bomb during its E3 2016 coverage, Spencer defended the mixed reception of its UWP-exclusive releases, stating that "they all haven't gone swimmingly. Some of them have gone well", and that "there's still definitely concern that UWP and our store are somehow linked in a way that is nefarious. It's not." He also discussed Microsoft's relationships with third-party developers and distributors such as Steam, considering the service to be "a critical part of gaming's success on Windows" and stating that Microsoft planned to continue releasing games through the platform as well as its own, but that "There's going to be areas where we cooperate and there's going to be areas where we compete. The end result is better for gamers." Spencer also stated that he was a friend of Sweeney and had been in frequent contact with him.[26][27]

On May 30, 2019, Microsoft announced that it would support distribution of Win32 games on Microsoft Store; Spencer (who had since been promoted to head of all games operations at Microsoft, reporting directly to CEO Satya Nadella) explained that developers preferred the architecture, and that it "allow[s] for the customization and control [developers and players] come to expect from the open Windows gaming ecosystem." It was also announced that future Xbox Game Studios releases on Windows would be made available on third-party storefronts such as Steam, rather than be exclusive to Microsoft Store.[28][29]

References

[edit]
  1. ^ a b "What's a Universal Windows app?". Microsoft Developer Network. Microsoft. May 7, 2018. Retrieved April 29, 2019.
  2. ^ "Introduction to Universal Windows Platform (UWP) apps for designers". Microsoft Developer Network. Microsoft. May 5, 2018. Archived from the original on February 22, 2019. Retrieved April 29, 2019.
  3. ^ "Xamarin Updates From Microsoft Build 2020". Xamarin Blog. May 19, 2020. Retrieved January 21, 2022.
  4. ^ "Migrate apps to the Universal Windows Platform (UWP)". Microsoft Developer Network. Microsoft. Retrieved July 31, 2015.
  5. ^ "Move from Windows Runtime 8.x to UWP". Microsoft Developer Network. Microsoft. February 8, 2017. Retrieved April 29, 2019.
  6. ^ Foley, Mary Jo. "Microsoft wants to close the UWP, Win32 divide with 'Windows Apps'". ZDNet. Retrieved May 8, 2019.
  7. ^ a b c Hachman, Mark (August 6, 2015). "Microsoft releases iOS-to-Windows app maker Windows Bridge to open source". PC World. IDG. Retrieved October 9, 2015.
  8. ^ "Universal Windows Platform Bridges - Windows app development". Microsoft Developer.
  9. ^ Chester, Brandon (April 29, 2015). "Microsoft Demonstrates Android and iOS Applications Running On Windows 10". Anandtech. Purch Inc. Retrieved October 9, 2015.
  10. ^ Protalinski, Emil (May 1, 2015). "Everything you need to know about porting Android and iOS apps to Windows 10". VentureBeat. Retrieved October 9, 2015.
  11. ^ "microsoft/WinObjC: Objective-C for Windows". GitHub. Microsoft. February 16, 2020.
  12. ^ Branscombe, Mary (May 11, 2015). "How will Android support work in Windows 10 for Phones?". TechRadar. Retrieved October 9, 2015.
  13. ^ Bright, Peter (April 29, 2015). "Microsoft brings Android, iOS apps to Windows 10". Ars Technica. Retrieved October 9, 2015.
  14. ^ Jo Foley, Mary (February 24, 2016). "Microsoft is buying mobile tool vendor Xamarin". ZDNet. CBS Interactive. Retrieved April 29, 2019.
  15. ^ Jo Foley, Mary (February 25, 2016). "Microsoft: Our Android Windows 10 bridge is dead, but iOS, Win32 ones moving ahead". ZDNet. Retrieved February 26, 2016.
  16. ^ Bright, Peter (February 26, 2016). "Microsoft confirms: Android-on-Windows Astoria tech is gone". Ars Technica. Conde Nast. Retrieved April 29, 2019.
  17. ^ "How to Run Android Apps in Windows 11".
  18. ^ Domingo, Michael (May 1, 2015). "Inside the Universal Windows Platform Bridges". Visual Studio Magazine. Retrieved October 9, 2015.
  19. ^ Radich, Quinn; Satran, Michael; Whitney, Tyler; Jacobs, Mike; Weston, Susan; Das, Debalin (May 7, 2018). "Guide to Universal Windows Platform (UWP) apps". Windows Developers Center. Microsoft. Retrieved May 10, 2019.
  20. ^ "Microsoft needs to stop forcing console-like restrictions on Windows Store PC games". Ars Technica. Conde Nast. February 29, 2016. Retrieved March 30, 2016.
  21. ^ "Create a DirectX Universal Windows Platform (UWP) game - UWP applications". learn.microsoft.com.
  22. ^ Hruska, Joel (May 10, 2016). "New Windows 10 updates add support for FreeSync, G-Sync, and unlocked frame rates". ExtremeTech. Retrieved May 10, 2019.
  23. ^ Makuch, Eddie (March 30, 2016). "Xbox Boss on PC Gaming: "We've Heard the Feedback Loud and Clear"". GameSpot. Retrieved May 10, 2018.
  24. ^ Walton, Mark (March 4, 2016). "Epic CEO: "Universal Windows Platform can, should, must, and will die"". Ars Technica. Conde Nast. Retrieved May 10, 2019.
  25. ^ Takahashi, Dean (March 4, 2016). "Epic's Tim Sweeney questions Microsoft's commitment to an open Windows platform". VentureBeat.
  26. ^ Bright, Peter (June 16, 2016). "Microsoft will use Steam to sell Windows games, not just its own store". Ars Technica. Condé Nast.
  27. ^ Makuch, Eddie (June 15, 2016). "Xbox Boss Confirms More Steam Releases Coming, Discusses PC Struggles". GameSpot. CBS Interactive.
  28. ^ Spencer, Phil (May 30, 2019). "Our Approach to PC Gaming". Xbox. Retrieved May 30, 2019.
  29. ^ Humphries, Matthew (May 30, 2019). "Microsoft Teases Xbox Game Pass for PC". PCMag. Retrieved May 30, 2019.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Universal_Windows_Platform&oldid=1229286621#iOS"