User Interface, Gestures, and Multitasking

by Anand Shimpi and Vivek Gowri

By now you should be fairly familiar with what Windows RT’s Start Screen looks like, at least from a distance. Power on a Windows RT tablet and you’ll be greeted by the new Windows UI. A big, horizontal canvas full of live tiles, a feature that first debuted in Windows Phone 7. Based on the Metro design language, and referred to as Metro UI for much of the development cycle, a trademark dispute has forced a name change to Modern UI. There’s no getting around it, there’s a definite learning curve to the interface. It doesn’t matter if you’re used to Windows 7, OS X, Android or iOS, the touch enabled Windows RT UI is going to feel different, and probably downright wrong...at first.

If you put in the time to learn and get used to the interface however, it is easily among the best tablet user interfaces I’ve ever tried. Everything we despise Windows 8 for on the desktop makes perfect sense when viewed through tablet colored glasses.

As a recap, Windows RT (and Windows 8) relies on edge swipe gestures for much of the macro control over navigation. Full screen apps are left purposefully barren, with their focus primarily on content. The power is in what lies (virtually) beyond the edges of the screen. 

There’s no capacitive sensor array in the bezel of a Windows RT tablet, instead what the touch controller does is looks at starting position and velocity of gesture to determine whether your swipe originated on or off screen.

There are only four edge swipes you need to learn, one for each edge of the display. Swipe in from the left and you flip through apps, giving Microsoft the win for quickest task switcher among all tablets. By default a left edge swipe will switch to the previously used app, or if you just switched from that it’ll move to the next most-recently used app.

If you have a lot of apps to switch between simply left edge swipe in partially then swipe back out, revealing a more traditional task switcher (Windows + Tab also brings up this switcher). Of all of the Windows RT gestures the swipe in/out to bring up the task switcher is the most clunky, but it’s easy to get used to.

Go to the opposite side of the screen and right edge swipe in to reveal the charms bar. Here you get direct access to the software start button as well as a bunch of key tools, among them are search and settings. 

Although the appearance of the charms bar never changes, the function of these buttons do. Start always takes you to the start screen, but search and settings apply to the app currently in focus. I can’t stress how much of an advantage this is over iOS. If I need to play with an app setting on the iPad I either need to go home and to settings then find the app or hope the developer has stuck a tab somewhere in the app where I can play with options. 

Even better is the fact that I can toggle things like an app’s ability to run in the background and whether or not it’s allowed to give me notifications on the lock screen directly from the app settings page. The icing on the cake? Playing with settings never forces me out of the app itself, Windows RT simply devotes the right 1/4 of the screen to settings, leaving my app still in focus on the left. It’s perfect.

Also perfect? The ability to snap applications to the right or left edge of the screen and have a different window open in the remaining portion. This was called Metro Snap before use of the Metro name was discontinued, and it’s one of the more interesting features here. Snapping requires a screen with at least 1366 horizontal pixels, allocated as 1024 to the main window, 22 to the splitter, and 320 to the snapped application panel. It’s great for having an IM conversation or email inbox open on the side when writing, browsing, or doing essentially anything else. 

One of the biggest issues I’ve had with tablet multitasking to date is that it’s all been very focused on the active window, which makes doing things like messaging an absolute pain because you’re continually flipping between whatever you were doing (let’s say browsing the web) and the messaging application. In Windows RT though, you just snap the conversation window to the side and continue browsing, just with a narrower browser window. 

Messaging is just one usecase though - email, Facebook, Twitter, Skype video calls (their implementation is pretty cool - more on this later), music, a small browser window docked on the edge while writing in the main screen, the possibilities are endless. You could even theoretically turn it into three near-equal size windows using Aero Snap in Windows desktop, though that severely cuts down on usable space. But generally, the Snap feature gives the end user a lot of flexibility and makes multitasking a lot easier. 

Top and bottom edge swipes end up being more application specific. Swipe up from the bottom and you usually get some additional options, while swiping down from the top edge is usually more of a navigational tool (e.g. showing multiple tabs in IE10). 

Although Windows RT borrows from its iOS and Android brethren in that it will automatically pause and unload unused apps from memory, you can always manually move the process along by edge swiping down from the top and dragging the window off the bottom of the screen. This also works from the task switcher on the left side, drag over and down to the bottom of the screen to close. There’s some built in lag to ensure that you don’t accidentally quit something of importance but otherwise it works fine. 

Overall, the edge swipe gestures take some getting used to but once you’ve made it over the hump they really unlock a totally new level of tablet usage.

