Microsoft hiring to develop cross-platform Windows 8-Windows Phone apps

While Windows 8, Windows RT and Windows Phone 8 all share at least some code, apps made for one of those operating system don't run on the other two without some additional programming help. Now there's word that Microsoft is trying to solve that problem with a project that would allow cross-platform app development.

ZDNet.com reports that a new job listing from Microsoft states:

Are you excited about Windows Phone? Are you passionate about delivering the best possible experience to the developer community? Do you wish the code you write for Windows Store apps would just work on the Windows Phone and vice versa? If so, then this is the role for you!

If this project is successful, it could allow a larger number of Windows Phone apps to make the move to Windows 8 or RT, which is currently far behind Windows Phone in terms of the number of apps in its library. Cross-platform apps would also certainly boost the total number of apps made for each platform as developers would no longer have to do any extra works to port their apps to work on three platforms.

This project might be part of "Windows Blue", the rumored plan that could see major updates made to a number of different Microsoft software products, including some outside of Windows.

Source: ZDNet.com | Image via Microsoft

Report a problem with article
Previous Story

Microsoft and Bing to offer U.S. State of the Union coverage

Next Story

Bing potentially reveals secret US drone base in Saudi Arabia

16 Comments

Commenting is disabled on this article.

What do you mean?

Atleast 90% of apps will work on both Win 8/RT by just compiling the app for both of them. Which takes a mouse click. The article is wrong by saying:

Article
While Windows 8, Windows RT and Windows Phone 8 all share at least some code, apps made for one of those operating system don't run on the other two without some additional programming help.

Edit: just realized you're talking abut Windows RunTime...

This should have been done at least a year ago.

Also, I still think Windows 8 should have an application that allows to run Windows Phone apps (the managed code ones) in a sandboxed environment.

MS has promised the same stuff several times in the past. First, MS launched .net framework (desktop) and .net compact framework (for pocketpc and smartphone) And now, MS is saying the same. sheesh.

Anyways, i blame the developer adoption of WP and ModernUI mainly because XAML, it s**ck *ss.

And MS allowed,as an alternative to XAML, the use of Javascript. However, the way to work with javascript is even more messy than to work with XAML. MS should learn from Bootstrap.

I understand why Sinofsky hated so much managed code, it is not that he hated any managed cpde but the managed code that MS is trying to adopt.

Edited by Brony, Feb 9 2013, 12:16am :

That was a different time. I think they at least have things in place this time to make it happen. The question is if developers will take full advantage of it.

Brony said,
Anyways, i blame the developer adoption of WP and ModernUI mainly because XAML, it s**ck *ss.

And MS allowed,as an alternative to XAML, the use of Javascript. However, the way to work with javascript is even more messy than to work with XAML.

Ummm. Ummm. What are you talking about? First of all, XAML doesn't suck. It's very nice. It works. And second, no, the alternative to XAML isn't JavaScript... you obviously don't know what you're talking about.

The alternative to XAML is Html5, where JavaScript is used for the codebehind as an alternative to C# or VB. JavaScript isn't a markup language.

Ok, not to be extra cranky, but everyone DOES realize that this has ALWAYS been in the works for a long time.

WP8 is using the WP7 UI/App Platform model, but is a combination of WinRT technologies instead of only Silverlight/.NET.

The WP8 rollout is designed to be seamless from WP7; however, technically there is NO reason that WP8 cannot run the full WinRT framework from Windows 8, and there is no reason that Windows 8 cannot run the WP8 modified UI/App platform.

As Windows 8 hits 'Blue' and WP8 hits its first revision, the movement towards each other gets closer as UI elements from 'both' platforms that are currently inconsistent gain parity between the two platforms. (i.e. The App Bar in WP will translate into the Windows 8 App bar, etc.)

So in other news, the sky is blue, and the sun should come up tomorrow...

