Universal Windows Platform

Welcome to the Universal Windows Platform Developer Feedback site. This site provides the Windows developer community with a channel for feedback on the following topics:

  • Windows developer platform (APIs, runtimes, and controls)
  • Dev Center (dashboard, reporting/analytics, submission process, etc.)
  • Microsoft Store

Your suggestions will be reviewed by the Windows platform developer team to help with planning ideas and to better understand how developers are using the platform.

What this forum is not intended to cover or capture:

  • Windows consumer suggestions: Use the Windows Feedback Hub app built directly into Windows 10
  • Documentation on docs.microsoft.com: Sign in at the bottom of the page to give documentation feedback via Github
  • Visual Studio / .NET: Use the Visual Studio UserVoice site

If you’re new to UserVoice, two things to keep in mind are (a) List items (and item rankings) represent community interest in features, and not the actual priority list for the product team; and (b) Suggestions made using this forum will be moderated if they do not actually represent a feature request (or if too many different ideas are included in one suggestion).

How can we improve the Windows dev platform?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. UWP XAML should be backwards compatible with older Windows 10 Versions

    Currently it is really painful to add new Controls from newer Windows SDK versions to apps and still support older versions.

    There needs to be a way to define new XAML Controls/Properties/Etc., as currently if you want to add these, with a lower Minimum version, it has to be from code-behind.

    Ways this could potentially be fixed:
    Have a separate Class Library that only supports new SDK versions, and it will only be loaded into the app on newer SDK versions, therefore you can write safe XAML markup including new Controls and Properties.

    Like how Xamarin.Forms does it, instead of…

    7 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      2 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks for the feedback William! With the fall Creators update we are introducing conditional runtime statements in markup. This will be backwards compatible to the Creators update and later (min version 15063).

      You can append a conditional statement to your namespace with the following syntax:
      xmlns:Creators=“using:foo?IsApiContractPresent(Windows.Foundation.UniversalApiContract,4)”

      Objects and properties marked with the ‘Creators’ namespace will only be parsed if the conditional statement is true.

      Sample markup to conditionally show text:
      xmlns:Creators=“http://schemas.microsoft.com/winfx/2006/xaml/presentation?IsApiContractPresent(Windows.Foundation.UniversalApiContract,4)”/>;
      < Button Background=“Green” Creators:Content=“Show text if on creators”/>

      We’re in the process of adding documentation, samples and tooling for the feature. You can live on the bleeding edge and use it now – be aware that there might be some rough edges in tooling :).

      To write adapative code that works on versions before the Creators Update, you’ll need to use on the methods outlined here: https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/version-adaptive-code

    • LoggingChannel not showing string message content in ETW payload around 15043

      It seems that since around 15043, when showing LoggingChannel.LogMessage() calls, the string message portion is blank in device portal (shows stringmessage:,). Same code on machine with anniversary update, portal shows the string message in payload.
      capturing events with xperf shows the message in EventData as expected, so I know it's logging correctly. Something seems to have changed with loggingchannel, possibly default manifest code that handles the string message has changed around 15043?
      FWIW, preview versions of windows post anniversary update were showing the message correctly.

      7 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        3 comments  ·  Windows Device Portal  ·  Flag idea as inappropriate…  ·  Admin →
        in preview  ·  Hirsch Singhal responded

        We’ve found a fix and it will be going out in an upcoming Windows Insiders Flight. We’ll be looking for feedback on the new output to determine if this should be backported to the Creators Update release.

        Thank you,
        Hirsch

      • Add an ExpirationTime property to the ScheduledToastNotification

        The ToastNotification object has a convenient ExpirationTime property that automatically dismisses it after a given period. Unfortunately, the ScheduledToastNotification, which is just a ToastNotofcation but "scheduled", lacks this helping feature. This makes me, as a developer, scracth my head and write a lot of code including background tasks just so I circumvent this problem and not have the users of my app get crowded with not-so-relevant-anymore notifications in their action center.
        Thank you.

        4 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

        • PasswordBox with InputScope=NumericPin locks keyboard for other controls

          Please fix this bug: Once a passwordBox with an InputScope=NumericPin is rendered the keyboard becomes stuck as a number pad and does not return to the full keyboard. Described nicely here: https://social.msdn.microsoft.com/Forums/vstudio/en-US/d54a77b9-9a47-4feb-81c0-be662639792e/soft-input-panel-does-not-change-back-from-numericpin-mode?forum=wpdevelop

          7 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

            1 comment  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
          • Implement System.ComponentModel.TypeConverter in WinRT APIs

            TypeConverter is helpful because it allows the author of a type to provide intrinsic support for determining to/from which types a type may be converted and actually converting between types - most typically for converting to/from string but other types as well.

            55 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              10 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
            • DataGrid Control for WinRT

              Some business applications require this type of control!!!
              Windows Store Apps for the line-of-business (LOB) apps need help.

              23 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)

                We’ll send you updates on this idea

                6 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →

                We brought over the DataGrid control from Silverlight to WinRT. You can access the pre-release nugget package today – aka.ms/win10datagrid

                We also open sourced it – aka.ms/win10datagridsource

                Read more about it here – aka.ms/win10datagriddoc

              • Detect whether user has rated the app or not

                As a developer, the only way to increase app ratings and review is to prompt user.

                At present there are no APIs to detect whether a user has rated the app or not. Some users get annoyed and down rate the app due to this very reason.

                This is a very basic piece of functionality that has been missing for long.

                Please provide us a simple API that gives us this information.

                Alternative for us to continue work towards this http://invokeit.wordpress.com/2013/10/16/detect-whether-user-has-reviewed-your-app-or-not-wpdev/ however I am not keen on this purely because I can see this being abused very easily.

                311 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  9 comments  ·  Missing APIs  ·  Flag idea as inappropriate…  ·  Admin →

                  Per the wonderful Mr. Torr: This should be supported now — if you use StoreRequestHelper.SendRequestAsync and pass 6 and an empty string as the parameters, you should get back a response. (Not documented yet…):

                  https://docs.microsoft.com/en-us/uwp/api/Windows.Services.Store.StoreRequestHelper#Windows_Services_Store_StoreRequestHelper_SendRequestAsync_Windows_Services_Store_StoreContext_System_UInt32_System_String_

                  Will close this out once docs are out

                • Provide ability to transfer ownership of app including IAP transfer

                  Some people have had other developers submit apps to the marketplace on their behalf for many reason. They may have been in a country that is not supported for example. More then one developer may have worked on the app and are now splitting. Some people may sell their apps to others.

                  In all these cases it breaks the update cycle for existing users because the new owner would have to create a new app instead of updating the existing one.

                  285 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    47 comments  ·  Dev Center + Microsoft Store  ·  Flag idea as inappropriate…  ·  Admin →

                    Starting this month apps can be transferred from one account to another. To start the process you need to open a support ticket to start the process. Once you submit the request, you’ll get a checklist (for example you need to finish any pending submissions, export the reports). The acquisitions, reviews history and users are transferred, though the historical revenue is not transferred. The feature is available to every app, except if the app has IAP – support for IAP is being investigated for the future.

                  • Don't see your idea?

                  Feedback and Knowledge Base