Interface

Via TechCrunch

-----

At SXSW this afternoon, Google provided developers with a first glance at the Google Glass Mirror API, the main interface between Google Glass, Google’s servers and the apps that developers will write for them. In addition, Google showed off a first round of applications that work on Glass, including how Gmail works on the device, as well as integrations from companies like the New York Times, Evernote, Path and others.

The Mirror API is essentially a REST API, which should make developing for it very easy for most developers. The Glass device essentially talks to Google’s servers and the developers’ applications then get the data from there and also push it to Glass through Google’s APIs. All of this data is then presented on Glass through what Google calls “timeline cards.” These cards can include text, images, rich HTML and video. Besides single cards, Google also lets developers use what it calls bundles, which are basically sets of cards that users can navigate using their voice or the touchpad on the side of Glass.

It looks like sharing to Google+ is a built-in feature of the Mirror API, but as Google’s Timothy Jordan noted in today’s presentation, developers can always add their own sharing options, as well. Other built-in features seem to include voice recognition, access to the camera and a text-to-speech engine.

Glass Rules

Because Glass is a new and unique form factor, Jordan also noted, Google is setting a few rules for Glass apps. They shouldn’t, for example, show full news stories but only headlines, as everything else would be too distracting. For longer stories, developers can always just use Glass to read text to users.

Essentially, developers should make sure that they don’t annoy users with too many notifications, and the data they send to Glass should always be relevant. Developers should also make sure that everything that happens on Glass should be something the user expects, said Jordan. Glass isn’t the kind of device, he said, where a push notification about an update to your app makes sense.

Using Glass With Gmail, Evernote, Path and Others

As part of today’s presentation, Jordan also detailed some Glass apps Google has been working on itself, and apps that some of its partners have created. The New York Times app, for example, shows headlines and then lets you listen to a summary of the article by telling Glass to “read aloud.” Google’s own Gmail app uses voice recognition to answer emails (and it obviously shows you incoming mail, as well). Evernote’s Skitch can be used to take and share photos, and Jordan also showed a demo of social network Path running on Glass to share your location.

So far, there is no additional information about the Mirror API on any of Google’s usual sites, but we expect the company to release more information shortly and will update this post once we hear more.

Via Technologizer

-----

How a little-known 1971 machine launched an industry.

Forty years ago, Nutting Associates released the world’s first mass-produced and commercially sold video game, Computer Space. It was the brainchild of Nolan Bushnell, a charismatic engineer with a creative vision matched only by his skill at self-promotion. With the help of his business partner Ted Dabney and the staff of Nutting Associates, Bushnell pushed the game from nothing into reality only two short years after conceiving the idea.

Computer Space pitted a player-controlled rocket ship against two machine-controlled flying saucers in a space simulation set before a two-dimensional star field. The player controlled the rocket with four buttons: one for fire, which shoots a missile from the front of the rocket ship; two directional rotation buttons (to rotate the ship orientation clockwise or counterclockwise); and one for thrust, which propelled the ship in whichever direction it happened to be pointing. Think of Asteroids without the asteroids, and you should get the picture.

During play, two saucers would appear on the screen and shoot at the player while flying in a zig-zag formation. The player’s goal was to dodge the saucer fire and shoot the saucers.

Considering a game of this complexity playing out on a TV set, you might think that it was created as a sophisticated piece of software running on a computer. You’d think it, but you’d be wrong–and Bushnell wouldn’t blame you for the mistake. How he and Dabney managed to pull it off is a story of audacity, tenacity, and sheer force-of-will worthy of tech legend. This is how it happened.

continue to the full story...

Via ars technica

-----

At the Google I/O conference earlier this year, Google revealed that the Android Market would come to the Google TV set-top platform. Some evidence of the Honeycomb-based Google TV refresh surfaced in June when screenshots from developer hardware were leaked. Google TV development is now being opened to a broader audience.

