Is Intel Targeting on Desktop Mode than Win RT Mode in Windows 8?

Is Intel Targeting on Desktop Mode than Win RT Mode in Windows 8?

I am interested in developing an app for Ultrabook. I am curious about mode that should be targeted for ultrabook apps. Should they be targeting Desktop mode, since Ultrabook have much Richer capabilities. I also saw some comparison where it was saying Touch is more powerful in Windows mode than in Win RT mode.

Since this is my first step towards developing an app, I just wanted to have better information to utilize strength of platform.

13 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.


what mode you want to target will essencially depends on what application you want to develop.
Generally speaking, Windows 8* store apps are intented to be immersive, well integrated with the other Windows 8* store apps thanks to contracts, respect strong design guidelines, and they also should be able to run inside the sandbox boundaries.
If your app doesn't fit in that, desktop is the way. You will also be able to use a lot of existing APIs that are not (yet? it depends) available for Windows 8* store apps.

I wouldn't say that touch is more powerful on a side than on another. You may be able to get a deeper access to the underlying functionnalities of the OS on the desktop side, whereas the Windows Runtime gives a more restricted, but also more easy-to-use one that is efficient enough for most of the applications.

Which mode you choose will depend on the features you are targeting, your preferred development environment, and the amount of work your willing to put in for the market opportunity. Do you want to leverage WiDi, the Win8 sharing system, OpenGL? Does your app already run on Win7 and do you want to distribute to legacy PC's? We are publishing two articles on this very topic very soon to help you make a choice. So stay tuned.

Thanks Xavirer and Bob. I will be looking forward for the documents to help me make choice.

I think WinRT provide the opportunity to develop different types of devices with similar interfaces were developed. . Net platform made quick work of course. Web applications, desktop applications, WPF applications and Silverlight applications to prepare the continuous performance spending. WinRT shortened these processes

Good Aspects
WinRT and touch screens can prepare more advanced interfaces
Also Winform different from that screen to design a more uniform
Improving the existing structures can customize Region

Bad Aspects
WinRT applications will not work with Win7 and the same features as the previous operating systems

WinRT Ultrabook offers us many opportunities to touch and touch screens, businesses seem to be ready already
Demands have changed and promises to be a very fast very fast even if the switch works
Intel probably going support all os system WinRT, Android, Mac or Linux for touch sensors.
I believe WinRT and Touch API will be best for touch devices. Because XAML data visualization interface is the best ever made

I think that Win8 will benefit from Apps available via Stores be they Microsoft, Intel or whatever. Innovation is probably best served in the new environment provided by WinRT - why ever did Microsoft come up with WinRT and Windows RT,two completely different things?

Desktop designed for touch Apps will need to take up a large portion of the screen as everything outside will be touch compatible but not touch aware so they will always look a 'forced' or 'half hearted' solution. I am sure this will change in time.


Below link is good an answer i think

I think in the future Windows RT and WinRT will be merged like WPF and Silverlight..

8< I think in the future Windows RT and WinRT will be merged like WPF and Silverlight..

Well developers for Windows RT use WinRT only and developers for Windows 8 can use WinRT or Win32/IE/.NET so I don't think that will happen soon, if ever.

OT too as Windows RT runs on ARM processors.


As per my Knowledge The whole WinRT library is written in C++.It is the way Microsoft thinks that will chnge the future of Coding.To a .net Developer WinRT will look like the same framework as .net Framwork 4.5 but in its entirity both are different but usage is more or less same.As of now the current focus is in MVVM design so WinRT helps but .net Framework 4.5 help us bind desktop applications.

I think the thread has wandered a little OT as the original question asked if Intel was pushing the Desktop rather the 'Metro' UI. I think some may have gained that impression as a lot of the samples have been in desktop mode but I don't believe Intel has an agenda to ignore 'Metro'.


PS I know we aren't supposed to call it 'Metro' but everyone does....

We support both and it looks like our content is fairly evenly split between the two. Since Microsoft is the best place to learn about Metro we feel obligated to cover Desktop in a way it's not being covered. In the end our focus is to show developers how to leverage the hardware features thus we cover both

You can easily create various types of devices with the same interface. WinRT is known for shortening the processes. The existing structures can also be improvised on with WinRT.

In the initial phases the program was called IADP (Intel Atom Development Program) and it was encouraged to write apps to target ATOM processor based devices. It included Desktops, Netbooks, Laptops and any other Custom made ATOM based device.It supported multiple languages/platforms (Ref. MeeGo). The business point is when a customer visits a retail shop, AppUp client is by default installed on the device. Windows being most widely used and offering flavors from XP onwards, something was essential to encourage .Net based apps and to prevent copy paste of the apps. With changes made to .Net by Microsoft and Windows to be made compatible on Intel Hardware platform some changes reflected in the IADP program.
So my simple answer to the question is, now there are no boundaries. If you want to take advantage of various form factors, computing and visual power, multi-threading etc. no problem.
Only limitation is Intel yet has not figured out Client/Server architecture in IADP program.
Jayant Akolkar

Leave a Comment

Please sign in to add a comment. Not a member? Join today