Windows 10 Sets interface
Image Courtesy: Microsoft.com

The Sets interface is not coming to your computers with the next Windows 10 update codenamed Redstone 5. Microsoft today in a blog post announced that they’re taking the Sets feature back and it’ll be released to the Insiders again when it’s ready. The report suggests that Microsoft is planning to improve Sets integration in apps like Edge browser and Office suite before the public release.

Windows 10 Sets approach is similar to the tabs in browsers. In other words, Sets allow users to operate multiple apps with just a single window of the program running on the screen.

It’s quite obvious that Sets feature won’t ship with next update for Windows 10 as Microsoft wants to continue the development of this feature to ensure it delivers the best possible experience before it’s ready for public release.

“Starting with this build, we’re taking Sets offline to continue making it great. Based on your feedback, some of the things we’re focusing on include improvements to the visual design and continuing to better integrate Office and Microsoft Edge into Sets to enhance workflow. If you have been testing Sets, you will no longer see it as of today’s build, however, Sets will return in a future WIP flight. Thanks again for your feedback,” Microsoft’s Dona Sarkar said in a blog post.

Windows 10 Sets feature is indeed useful and the company plans to bring it to the universal apps, and as well as the traditional Win32 apps.

Microsoft will allow users to enable this feature in Win32 software, such as File Explorer, Microsoft Office, Notebook and other titles. It appears that it has hit some roadblocks, especially because some apps come with customized title bars.

Microsoft apparently thought of that in advance and plans to polish the tabs integrations in apps before releasing it to the public next year.

  • YeahRrright

    Wow, in this case I might even consider going to insider builds, cause at lease according to blogs it has some love towards touch keyboard, and the stuff that is currently out in public is just pathetic…

    • M Rankin

      The keyboards pretty solid in 17134 now
      it’s OK to admit you just want the swiftkey integration
      but by your frequency level of complaining I would just wait a few builds
      or till it get pushed out to release ring uses

      • YeahRrright

        I suppose you are right. It’s just the state of touch keyboard on official release is so bad that I was almost ready to jump back in insiding just to see if it is any better there…