In a post on the official Google TV blog, the search giant has announced the availability of a Google TV add-on for the Android SDK. The add-on is an early preview that will give third-party developers an opportunity to start porting their applications to Google TV.

The SDK add-on will currently only work on Linux desktop systems because it relies on Linux's native KVM virtualization system to provide a Google TV emulator. Google says that other environments will be supported in the future. Unlike the conventional phone and tablet versions of Android, which are largely designed to run on ARM devices, the Google TV reference hardware uses x86 hardware. The architecture difference might account for the lack of support in Android's traditional emulator.

We are planning to put the SDK add-on to the test later this week so we can report some hands-on findings. We suspect that the KVM-based emulator will offer better performance than the conventional Honeycomb emulator that Google's SDK currently provides for tablet development.

In addition to the SDK add-on, Google has also published a detailed user interface design guideline document that offers insight into best practices for building a 10-foot interface that will work will on Google TV hardware. The document addresses a wide range of issues, including D-pad navigation and television color variance.

The first iteration of Google TV flopped in the market and didn't see much consumer adoption. Introducing support for third-party applications could make Google TV significantly more compelling to consumers. The ability to trivially run applications like Plex could make Google TV a lot more useful. It's also worth noting that Android's recently added support for game controllers and other similar input devices could make Google TV hardware serve as a casual gaming console.

Via Slash Gear

-----

Apple released its new OS X Lion for Mac computers recently, and there was one controversial change that had the technorati chatting nonstop. In the new Lion OS, Apple changed the direction of scrolling. I use a MacBook Pro (among other machines, I’m OS agnostic). On my MacBook, I scroll by placing two fingers on the trackpad and moving them up or down. On the old system, moving my fingers down meant the object on the screen moved up. My fingers are controlling the scroll bars. Moving down means I am pulling the scroll bars down, revealing more of the page below what is visible. So, the object moves upwards. On the new system, moving my fingers down meant the object on screen moves down. My fingers are now controlling the object. If I want the object to move up, and reveal more of what is beneath, I move my fingers up, and content rises on screen.

The scroll bars are still there, but Apple has, by default, hidden them in many apps. You can make them reappear by hunting through the settings menu and turning them back on, but when they do come back, they are much thinner than they used to be, without the arrows at the top and bottom. They are also a bit buggy at the moment. If I try to click and drag the scrolling indicator, the page often jumps around, as if I had missed and clicked on the empty space above or below the scroll bar instead of directly on it. This doesn’t always happen, but it happens often enough that I have trained myself to avoid using the scroll bars this way.

So, the scroll bars, for now, are simply a visual indicator of where my view is located on a long or wide page. Clearly Apple does not think this information is terribly important, or else scroll bars would be turned on by default. As with the scroll bars, you can also hunt through the settings menu to turn off the new, so-called “natural scrolling.” This will bring you back to the method preferred on older Apple OSes, and also on Windows machines.

Some disclosure: my day job is working for Samsung. We make Windows computers that compete with Macs. I work in the phones division, but my work machine is a Samsung laptop running Windows. My MacBook is a holdover from my days as a tech journalist. When you become a tech journalist, you are issued a MacBook by force and stripped of whatever you were using before.

I am not criticizing or endorsing Apple’s new natural scrolling in this column. In fact, in my own usage, there are times when I like it, and times when I don’t. Those emotions are usually found in direct proportion to the amount of NyQuil I took the night before and how hot it was outside when I walked my dog. I have found no other correlation.

The new natural scrolling method will probably seem familiar to those of you not frozen in an iceberg since World War II. It is the same direction you use for scrolling on most touchscreen phones, and most tablets. Not all, of course. Some phones and tablets still use styli, and these phone often let you scroll by dragging scroll bars with the pointer. But if you have an Android or an iPhone or a Windows Phone, you’re familiar with the new method.

