c# - What are the touch-centric development benefits of moving a windows WPF desktop application to a Windows Store app? -

I have a WPF / MVVM application that runs on Windows 7. Most of my users have Windows 7 machines but I would like to develop an advanced touch-enabled version for windows, but need to keep Windows 7 version up to date. The app currently works as it happens on Window 8, which acts as a click. The ability to run on an RT tablet is also not included, how will this rewrite benefit me? The purpose for expansion is to take an application with a repetitive click and to make it more efficient and less stressful on long-term users. The application will never need to run on the tablet because it requires many screen spaces and visual inspection of many images.

For example, are there specific gestures like pinch and zoom which are easy to store in apps compared to WPF to apply in windows?

I have struggled to ask this question, so if I remember the proper title, then I will be happy to change it to make it clear.

my 2c

WinRT / XAML benefits

1. Controls designed for you to get touch - they respond more to touch-friendly, better touch and some of them are unique to WinRT, this allows you to at least Can save time, which you may need to spend most of the WPF controls.
2. You get a scroll wover that easily and zooms with touch, you are the one that has pans for WPF, but I'm not sure that it can not be responsive.
   The surface SDK is also going a bit old (VS 2012, WPF 4.0) and I'm not sure it's ideal for desktops. Once you remember from the time of the large surface, you can press more than one button at the same time that can not be ideal.
3. You get all the list controls which are ScrollViewer and ListView , GridView or FlipView .
4. You get great integration with a browser control ( WebView ), the latest DirectX and Media Foundation (Mike, Camera, Video, audio).
5. You get a text box which integrates well with the virtual keyboard, allows selection with touch etc.
6. Many other small controls.
7. decent high DPI support.
8. The app is easy to sell in public easily.
9. You can get a new, responsive async API and learn a new framework that can be a future.
The advantage of WPF
You get to learn the skills that WPF can get to reuse most skills .
1. Enterprise deployment can be simple (depending on the scale and current infrastructure for a WPF app).
2. You do not have to rewrite your code or you do not have to wade two very different structures which probably do not work well, usually with some development tools, usually write more time than initial estimates It seems and often brings many bugs and limitations that were not in older versions of the software.
3. You can move forward using your existing skills.
4. Frameworks and libraries of many heritage available to you
5. No Windows Store app sandbox limitations.
6. There are many powerful controls in the platform and third party libraries that might not work great with the necessary contact but are very powerful for the mouse and keyboard. Particularly different datagrids and possibly charts and others. Apart from office document view and any other ActiveX things also hosting.
7. WPF is still in the future for desktops and can achieve some features or controls which are currently ViewRT / XAML and create from 2014.
8. More mature tooling (snoop!)
9. The overall and more mature platform is not likely to turn as hot under your feet as hot and new as possible.