Microsoft details the present, and future, of Windows Bridge for iOS

Today on the Windows Blog, Microsoft took the opportunity to speak more about how the Windows Bridge for iOS is progressing and where it is headed. The Windows Bridge for iOS was released as an open source project on Github in August to begin the hard work of creating a way for developers to convert their iOS apps into Universal Windows Programs.

As we reported last week, the sister Windows bridge project for Android apps has not fared well, and Project Astoria, as it is (was) known, has been put on hold indefinitely. But the Windows Bridge for iOS, known internally as Project Islandwood, has been more successful.

iOS Bridge Landing Page

In today’s blog, Microsoft notes that 4,500 developers have starred the project’s repository in Github, and that “what’s more, over 500 created your own fork. More than 200 issues have been filed (and several dozen closed, with many more in various stages of being fixed).”

And since making the project open source in August, Microsoft has added support for:

    • GLKit. We’ve built out support for apps that make use of GLKit’s math libraries, textures, shaders and effects, as well as views and view controllers, so you can finally bring that game you’ve been working on to Windows devices.
    • Xibs, AutoLayout & Storyboard. One of the biggest requests we’ve gotten has been for Xib, AutoLayout and Storyboard support. We’ve added support for Xibs using our Xib2Nib tool as well as preliminary support for both AutoLayout and Storyboards.
    • KVO/KVC. Another widely requested feature, and one we were pleased to add robust support for a few weeks ago.
    • New sample projects. We’ve added sample projects showcasing GLKit support, intermixing of UIKit and XAML controls, and a simple HelloWorld project to help new users get started.
    • And much, much more. In addition to those features specifically called out here, we’ve continued to expand our coverage of iOS libraries, crushing bugs right and left along the way.

The Windows App team also detailed more about the future plans for the project and what is next for developers who are interested in bringing their iOS app to Windows. Microsoft has released a new landing page for the iOS bridge which will be used for a new series of tools to assist in the conversion. The Windows App team also said that the new website will include more answers for developers’ questions regarding API availability and the project’s development roadmap on Github.

Outlook for iOS

Finally, the Windows App team put out the request to iOS developers to help test the first tool for their new website. Microsoft needs developers to test their IPAs (the iOS application archive file which stores an iOS app) in a new automatic app analyzer. The new tool analyzes uploaded IPAs and provides a compatibility analysis to the developer over the web. The analysis will hopefully give developers a detailed idea of how much work has to be done to convert it to Windows, as well as include tips and suggestions. If you are interested in submitting your iOS app’s IPA and being one of the first to get the new automatic app analyzer results, you can head over to the Windows App team’s page here.

After the news of Project Astoria’s troubles, its good to hear from an official blog post that the Windows Bridge for iOS is gaining steam with support expanding along the way and into the future. Also with the loss of Project Astoria, the weight falls that much more heavily on the shoulders of Project Islandwood to help curtail the perceived “App Gap” problem which has been to the detriment of Windows Phone market share.

Hopefully, in the future, a successful Project Islandwood will bolster the already incredibly fast pace of Windows 10 adoption by helping increase the robustness of Microsoft’s new unified store.

Share This
Further reading: , , , , ,

Are you planning to use the Windows Bridge for iOS to make a universal windows app?