My real interest here is to examine how the user is placed in the conversation between your fingers and the object on screen. I have heard the argument that the new method tries, and perhaps fails, to emulate the touchscreen experience by manipulating objects as if they were physical. On touchscreen phones, this is certainly the case. When we touch something on screen, like an icon or a list, we expect it to react in a physical way. When I drag my finger to the right, I want the object beneath to move with my finger, just as a piece of paper would move with my finger when I drag it.

This argument postulates a problem with Apple’s natural scrolling because of the literal distance between your fingers and the objects on screen. Also, the angle has changed. The plane of your hands and the surface on which they rest are at an oblique angle of more than 90 degrees from the screen and the object at hand.

Think of a magic wand. When you wave a magic wand with the tip facing out before you, do you imagine the spell shooting forth parallel to the ground, or do you imagine the spell shooting directly upward? In our imagination, we do want a direct correlation between the position of our hands and the reaction on screen, this is true. However, is this what we were getting before? Not really.

The difference between classic scrolling and ‘natural’ scrolling seems to be the difference between manipulating a concept and manipulating an object. Scroll bars are not real, or at least they do not correspond to any real thing that we would experience in the physical world. When you read a tabloid, you do not scroll down to see the rest of the story. You move your eyes. If the paper will not fit comfortably in your hands, you fold it. But scrolling is not like folding. It is smoother. It is continuous. Folding is a way of breaking the object into two conceptual halves. Ask a print newspaper reporter (and I will refrain from old media mockery here) about the part of the story that falls “beneath the fold.” That part better not be as important as the top half, because it may never get read.

Natural scrolling correlates more strongly to moving an actual object. It is like reading a newspaper on a table. Some of the newspaper may extend over the edge of the table and bend downward, making it unreadable. When you want to read it, you move the paper upward. In the same way, when you want to read more of the NYTimes.com site, you move your fingers upward.

The argument should not be over whether one is more natural than the other. Let us not forget that we are using an electronic machine. This is not a natural object. The content onscreen is only real insofar as pixels light up and are arranged into a recognizable pattern. Those words are not real, they are the absence of light, in varying degrees if you have anti-aliasing cranked up, around recognizable patterns that our eyes and brain interpret as letters and words.

The argument should be over which is the more successful design for a laptop or desktop operating system. Is it better to create objects on screen that appropriate the form of their physical world counterparts? Should a page in Microsoft Word look like a piece of paper? Should an icon for a hard disk drive look like a hard disk? What percentage of people using a computer have actually seen a hard disk drive? What if your new ultraportable laptop uses a set of interconnected solid state memory chips instead? Does the drive icon still look like a drive?

Or is it better to create objects on screen that do not hew to the physical world? Certainly their form should suggest their function in order to be intuitive and useful, but they do not have to be photorealistic interpretations. They can suggest function through a more abstract image, or simply by their placement and arrangement.

In the former system, the computer interface becomes a part of the users world. The interface tries to fit in with symbols that are already familiar. I know what a printer looks like, so when I want to set up my new printer, I find the picture of the printer and I click on it. My email icon is a stamp. My music player icon is a CD. Wait, where did my CD go? I can’t find my CD?! What happened to my music!?!? Oh, there it is. Now it’s just a circle with a musical note. I guess that makes sense, since I hardly use CDs any more.

In the latter system, the user becomes part of the interface. I have to learn the language of the interface design. This may sound like it is automatically more difficult than the former method of photorealism, but that may not be true. After all, when I want to change the brightness of my display, will my instinct really be to search for a picture of a cog and gears? And how should we represent a Web browser, a feature that has no counterpart in real life? Are we wasting processing power and time trying to create objects that look three dimensional on a two dimensional screen in a 2D space?

I think the photorealistic approach, and Apple’s new natural scrolling, may be the more personal way to design an interface. Apple is clearly thinking of the intimate relationship between the user and the objects that we touch. It is literally a sensual relationship, in that we use a variety of our senses. We touch. We listen. We see.