I believe Microsoft is on to something real here with the new Windows UI for tablets. This new OS feels ahead of the curve on major issues like multitasking, task switching and displaying multiple apps on the screen at the same time. I was always told that marketshare is lost and gained in periods of transition. Microsoft missed the first major transition to new ARM based smartphones and tablets, but it’s perfectly positioned to ride the wave to notebook/tablet convergence. In fact, when it comes to figuring out how to merge those two platforms I don’t believe Apple or Google have a reasonable solution at this point. In Apple’s world the two are distinctly separate, while Google is arguably even worse off as it doesn’t have a good notebook OS at this point (the verdict is still out on Chrome OS, as promising as the new Samsung Chromebook appears to be). It’s unclear how big this convertible/hybrid market will grow, but I see real potential here. There are users who want an iPad and I don’t believe Microsoft does anything to change their minds. The iPad and iOS remain a very polished, very accessible platform that is really optimized for content consumption and light productivity. For anyone who wanted more however, there’s now an alternative: Windows RT.

Meet Windows RT Bridging the Gap, the Dichotomy of Windows RT
POST A COMMENT

233 Comments

View All Comments

  • tbutler - Friday, October 26, 2012 - link

    Except that, at least as I read it, Metro vs desktop divides more along 'touch vs keyboard/mouse', not consumer vs power user.

    Or to put it another way - while the simplicity of Metro apps might appeal to consumers, that is trumped by the issues trying to use them with a keyboard/mouse. In fact, I'd argue that the Metro environment is *worse* for a keyboard/mouse using consumer, given how so many operations are hidden/not obvious/best used with shortcuts. Windows-C to get the Charms bar is a learned power user trick, not an average user thing.
    Reply
  • steven75 - Friday, November 02, 2012 - link

    Nailed it. The "x86 userbase will ensure a massive market for Metro apps" angle is *anything* but a sure thing. Reply
  • Dorek - Friday, November 02, 2012 - link

    "Except that, at least as I read it, Metro vs desktop divides more along 'touch vs keyboard/mouse', not consumer vs power user."

    Having used Metro apps with a mouse and keyboard, I don't see any problems. They work well on a laptop and on a desktop. I never had any problems.
    Reply
  • designerfx - Thursday, October 25, 2012 - link

    exactly. People aren't willing to buy a windows tablet and not a windows OS. It's not like buying android or ios here.

    It's simply not the same environment, the reason for android/ios is because of the app market - that is literally the singular reason to not need a windows device.
    Reply
  • khanikun - Friday, October 26, 2012 - link

    Have you even looked in the Apple's app store or Google's Play store? It's just tens of thousands of apps that do the same like 10 things and a lot of flash games converted for their respective OS. Majority of them being for non-productive uses.

    On my two Android tablets and my Android smartphone, I have like one productive app. Some free office like app, that allows me to open Office docs, but I can't edit them in any way. The rest? Games and photobooks.

    Windows RT will definitely be a big step towards making tablets more productive than a big toy. I won't bother. I'm waiting for Windows 8 Pro.
    Reply
  • steven75 - Friday, November 02, 2012 - link

    iPad has had the iWork suite since 2010. While that may not matter to businesses entrenched in Microsoft Office, it sure is enough for students that can easily convert anything to PDF and avoid all compatibility issues. Reply
  • strangis - Friday, October 26, 2012 - link

    "Really? A month from now? Can I hold you to that? It will be at least a year before Metro store gets even tens of thousands of apps"

    Just as a barometer, WP7 hit the 10,000 apps mark in under 6 months. Do you really think that it's going to take Windows 8 longer?

    And you accuse someone else of lacking objectivitiy...
    Reply
  • GuardianAngel470 - Sunday, October 28, 2012 - link

    You've completely missed the reason for the statement.

    iOS, Android, Windows Phone, WebOS, and every other OS had to build a consumer base from scratch. By extension they had to build a developer base from scratch.

    Windows RT doesn't need to do the former and by extension doesn't need to to do the latter. There are guaranteed to be millions of people running Windows 8 in a few month's time. Because Windows 8 didn't divorce Metro from its desktop and because Visual Studio 2012 Express intentionally hobbles the development of desktop applications, the developers that are guaranteed to develop for Windows 8 will be there to fill the App Store.

    It can be argued that they'll focus on the development of desktop apps sure but you're basing your opinion on OS's that were never in the same situation as Windows RT.
    Reply
  • trip1ex - Monday, October 29, 2012 - link

    Gotta agree. I just don't see a huge ramp in 3rd party apps in 1 month. And I fail to what the power of Windows desktop is when RT will be running on ARM.

    For the problems MS will have look no further than the Zune except now you are also at an apps/developer support disadvantage.

    And it doesn't just matter if RT gets apps but how those apps compare to apps on the other systems. I remember using the Mac 5 years ago when many programs were also on the Mac, but were behind the Windows versions in features and worked worse in general.

    That being said I doubt most people use that many apps. We mostly surf and check email on our IPad.
    Reply
  • guidryp - Thursday, October 25, 2012 - link

    Both of these reviews feel like a whitewash to me.

    No mention of how buggy software is, or slowdowns and crashes that many others are reporting.

    It says others are making snap judgements, but this is sweeping the defects under the rug.

    Not what I expect from Anandtech.
    Reply

Log in

Don't have an account? Sign up now