If you’re reading this on a PC, it’s probably on Google Chrome or Firefox — the two most popular browsers on Windows that Mashable readers use. It’s a telling example about how most tech-savvy Windows users don’t use the default browser on their machines, Internet Explorer. But how’s that going to change when Windows 8 launches later this year?
Windows 8, as you may know, has two modes: the familiar desktop, and the all-new Metro interface (for a primer on Windows 8, check out this link). Metro differs from traditional Windows in many ways, but one of the ways that’s not often talked about is that Microsoft will have final say over what apps run on it, since Windows 8 users will only be able to download Metro apps from the Windows Store.
With such ironclad control over the new operating system, would Microsoft even allow other web browsers to run in Metro? The answer is yes, and Mozilla is already hard at work developing the Metro version of Firefox, one of the company’s developers revealed on his personal blog. He also revealed a little tidbit: Browser apps will work somewhat differently than other Metro apps.
Mozilla engineer Brian R. Bondy says there are three types of Windows 8 apps: those that run solely in the classic desktop, Metro apps, and Metro-enabled browsers for the desktop. It’s the last one that Metro versions of Firefox (and presumably Google Chrome) will be.
Bondy references a Microsoft white paper that says Metro-style browsers aren’t completely confined to the Metro environment. That means, as Bondy describes, that the browser can be just as powerful as its desktop equivalent, with the ability to multitask, download files in the background and render web-based HTML5 apps in their entirety.
That’s because, if Internet Explorer 10 is any indication, that the browser is essentially the same animal whether it’s running in the desktop or Metro — it’s only the user interface that’s different. Still, that involves quite a bit of coding, and Bondy says it’s a “very large project.”
There’s a catch, though: For a browser to run in Metro, the user must pick it as the default browser. That likely won’t be an issue for most fans of Firefox and Chrome, but it does mean you won’t be able to have multiple browsers open in Metro.
How Windows 8 Tablets Could Seriously Challenge the iPad
=============================================================
SEE ALSO: Windows 8 Consumer Preview: The Good, the Bad and the Metrowww.embarcadero.com/appwave
I’m writing this article on a Windows 8 tablet. Thankfully, I’ve got a wireless keyboard and mouse as well as a dock to help the Samsung developer tablet act more like a regular PC. Microsoft made the Windows 8 Consumer Preview availablethis morning to everyone who wants to check it out. It was also kind enough to give Mashable a sneak peek.
What exactly is a consumer preview? I can tell you this: It definitely means it’s not ready for general release. It’s been a challenge trying to separate issues that are due to the inherent bugginess of a pre-release, changes that I’m just not used to, and things that are real problems. But here goes.
First, a little background: Windows 8 is a complete re-imagining of Windows. And it’s also the same. Its schizophrenic nature is due to its two modes: the familiar (yet subtly different) desktop that we’re all used to, and the Metro interface. Metro, borrowed from the Windows Phone platform, takes a hard right turn from traditional Windows: Instead of files and folders, there are touchable tiles that fire up your apps, and those apps take up the whole screen.
That’s really just scratching the surface of Metro, but let’s not get ahead of ourselves. For this look at Windows 8, I’m going to focus mainly on the bigger-picture features and what’s new since the initial developer release from last fall. Microsoft says that where the developer build was about emphasizing touch, with the consumer preview (Build 8250 for those scoring at home) it focused on showing how the mouse and keyboard is just as friendly to Metro.
My first impression: Almost, but not quite.
Metro With a Mouse & Keyboard
Microsoft has a vision, a dream even. It wants to have the same operating system running across all its devices. It’s a laudable goal, with many advantages for both Microsoft and its customers. The thing is people use different gadgets differently — you don’t do all the same things on a tablet that you do on a PC, and when you do, the experience is different.
Microsoft knows this, so Windows 8 is highly adaptable. It responds differently to touch than it does to a mouse. For example, to bring up your Settings menu with your finger, just slide in from the edge; if you have a mouse, you aim for the corner.
Making the corners the key points when operating Windows 8 with a mouse is a good choice — they’re pretty unmissable and you don’t need to be precise. However, some of the subtleties in the interface appear to be poorly thought out.
For starters, the icons don’t follow standard web “mouseover” rules. Take one example: When you point toward the lower left corner, Windows 8 (either Metro or desktop) calls up the Start screen. Or rather, it calls up anicon for the Start screen, but if you hover your mouse over it, it disappears. This goes against what websites have trained people to do for a decade: call up menus by holding your mouse over icons, then navigating through the menu by staying on top of it.
It sounds like a minor point, but it’s actually not, and the same problem bubbles up time and again from Windows 8: unintuitiveness. Metro is a beautiful and powerful interface, but it’s hard to get used to, sometimes needlessly so. Another example: the Start screen allows you to scroll left and right simply by pushing your mouse icon right up against the edges of the screen. Yet several apps (like Photos) incomprehensibly don’t do this, instead forcing you to use a scrollbar (or the mouse scroll wheel). Again, it sounds minor, but it’s everything.
Also, Metro is all about scrolling left and right. Apps like Finance look beautiful, with amazing layouts and great landscape pictures. So why have the top and bottom edges do nothing at all when you mouse against them? We’re all used to calling up docks or menus when pressing against the edge, and Metro even lets you do this via touch. It would have been helpful to keep some of that functionality when using the mouse.
Working with a keyboard was better, with intuitive navigation via arrow keys. There are some nice keyboard shortcuts (like screengrab) that you can’t replicate via touch, so it definitely opens up the experience. There was occasionally a little lag with the wireless keyboard Microsoft supplied us with, but it was something I could live with.
(lots more after the gallery)
No comments:
Post a Comment