But perhaps I do not need, nor do I want, to have this relationship with my work computer. I carry my phone with me everywhere. I keep my tablet very close to me when I am using it. With my laptop, I keep some distance. I am productive. We have a lot to get done.

Via Engadget

By Ross Rubin

-----

Last week's Switched On discussed how Lion's feature set could be perceived differently by new users or those coming from an iPad versus those who have used Macs for some time, while a previous Switched On discussed how Microsoft is preparing for a similar transition in Windows 8. Both OS X Lion and Windows 8 seek to mix elements of a tablet UI with elements of a desktop UI or -- putting it another way -- a finger-friendly touch interface with a mouse-driven interface. If Apple and Microsoft could wave a wand and magically have all apps adopt overnight so they could leave a keyboard and mouse behind, they probably would. Since they can't, though, inconsistency prevails.

Yet, while the OS X-iOS mashup that is Lion exhibits is share of growing pains, the fall-off effect isn't as pronounced as it appears it will be for Windows 8. The main reasons for this are, in order of increasing importance, legacy, hardware, and Metro.

Legacy. Microsoft has an incredibly strong commitment to backward compatibility. As long as Microsoft supports older Windows apps (which will be well into the future), there will be a more pronounced gap between that old user interface and the new. This will likely become more of a difference between Microsoft and Apple over time. For now, however, Apple is also treading lightly, and several of Lion's user interface changes -- including "natural" scrolling directions, Dashboard as a space, and the hiding of the hard drive on the desktop -- can be reversed. Even some of Lion's "full-screen" apps are only a cursor movement away from revealing their menus.

Hardware. As Apple continues to keep touchscreens off the Mac, it brings over the look but not the input experience of iPad apps, relying instead on the precision of a mouse or trackpad. Therefore, these Mac apps do not have to embrace finger-friendliness. In contrast, the "tablet" UI of Windows 8 is designed for fingertips and therefore demands a cleaner break with an interface designed for mice (although Microsoft preserves pointer control as well so these apps can be used on PCs without touchscreens).

Metro. A late entrant to the gesture-driven touchscreen handset wars, Microsoft sought to differentiate Windows Phone 7 with its panoramic user interface. When Joe Belfiore introduced Windows Phone 7 at Mobile World Congress in 2010, he repeatedly noted that "the phone is not a PC." That's an accurate assessment, and perhaps one worth repeating in light of all the feedback Microsoft ignored over the years in the design of Pocket PC and Windows Mobile. It also of couse holds true beond the user interface for design around context and support of location-based services.

But now that the folks in Redmond have created an enjoyable phone interface, have things actually changed? Was it true only that the phone and PC shoud not have the same old Windows interface, or is it also still true that the PC and phone should not have the same new Windows Phone interface? Was it the nature of the user interface itself that was at fault, or the notion of the same user interface across PC and phone regardless of how good it is?

There is certainly room for more consistency across PCs, tablets and handsets. However, Microsoft did not just differentiate Windows Phone 7 from iOS and Android, it differentiated it from Windows as well. And that is the main reason why the shift in context between a classic Windows app and a "tablet" Windows 8 app seems more striking at this point than the difference between a classic Mac app and "full screen" Lion app. Lion's full-screen apps could be the new point of crossover with Windows 8's "tablet" user interface mode. Based on what we've seen on the handset side, it is certainly possible for developers to write the same apps for the iPhone and Windows Phone 7, but these are generally simpler apps (and then there are games, which generally ignore most user interface conventions anyway).

Apple and Microsoft are both clearly striving for a simpler user experience, but Microsoft is also trying to adapt its desktop OS to a new form factor in the process of doing so. The balancing act for both companies will be making their new combinations of software and hardware (from partners in the case of Microsoft) embrace a new generation of users while minimizing alienation for the existing one.

-----

Personal comments:

See also this article