Windows phone currently uses as subset of the WinRT API.So you cant create a windows 8 project for example,then compile for windows phone. The way to do it currently is to create a Windows runtime component that can be shared to windows phone, or windows8/rt. For example,if im creating an IRC client,i will build all the logic and parsing code of the IRC functionality as a Windows Runtime Component(dll), then create a windows phone project and call this functionality from my app using the windows phone SDK(I have to implement the networking using windows phone SDK for example). If I want a Windows 8 app,ill do the same,use the shared component and use the WinRT API to write my Windows 8 app using WinRT API.

What Microsoft is apparently doing is unifying the API where you can create only one project that will compile and run on phone,tablet or PC.

Inside the code,lets say I want to determine which device im using to process the correct control input,i would do this

switch(device)
{
case PHONE:
getphoneinput();
break;
case TABLET:
gettabinput();
break;
case PC:
getpcinput();
break;
}

I could use this when rendering to screen as well depending which device im using.

This would make it so easy to create apps or games for all devices without having to waste time with porting,re writing code depending on the API and limitations. Someone writing a tablet app wont think twice of making it phone compatible.

This is the future folks,and its ****in insane. Cant wait.

vcfan said,
Windows phone currently uses as subset of the WinRT API.So you cant create a windows 8 project for example,then compile for windows phone. The way to do it currently is to create a Windows runtime component that can be shared to windows phone, or windows8/rt. For example,if im creating an IRC client,i will build all the logic and parsing code of the IRC functionality as a Windows Runtime Component(dll), then create a windows phone project and call this functionality from my app using the windows phone SDK(I have to implement the networking using windows phone SDK for example). If I want a Windows 8 app,ill do the same,use the shared component and use the WinRT API to write my Windows 8 app using WinRT API.

What Microsoft is apparently doing is unifying the API where you can create only one project that will compile and run on phone,tablet or PC.

Inside the code,lets say I want to determine which device im using to process the correct control input,i would do this

switch(device)
{
case PHONE:
getphoneinput();
break;
case TABLET:
gettabinput();
break;
case PC:
getpcinput();
break;
}

I could use this when rendering to screen as well depending which device im using.

This would make it so easy to create apps or games for all devices without having to waste time with porting,re writing code depending on the API and limitations. Someone writing a tablet app wont think twice of making it phone compatible.

This is the future folks,and its ****in insane. Cant wait.


You know, I wasn't thinking like that. That would be tremendous.

ShareShiz said,
I thought that was the whole point of Windows 8

Well. Your code works on both Windows Phone and Windows 8. But they have to be in separate projects, although potentially in the same solution. And the backend code can be shared, but you obviously have to have different XAML UI code for each... to optimize the UI for large and small screens.

The only thing they need to do is allow you to create one project for both (not separate projects in the same solution), and either use the same UI or choose UI based on form factor. I believe that is the state of things for iPhone and iPad, but obviously that doesn't extend to OS X.

In any case, what I do is put my projects in the same solution and add shared code as links to the other projects. Modify the WinRT version, and the WP7 and WP8 versions get modified too. The WP8 version entirely consists of links to WP7 files... with a few #if WP8 preprocessor directives for the WP8 specific parts... like voice commands.

It will be interesting to see what developers can make when coding for one platform that has different screen sizes and interactivity. One app will have to work with mouse/KB, Touchpad and KB, Touchscreen and KB, control pad/voice/Motion control input for the XBox, and just a touch interface for tablets and be able to work on screen sizes from 3.5 to 40 inches. Having one code base to work on might give an advantage and the they could publish to every device, but it means doing a lot of testing and imagination. I think MS should lead the development way with some in house development and examples.

Drewidian said,
It will be interesting to see what developers can make when coding for one platform that has different screen sizes and interactivity. One app will have to work with mouse/KB, Touchpad and KB, Touchscreen and KB, control pad/voice/Motion control input for the XBox, and just a touch interface for tablets and be able to work on screen sizes from 3.5 to 40 inches. Having one code base to work on might give an advantage and the they could publish to every device, but it means doing a lot of testing and imagination. I think MS should lead the development way with some in house development and examples.

Agreed. It might be great as a developer, but I can see this being less great for users...