Yesterday we brought you pictures of the touchscreen-loving user interface on Sony’s genre-straddling camera concept, so what better way to improve on that than with video and a few specs? Beyond the break you shall find one of those excessively stylized promotional vids you know and love to hate, but tolerating the fluff with reward you with some nice hints about how the shooter is operated plus finally some word on what’s inside. An Exmor APS HD CMOS sensor is touted, along with the accompanying capability to shoot 1080p AVCHD video. While we still find the design of these interchangeable lens cameras ridiculously appealing, there is one thing we have to complain about and that’s the clunky naming scheme. Please Sony, give us something sexier to call it than an “ultra-compact camera concept” — how about the Sony Beta, it comes after Alpha and is typically used to denote an unfinished product. You can have that one for free.
We know that it ain’t always practical or desirable to put money down on a phone every time a new OS or interface comes out — so what is a gadget hound to do when they realize their hardware won’t be supported by Windows Phone 7 Series? Well, if you’re anything like these enterprising individuals you roll your own. Both Jaxbot and LeSScro, members of the XDA Developers forum, have skins in the works that mimic the new OS on WinMo devices with varying degrees of success. The work of the former is still pretty slow and buggy but it does offer some functionality — including info on live tiles and the ability to see upcoming appointments on your lock screen. The latter theme, on the other hand, sports time, date, and notifications on the lock screen, profile settings, transitional animations, a handful of hubs (including games, media, and Office), and an apps launcher. Check out the source links for more info — but not before checking out the demo videos after the break.
Maybe it’s the lack of a banging soundtrack, but we’re finding ourselves somewhat underwhelmed by these first video appearances by the highly anticipated Symbian^4 user interface. What we’re shown is a now familiar layout for touchscreen devices, with a trio of home screens that can be customized with widgets and live information trinkets such as a clock and a weather app. It is, as promised, very touch-centric, but it is by no means revolutionary. Both videos are titled as mere “first glimpse” offerings, however, so the eternal optimist in us likes to believe that there’ll be plenty more to get excited about as we move closer to that early 2011 launch. See them after the break and let us know what you think.
Our recent chance encounter with a multitouch-friendly iteration of HTC’s Sense UI turns out to have been a preview of the company’s latest version of the software. Announcing that it has “enhanced” the already quite delectable skin, HTC has noted it’ll be available preloaded on the brand new Desire and Legend handsets, and as a free download for the venerable Hero. So what’s new? The press event this morning told us about Leap, the new pinching function that allows you to view all your home screens at once (see above), and Friend Stream, which aims to be your social media aggregator du jour with its one stream combining Facebook, Twitter and Flickr updates. There’s also a new newsreader application and widget, along with additional improvements to the browser and web client. You’ll find the full PR after the break and early impressions of the new interface in our hands-on with the new phones.
Update: See a full walkthrough of the new UI in a video after the break.
It’s hard to believe this homegrown home screen actually runs as quickly as the video demo (posted up after the break) shows, but even if it’s just 89.877 percent as fast, we have a good idea we’d be interested. TAT Home is a gesture-powered 3D home screen for Android, and it relies heavily on cascading windows and finger flicks in order to improve your navigational efficiency. Clueless as to what we’re referring to? Jump past the break and mash play, and then surf on over to the source link to sign up for the preview program.
We already know all of you have more than a few ideas about what TiVo should or will bring to the table March 2, but an anonymous tipster claiming knowledge of recent developments in the beta program let us know what may be coming. Although it began as simple bug fixes for the Series 3 now an all new user experience is on the way that the company expects to perfect the DVR. The UI is speedy again, rising to the level of the older Series 2 but with new high res, crisp widescreen elements designed to look great on your HDTV. Other fixes that should have the faithful drooling are a capacity meter for add-on drives and Tivo Desktop enhancements including “Sling-esque” features. Naturally, add-ons like Netflix, Amazon, Blockbuster and even Facebook lead the app charge with faster and easier program access. No real details on what’s new on the hardware side, but that QWERTY remote seems to be a sure bet, we’ll be counting down the next 19 days until we know for sure.
Could gesture recognition become the successor to touchscreen? And if it does, what would it be like to use it to interact with our gadgets.
A prototype design shows a cube-shaped device that can be used to access music, look up recipes and flick through photos.
The idea called Gesture Cube senses hand movements made close to the screen and translates them into commands for the device. It’s an user interface idea for the next generation of digital devices, says German company Ident, whose technology powers the device.
The cube has sensors that detect the approach of a hand and transmit the coordinates to the electronics. Functions such as pulling up the playlist or activating the browser can then be assigned to the co-ordinates. Finally, touching a switch or button finally activates the task.
For now, the idea is the concept stage. But with the interest in gesture recognition, it’s to see that this idea could find a way into real world devices soon.
Check out the video to see the Gesture Cube concept at work.
Tablets today are thought to be made in one of two ways: Upsizing a smartphone or downsizing a laptop. Many of these new tablets are decent, but both methods render something less than the perfect tablet.
These tablets—not the convertible laptops of the past decade, but real single-pane slate-like ones—are in various stages of development, and have various operating systems. You have your iPad, JooJoo, a bunch of Android tablets, HP’s slate, the as-yet-unseen Chrome OS tablets, the equally mysterious Courier, and the Microsoft-partner tablets that currently run a reasonably full version of Windows 7. You can easily categorize nearly all of these into two basic design philosophies: The iPad and Android tablets come from platforms originally designed with smartphones in mind; the Windows 7 tablets fully embrace the traditional desktop-metaphor OS; the Chrome OS and JooJoo strip out most of the desktop, leaving—perhaps awkwardly—just the browser.
But what about the Courier? If there is such a thing as a “third” option, it’s what Microsoft dreamed up over the last year. Microsoft, already has its fingers in both ends of the pie, but Courier represents a truly different envisioning. Could the tablet that we’ve really been waiting for come from Redmond? Maybe, but at the moment the fate of Courier isn’t clear at all.
Making Phones Bigger
First you have the method of taking a phone interface and making it bigger. That’s the iPad, the Android tablets and, in some modes, Lenovo’s Ideapad U1. Android tablets are basically doing an upscaling of the base Android interface, whereas the iPad also makes customized first-party apps to take advantage of the increased screen space. Both can theoretically run all the apps their little brothers can. Lenovo is also doing something very similar by creating a completely customized ground-up OS that’s sorta widget-based, which is basically a smartphone in everything but name. (When docked, the U1 tablet becomes a screen for a Windows computer, but that’s another story.)
So far, going up from a phone OS seems to be the better bet, compared to simplifying a desktop-style OS. But the phone experience is far from perfect.
When you work off of a smartphone base, you theoretically already have the touch interface locked in, because Android, iPhone, Palm and other smartphones now eschew the skinny stylus for your fat finger. It’s a more natural pointing device for a tablet, since you can hold the device in one hand while pointing at it with the other. If you were to use a stylus, you’d have to grip the tablet with your forearm, like a watermelon or a baby, in order to provide a stable enough surface to press down upon with a pen.
Also, because you’re working with a phone-up methodology, you get to sell a tablet relatively cheap by using high-end phone parts rather than low-end netbook parts. For example, you have Android tablets that are made from ARM processors and Nvidia Tegra graphics, which are basically meant to run high-end phones. Then there’s the Apple A4 processor, which is also ARM-based.
So for these manufacturers, they already have the type of modularized applications with minimal multitasking (in Apple’s case, basically none) that can run decently well on low-powered hardware. Plus, this type of system requirements basically guarantees that you’ll have a better battery life than the alternative.
Jesus already sung much of the praises of this approach when he correctly surmised that the iPad would have this style of operating system. But what about the negatives?
If you’re building a tablet from a phone OS, you would fail to have a completely stand-alone device, in the sense that a laptop is completely standalone. You couldn’t have file access to dump photos, video and other media onto, you’d have to sync it to something else once in a while to get everything you need. And you have to go through a marketplace instead of installing stuff like a computer.
There is also no real way for apps to interact with each other. There’s copy and paste on smartphones, and certain apps can read data files from certain other apps (like the contact list), but there’s no way to interact like dragging and dropping files across applications. In the iPhone, you can’t even multitask to work on two things simultaneously. You can on Android, but there’s minimal interaction between applications. That’s not saying it can’t be done, it’s just not so entrenched in the base OS or the base philosophy that application developers don’t do it very often. If the OS maker doesn’t do it, developers won’t either.
Also, because phones are a very isolated experience, App Stores make it much easier to find apps that are both customized for your device and safe to install. This is great for phones, since stability is important, but when you’re getting into higher-performance devices, you want the ability to choose what apps you want, not just pick from the ones that Apple or Google deem OK for you to consume. And since this kind of tablet is adapted from the phone ecosystem, that’s the only choice you have.
To have a very good experience on any sort of serious computing device (not a phone), you need interactivity. An example on the Mac is the way your Mail application knows if someone is online in iChat, and shows a little light by his name, telling you that you can just IM him instead of emailing. Interactivity like this is part of the base design experience of Courier, judging on the videos we posted. You can move parts of each application easily into any other application, and each piece knows what’s being dumped onto it. The current state of phones can’t, and don’t this co-mingling philosophy engrained into it.
Peripherals is something else a phone-based OS can’t handle well. You’re limited to a specific number of device accessories that needs to be vetted in order to ensure compatibility. Even the iPad, which has a few more accessories than the iPhone (like a keyboard), doesn’t have nearly the amount of compatibility as a desktop. A tablet needs to learn this lesson from desktops in order to be truly useful. Plug in a keyboard? Sure. A firewire camera to have the device act as a target storage device? Absolutely. Another tablet, so you can have twice the amount of display area? Why the hell not. Print? Yes.
All this stuff is doable on phone devices, if developers wanted to. Hell, anything is possible if you want it to be. None of this stuff is against the laws of physics, it’s just a matter of wanting to put it in. There’s no reason why these phone-based OSes can’t accept peripherals, multitask, and do everything better than a phone. It’s just against the design philosophy.
But not all of this is software. There are certain hardware expectations that can’t be met with the current batch of phone OSes. If you’re looking at devices on a curve, you have your phone, then your tablet, then your laptop and your desktop. As the size of a increases, your expectation for power does too, and battery life decreases in accordance. So theoretically, in a tablet device, you’d want to have one significant step up in performance over phones, which we’re not seeing in these devices. I’m not talking just running the same applications faster, with upscaled graphics, I’m talking entirely new things you can only do with increased processing power. Stuff like true multitasking, games that are actually noticeably better than cellphone games, light media editing (not as good as a laptop, of course) and media playback of all kinds, handling all sorts of codecs.
That’s right, people expect more functionality and power with that bigger screen. Android’s tablets run Android apps pretty fast, but not so fast that they’re on an entirely new level. Widget-ized computing may prove to be practical, something people need as a second device. But for anybody in need of real heavy-duty computing, like Photoshop photo editing or Final Cut video processing, the design of a tablet simply won’t do.
Shrinking PCs Down
Then, you have the people who have taken a windows-style desktop-metaphor interface and simplified it for a tablet. There’s the HP slate, which runs Windows 7 but, knowing HP, will come with a friendly TouchSmart skin to hide Windows from sight while you’re doing basic media and (hopefully) social stuff. There are various other Windows 7 tablets, including the Archos 9, basically just Windows 7 machines stripped of their keyboard. (Some have styluses.)
What makes no sense about the new crop of Windows-powered tablets is that they are based on a design concept that is already proven not to work. You’ll recall back to the first time Microsoft tried these tablets, with Windows XP Tablet PC Edition, around the turn of the century, and you’ll remember that although the premise was neat, the execution had no unique functionality, no specific base of great apps, from Microsoft or anybody else. It was just a regular laptop with a stylus interface thrown in. What has changed? Now you can use your finger, instead:
There are benefits: Excellent peripheral support, the ability to install custom applications, true multitasking and cross-app interactivity, enhanced media performance, etc. In short, everything you expect from a low-powered Windows laptop, you can more or less expect here. But that extra boost of juice, that ongoing background chatter, demand more on the system. The downside is that battery is never remotely as good, and you have to deal with old-world Windows issues, like slower boot times, sleep issues, and, yes, viruses.
HP has worked hard to sell the concept of the touch PC with their TouchSmart platform. We have seen the desktop all-in-one TouchSmarts running multitouch Windows 7 but there wasn’t a lot of software for them. Now, HP appears to be pinning its hopes to the slate, presumably giving a nice “tablet” interface on top of Windows 7 when you need it, but with the ability to pop back into desktop mode when you don’t. That’s fine, better even, but it’s not a coherent computing experience.
Since it’s ultimately a desktop OS, it’s not designed for the type of input schemes you have on tablets. Besides, what happens when something running in the background crashes or demands attention? Nothing will shake you from your tablet reverie like an unexpected alert from the good people of Norton that your PC is in grave danger of being violated. Unless the tablet-friendly environment is more than skin deep, like the ones phone developers now use to hide Windows Mobile, the whole thing is a wash. By delaying on the Courier and promoting Windows 7 touch tablets, Microsoft’s making the same kind of mistake that made WinCE devices (Windows Mobile) slow and clunky. They’re offering up their standard base operating system and just telling people to add a skin on top, which is not the way to a tablet revolution.
Desktop Lite: The Browser-Only Approach
Frankly, we’re not sure where to put JooJoo and the mysterious Chrome OS. Their philosophy? Why design a whole new OS when you can take the screen most people stare at most often—the web browser—and effectively limit your OS to that. Sure, web apps are only going to get better, richer. But this approach seems to take the limitations of both the phone and the desktop-metaphor OS, with almost none of the benefits of either.
Everything we’ve seen from the Chrome OS, both early on and more recently, suggests that it is typical white-on-black boring Google desktop style. We hope there’s a trick or two up its sleeve, because if it’s just a Chrome browser in a box, it might suffer.
We know more about the JooJoo. What’s nice about it is that, presumably like the Chrome, its browser is a real WebKit PC browser, not a skimpy mobile one, so it supports Flash and Silverlight, and therefore Hulu, YouTube in HD, and other great video experiences. It does have a 1MP webcam, as well, but it’s only for “video conferencing,” if and when a browser-based video Skype comes along.
What We Need Is a Third Approach
The tablet operating system problem is one that no one has actually solved in the thirty-something years of personal computing, even though tablets have been in the public’s imagination for at least that long.
The biggest players, Apple, Google and Microsoft have huge investments in both desktop and mobile software, and seem to attack this tablet problem from attacking with both Android and Chrome OS. They’re all using their previous knowledge to get a head start. This is bad. Neither of these two solutions is optimal.
Surprisingly enough, it’s Microsoft—preoccupied as it is with mobile and desktop—that’s perhaps closest to this golden mean of tablets.
If you watch the Courier video above, you’ll notice that it’s an entirely new class of interface. It doesn’t have anything reminiscent of applications, which are the way phones do it, and it doesn’t have the traditional windowing (lower-case) for programs, which is what desktops use. It’s kinda just one big interface where everything talks to everything else, where you can do stuff in a natural way that makes sense.
Or take a look at this video. Again, it’s neither phone nor desktop—it’s designed with finger pointing in mind, optimized for this middle-ground in screen size. This is just a concept render, but it serves the point: We’re looking for something completely new with an interface that “just works” for the device, giving you features from the desktop-side such as multitasking, serious computing and the ability to run any app without having to go through a locked-down application store funnel. But we also don’t want to sacrifice the gestures, fingerability or light-weightness that you gain from smartphones.
It might never happen. It takes years and massive amounts of manpower to create a new operating system. Microsoft’s taking forever just getting Windows Phone into the 21st century. While we have faith (somehow) that Microsoft will revamp its mobile franchise in its 7th iteration, it’s unlikely that they would also then push out an entirely new operating system anytime in the next few years. More problematic is the recent insistence by Steve Ballmer at CES that Windows 7 tablets are the solution, when they very clearly are not.
If not Microsoft, then who? Apple and Google have already shown what they plan to do in the tablet space—and their operating systems may grow and develop in ways only hinted at now. The iPhone platform is not bad, and if they can break through the glass ceiling described above, it could be the answer. Google Chrome OS could also manifest itself in unexpected ways, even if we currently don’t have too much optimism. Until that day arrives—or until the unlikely event that an upstart designs a seriously revolutionary OS and accompanying hardware platform to deliver it on—we’ll have to make do with our big phones and keyboardless laptops.
At this particular point, 50-something days away from the earliest iPad deliveries, we doubt too many people are up in arms about the iPad’s ability to act as a jumbo iPhone. On the other hand, if we told you you can take pretty much the entire iPad experience and distill it down to your iPhone OS device, well you’d probably care a lot more, wouldn’t you? To get that extra 3D flavor to your UI, including the fetching iBooks shelf and other iPad-specific touches, you’ll need a jailbroken iPhone or iPod touch, access to the Cydia app store, and the manpower to click past the break for the full instructional video. Come on, you know you want to.
The iPad is a gargantuan iPhone, perhaps more precisely than many hoped. But, if you look closely, you can see hints of what’s truly coming next.
There are a few new scraps of gestures and interface bits, all thanks to the larger screen, which you can see sprinkled throughout the keynote video:
• True multi-finger multitouch Two finger swipes, three finger twirls—multitouch gestures that weren’t really possible on the iPhone’s tiny screen, unless you’re a mouse. This is what people were excited about, and we only get a taste. Though, the gesture Phil uses to drag multiple slides in Keynote, using two hands, looks a bit awkward and belabored.
• Popovers The most significant new UI element of the iPad vs. the iPhone are popovers, which you see all over the place when you need to dive further into the interface, or make a choice from a list (since blowing up lists to full screen size doesn’t make a whole lot of sense now). A box pops up, and has a list of choices or options, which might take you down through multiple levels of lists, like you see in the demo of Numbers, with selecting functions to calculate. Gruber has more on popovers, and why they’re significant, here.
• Media Navigator In some ways, the media navigator Phil Schiller shows off in iWork is the most interesting bit to me: That’s what Apple sees as replacing a file browser in this type of computer. It’s a popover too, technically.
• Long touches and drags Lots of touch, hold and drag, something you didn’t see much of in the iPhone. With more UI elements, and layers of them, you need a way of distinguishing what type of motion action you’re trying to engage.
These are all pretty basic, so far, building right on top of the iPhone’s established interface, but it points to the future: More fingers, more gestures, more layered UI elements and built-in browsers.
This is site is run by Sascha Endlicher, M.A., during ungodly late night hours. Wanna know more about him? Connect via Social Media by jumping to about.me/sascha.endlicher.
We know that it ain’t always practical or desirable to put money down on a phone every time a new OS or interface comes out — so what is a gadget hound to do when they realize their hardware won’t be supported by 
We already know all of you have 
To have a very good experience on any sort of serious computing device (not a phone), you need interactivity. An example on the Mac is the way your Mail application knows if someone is online in iChat, and shows a little light by his name, telling you that you can just IM him instead of emailing. Interactivity like this is part of the base design experience of Courier, judging on the videos we posted. You can move parts of each application easily into any other application, and each piece knows what’s being dumped onto it. The current state of phones can’t, and don’t this co-mingling philosophy engrained into it.
