You don’t have to use a smartphone for more than a week to amass a staggering amount of crap on it, from text messages and phone numbers to personal settings and photo libraries, and as with your laptop or desktop, a significant portion of this crap is stuff that you want to keep. And mobile phone backup isn’t just a matter of keeping copies of data that you consciously archive every day, like contacts, photos and notes – it’s about keeping copies of information that you didn’t even know you wanted. How many times have you needed to dig through an old text message conversation? Referred back to your received call list to recover a number you didn’t save? People: back it up. You’ll feel better.

By platform:

iPhone

If you’ve got an iPhone, there’s a good chance you’ve already sat through – and been annoyed by – its backup routine. iTunes updates your iPhone’s backups at every sync, which makes users’ lives a bit easier, and guarantees some kind of safety net by default. But! As with most fully automated systems, iTunes backup is kind of enigmatic. It just sort of… happens.

What it’s doing is performing a full backup equivalent. In other words, instead of just mirroring your entire device as a big image file, it’s extracting all the useful bits, so it can restore your iPhone as if it had undergone a full, mirrored backup. This includes, among other things, bookmarks, app settings and data (including in-app purchases, but not the apps themselves), contacts, call history, Mail accounts, SMSes, videos and photos. In other words, pretty much everything. Backups are performed automatically, and restoring to one is a simple matter of plugging in your iPhone, alt-clicking on its icon in iTunes and selecting “Restore from Backup”.

Crucially, this is different from selecting “Restore” in the device summary page: doing that will restore from a clean, factory-default image, which will delete all your personal data. Not what we’re trying to do here! (Though if you attempt to do this, you will be prompted to perform a backup, which should be a red flag.)

iTunes stores its backups as archived files in semi-cryptic directories, so if you want to pull them out of the close iTunes system for proper backup, i.e. to an external HDD or online storage solution, you can find them here:

On a Mac: ~/Library/Application Support/MobileSync/Backup/

On Windows XP: Documents and Settings(username)Application DataApple ComputerMobileSyncBackup

On Windows Vista: Users(username)AppDataRoamingApple ComputerMobileSyncBackup

To add a backup to to iTunes, simply copy it back to its default directory, and it should show up as a restore option, labelled by date, when you’re setting up a wiped or recently capital “R” Restored iPhone or iPod Touch.

Android

Google’s philosophy with Android backup and sync has been translucent, perhaps to a fault: Since it depends so much on web services, it doesn’t need to be backed up! It’s already backed up, in the cloud! We’re freakin’ Google, y’all! THIS IS THE FUTURE! (Carried to its logical conclusion, this is the Chrome OS ethos. Anyway.) This is fine, and can be put to good use: Gmail and Gcal are always safe, and your contacts can be added to your Google account too – should you designate them to be saved as Google contacts, not just SIM or Phone contacts. To do this:

1. Open your Contacts list
2. Press the Menu button
3. Select Import
4. Tick the “Google Contacts” box

But for anyone who wants to back up more than their Google-service-based info, this doesn’t really help. For that, you’ll need to go third-party. There are lots of backup apps for Android, but they’re all paid, either immediately or after a free trial. I assume just go with the best free(ish) solutions, all of which you can find by searching for their names in the Android Market.

Backup apps on Android are split into two types: the all-in-one apps that sync your data to a single file, and the piecemeal apps. Unfortunately, the AIO apps tend to be paid; doing this for free takes multiple downloads. Download these three apps: SMS Backup and Restore, Call Logs Backup & Restore, and APN Backup & Restore. Each one backs up its respective data to your microSD card (in /sdcard/*appname*BackupRestore/) for easy restoration on another phone. Using these apps is self-explanatory, since there are only three buttons: Backup, Restore and Delete.

Astro File Manager fills a remaining gap: app backup. It’s a free file browser at heart, so the backup option is kind of hidden – once in the app, press the menu button, then click “Tools”. Select “Application Manager/Backup”, and you’ll be able to backup your apps to your SD card. To restore, just install this same app on the device, insert the old SD card, navigate to the same “Application Manager/Backup screen” again, and select the “Backed Up Apps” tab. Astro is also a solid file browser, you can can manually move your data – like photos and videos – to a microSD card, where you should probably be storing them anyway. [Pic via]

There! Sprite Mechanic does the same in a slightly simpler way, but I’m hearing reports that it’s a bit buggy on certain handsets. Still, it’s free, so it may be worth a try.

Lastly, if you’ve got a rooted phone, Backup for Root Users backs up virtually everything, and it’s totally free. That catch? You need to have a rooted phone, or else it won’t work. Which is a crying shame.

Palm Pre/Pixi

Where Android’s cloud-based not-really-a-backup system has gaping holes, the Pre’s is actually pretty good: Backup is performed automatically, every day, and linked to your user account. This covers the absolute basics, though. For example, a list of apps is kept server-side, but the app data itself isn’t back up; browser bookmarks are remembered, but no form data or website passwords. Media isn’t backed up at all. Here’s the full list. The solution is a bit hackish, but it works fine for most data. From PreCentral, a brief guide on backing up using either Microsoft’s Sync Toy for PC, or with slight, obvious modifications, ChronoSync for Mac:

1. Plug in the Pre and select USB Drive.
2. Download SyncToy and install.
3. Click SyncToy on your desktop to run SyncToy for the first time.
4. Click Create New Folder Pair. For the Left Folder, Browse to the Pre’s Drive (maybe E: or F:)
5. For the right folder browse to your documents folder and create a new subdirectory such as PreBackup and select it.
6. Choose to Synchronize and name your folder pair something easy to remember like PreBackup.
7. Click Run.

What you’re doing here is essentially backing up the Pre’s internal storage, bit for bit. Unfortunately, this doesn’t back up settings and some application data, so restoring from this image won’t ensure that you don’t lose some data; just media, ringtones, etc.

Between this, Palm’s backup and the natural backup inherent in being tied to online services like Gmail and Flickr, the only thing not really backed up properly is specific application data and SMS conversations.

Windows Mobile

Microsoft has always offered some kind of backup out of the box, and as of the release of version 6.5, there are multiple options. The core backup utility, of course, is Windows Mobile Device centre, or as it’s known in XP, ActiveSync. Pairing your device with these apps is quite simple, and takes care of most of the data you could want to back up, including contacts, calendar appointments and media.

In XP, download and install ActiveSync, and when you plug in your phone, start the ActiveSync app, which you should be prompted to open anyway. Set up a pairing relationship, select the data you want to backup, and you’re good to go.

In Vista, you’ll need to download Windows Mobile Device Center and do the same; in Windows 7, you should be prompted to install Windows Mobile Device centre as soon as you plug in a WinMo handset.

Now, let’s assume you’re not using a Windows PC, or you don’t want to bother with setting up a sync relationship with a computer. You’ve got two free options, which together back up even more data than ActiveSync, without and external machine.

My Phone, another Microsoft app, is available for free to any Windows Mobile 6.0, 6.1 or 6.5 user. It’s a misleadingly basic-seeming little app, which backs up nearly everything you store on your phone: [By default]: contacts, calendar appointments, tasks, photos, videos, text messages, songs, browser favourites and documents between your phone and your My Phone web account. Restoring from My Phone is just a matter of logging into your Live account from within the app. You get 200MB of free storage, after which you’ve got to pay. Still: pretty fantastic.

If you want to back up your phone’s data without a PC or a cloud-based service, there’s PIM Backup. This utility feels and looks kind of ancient, but it’s great at what it does. And what does it do? Everything:

– backup/restore appointments
- backup/restore call logs
- backup/restore contacts
- backup/restore messages (SMS, Mails, …) NEW !!!
- backup/restore speed dials
- backup/restore tasks
- backup/restore custom files

Best of all, it stores your backup in a single file, which can be restored on any device using the same app. The procedure is dead-easy: Download the PIM CAB file to your device, install it, open it, check the data you want to back up off the list, and go. To restore, you go through the exact same interface, selecting “Restore” from the app’s pulldown menu instead of “Back Up”. In the spirit of safety, you’re going to want to back up PIM’s backup files. PIM lets you designate where you’d like to store its backups; select your microSD card if you have one. If not, you may want to transfer your backup to a PC or external storage device. (Unfortunately, the easiest way to do this is probably with ActiveSync or Mobile Device Center, since most WinMo phones don’t allow you to browse the root storage in Explorer.)

Still though aside from the iPhone, Windows Mobile offers the most complete backup solutions.

Symbian

Depending on which brand handset and Symbian shell you’re using, your backup options are going to differ. The Ovi Suite will do the trick. It’s a full, automated backup suite, but it’s PC-only and works exclusively with Nokia phones. Using it is as easy as setting up a sync relationship – just install the suite and plug the Nokia phone in via USB, and follow the wizard prompts – and it’ll keep contacts, calendar items and media backed up. [Pic via]

Non-Nokia Symbian users – Samsung folks, listen up – can use a free app called The Symbian Tool. This will actually pull a full image copy from your Symbian phone, meaning that you can restore your phone bit-for-bit to the state it was in at the time of backup. There are also less severe options for media backup. More details here.

If you have more tips and tools to share, please drop some links in the comments – your feedback is hugely important to our How To guides. And if you have any topics you’d like to see covered here, please let me know. Happy backups, folks!

Voices: There are a few voice modulation apps on the shelves of the App Store, but none has captured Jesus’ heart like Voices: Retro tape recorder and microphone, cute icons, simple touch interface, and sharing via Twitter, Facebook and email, so you can spook everyone with that infernal Reverse Voice effect. For just $1.19, it’s impossible to resist.

Zosh: Signing things over email: a thing that is dumb. Zosh: a thing that makes that process much easier.

Zosh is a $4 app that allows you to sign attached documents on your iPhone. Basically, you forward the emailed document to Zosh from the iPhone’s mail app, then you open the Zosh app to sign it (plus you can add a date and stuff).

I especially like this one because it’s not just a good way to sign documents on the iPhone, it’s a good way to sign documents in general. I mean seriously, who wants to scan their signature or jitter one out in MS paint? One catch: it only supports PDFs for now, so convert or die.

CatPaint: Negative space, as defined in the eminent McFairlyshire Encyclopaedia of Artistic Principles (1904): An area, perimeter or measurable expanse that lacks cats. And one of the first thing they teach to you at any good art school is to fill it up, with cats. Facts! Enter CatPaint:

Cats can be added to pre-existing photos or cat-scarce shots from the iPhone’s camera, and either saved to your camera roll or sent via email. Using it takes a while to get used to: Once you’ve selected a cat from the app’s animal palette and set the slider for size, each tap on the photo instantly splashes a new cat at the point of contact, which can’t be edited, save for a temperamental shake-to-delete function.

It is the best thing, this app. $1.19.

Knocking: Live Pic Sharing: Uses server-side galleries to let you view photos in sync with other people, which you can send or flip through by “knocking”. Ideal scenario: You’re talking to your friend over the phone, you want to show him a gallery of pictures, you tell him to jump onto Knocking, and suddenly you’re in control of his viewing experience. It pretty much works like that. Free.

Blower: Real Air: Can you guess what this one does? Really, no? Then you’re probably a good candidate for spending money on it. For what it’s worth — something? — Blower explores the iPhone’s absurd novelty potential in a completely new way. From the reviews, a perfect description: “It feels like an ant blowing on you.”

Call of Duty: The control scheme isn’t perfect, and the price ($13) is high, but it’s tough to argue with a Nazi Zombie shoot ‘em up with the Call of Duty name. Pro tip: Switch to the tilt controls, because the overlaid joystick is not good. (They never are!)

Fit or Fugly: Rounding out our cr-appier selections for the week, an app that purports to measure your beauty according to some kind of mathematical equation. It’s not a good way to actually tell if someone is attractive, nor is it a particularly well-executed app. It is, however, a good excuse to tell your friends that their faces are asymmetrical, which evokes surprisingly intense responses. Try it! (The face thing, not necessarily the app.)

Google Earth 2.0: You can create and store your own customised maps in the desktop version of Google Maps and save them to your account — this is great for keeping running routes, sharing driving directions and the like. You can view them in the new version of Google Earth for the iPhone now, which is useful and also sort of hilarious since you can’t even access them in the official Google Maps app. Sound silly? Welcome to the iPhone, y’all!

This list is in no way definitive. If you’ve spotted a great app that hit the store this week, give us your first-hand impressions in the comments. And for even more apps: see our previous weekly roundups here, and check out our Favourite iPhone Apps Directory. Have a great weekend, everybody!

Finance director for the company, Alexandre de Rochefort, says that even a company that’s done extremely well on the iPhone can have trouble breaking even on Google phones:

We have significantly cut our investment in Android platform, just like … many others … [The Android Market] is not as neatly done as on the iPhone. Google has not been very good to entice customers to actually buy products. On Android nobody is making significant revenue.

That’s the essence of the App Effect: High volume, customer pressure and nudging from Apple drive iPhone app prices down break-even levels, which gives app developers two options. They can either charge higher prices for equivalent apps on Android, for which they will be crucified by customers, or they can match their prices and hope that enough of Android’s comparatively small, fragmented user base just happens to stumble across said app in the barely navigable App Market. An attractive business proposition, I say!

So what needs to happen? Either Android adoption grows (which it’s doing), the App Market gets much easier to navigate (a desktop app, maybe?), or you know, both. [Reuters]

The news comes from the COO of Syabas, the company that makes the Popcorn Hour set-top box. Up until now they’d had a loose agreement with the ‘Tube: They can stream video from YouTube for free, but YouTube can change the terms of the deal whenever they want. Which they did!:

YouTube has always retained the right to change its terms of service in the future should it ever wish to do so. As a result of Google’s decision, Syabas is no longer allowed to access YouTube through its APIs. To be clear, Syabas is not being singled out. With the exception of a few strategic partners Google has chosen to work with, the company has informed Syabas they are asking all over-the-top device makers that are currently connecting to YouTube content through its APIs to take down the service.

To quote every set-top box manufacturer in the world, probably: “Shit.” YouTube access had become the kind of thing you take for granted in a connected box or Blu-ray player, and it was nice to have. Now, it’ll be limited to devices like the PS3, Wii and TiVo — backed by the kinds of players who have the clout to pressure Google, or the money to pay them — leaving everyone else to search for some kind of hacky workaround.

I understand that Google wants to squeeze some ad revenue out of YouTube, and that letting anyone and everyone access raw, ad-free content through the back end probably isn’t the best business plan, but this isn’t Hulu — it’s not like they have many powerful content providers to appease, just a bunch of teenagers with webcams. Set-top box folks: Watch your free video cornucopia dissolve on December 2.

UPDATE: YouTube’s statement:

Since July of 2008, YouTube’s Terms of Service has restricted implementations for televisions based on our APIs. YouTube has been in active discussions with various developers on how best to implement YouTube on set top boxes and TVs. There are several companies, however, that have deployed solutions, like video scraping technology, to circumvent the rules and violate YouTube’s Terms of Service. Companies that have negotiated agreements to use our APIs, like TiVo, Sony, Panasonic and Sony’s PS3 are not impacted.

So, companies like Syabas have been in violation of YouTube’s terms of service for some time now and knew this was going to happen. The question remains, though: Why couldn’t they just comply and get a deal like TiVo or Sony? Does it cost anything? Is YouTube selective? Does it just take awhile? [Syabas via Engadget via Lifehacker]

Is it just what they’re showing us? A Flo TV app, that requires some kind of accessory to tune into broadcasts? That’s possible, but given how well the iPhone can stream video over 3G, it’d be a hard sell, even with Flo TV’s cable-like channel selection. It would also help if said accessory wasn’t larger than the actual iPhone.

Or is it to foster excitement over the idea of native Flo TV hardware support in the iPhone, like in the HTC Imagio? Because that will never, ever happen. So again, why? [Electric Pig]

Granted, it’s a little worrisome that Barnes & Noble is taking pre-orders before letting reviewers have their say, so maybe this enforced waiting period is a good thing. At any rate, it’ll be January — well after we’ll have run B&N’s Android-powered ereader through its paces — before anyone else will be able to get one. [B&N via Bits]

According to Fudzilla, the platform will include a new memory controller to accommodate DDR3 RAM which, despite supporting two slots, will remain single-channel. Pineview, the next Atom before Cedarview, hasn’t even shipped yet — that’s expected to be the beginning of next year — so it’s interesting to glimpse this far into the future, where Atom, such as it is, will remain positioned almost exactly where it is now. Oh well! [Fudzilla]

Disclaimer: That Atom sitting on the penny up there is an older version (not that the new one will look any different).

Veronica Belmont, of Tekzilla/Mahalo/BOL fame/general video on the internet fame, sees Apple finally going ahead with that Courier concept Microsoft keeps dragging their feet on. Or Apple subsumes Microsoft entirely. What do you know, Belmont?

BoingBoing’s/MAKE’s Mark Frauenfelder goes as DIY-y as is humanly possible and projects a future in which Apple is just a bunch of dudes with Arduinos and a pair of pliers. You see, we’ll just buy Apple’s designs, and your iMake object printer will print them out.

Brian Lam, Man With Hat, just wants his iPhone to get reception in San Francisco, for once. Hence, bunny hears.

There are a couple more, and they’re all in the same whimsical, not-quite-serious vein. Check them out at: [Maclife]

Just to be clear, I’m not talking about Chrome OS 1.0. You can build that now and (maybe) install it on your netbook, and you should be able to buy it on hardware next year. All that stuff — to borrow a word that Google loves to misuse — is a beta. A test. A trial. A first step toward a larger vision, which Google has been hinting at since they branched out from search: In the future, we will live on the internet. We’ll be able to do all the things we do on computers now, and probably more, while connected to the cloud. And it’ll be great.

Chrome OS is an explicit step towards making this happen, but the version we saw today is just an early, broad step. Google even said so! Despite early talk about how Chrome OS could be a full replacement OS one day, suitable for regular ol’ laptops and desktops, today’s pre-announcement of a version strictly for netbooks included an admission that it would only be intended as a secondary OS. So, what does Google need to see this thing through and make Chrome as capable as the OSes we’re used to using now? Lots:

The Internet Needs to Get Way, Way Faster

And I’m not just talking about higher bandwidth. Broadband connections are pretty quick nowadays, but compared to reading — and especially writing — data to a hard drive, sending bits over the internet is excruciatingly slow. And Chrome OS isn’t even really a true web OS: it’ll slurp the guts of larger web applications like Gmail and Gcal and effectively make them local, meaning that the kinds of tasks that require low latency and fast load times will run tolerably.

That kind of local storage, along with JavaScript technologies like AJAX, is a salve. We need them because communicating with a server for every event in an application would take forever, and make using them miserable. Remember how webmail used to be, before it got all AJAXy? Awful. And it still would be, if not for recent JavaScript advances and local storage.

There’s nothing fundamentally wrong with making web apps local, and Chrome OS will keep doing that forever: it’s the only way Chrome OS can work offline. But that doesn’t cover everything. What about high-bandwidth tasks like photo and video editing? To do it the way they suggest would require constant syncing between local memory and a remote server. These are basic tasks for a computer. Basic tasks that’ll be impossible on Chrome until super low latency, 100mbps+ broadband is not only commonplace, but also wireless and effectively ubiquitous. That’s quite a few years away, even by generous estimates.

Web Apps Will Need To Get Much Better

I’m sure Gmail, Google Reader and Google Calendar will be totally swell in Chrome OS. They’re some of the most feature-complete web apps in the world, and they’re good enough to replace desktop apps for most people. But what about VoIP apps? Torrent clients? Media players? Image editors? Video editors? There are web apps for almost all of these things, but collectively, they amount to a big bag of dick. Trimming videos with YouTube’s tools is nothing like editing them in Final Cut or even iMovie. Cropping a few images in an online photo editor and playing with their contrast is fine, but what about my bloated Sony RAW files? There are still some massive gaps in the web app world, hence Google’s repeated, vague pleas for developers to do better, alright?

Web Standards Will Have To Evolve, Fast

Google wants to replace regular apps with web apps by making web apps more like native apps, in concept and execution. Eventually, the hope is that they could use the new features of HTML5, like local storage, drag and drop, canvas drawing, native animation and location awareness, to have all the powers of a native app. Thing is, HTML5 is just a stepping stone; it’ll take more than a few new HTML tags to pave the way for honestly native-seeming applications.

Google’s obviously got a lot of leverage over standards bodies like the WHATWG and W3C, so they could help move new HTML capabilities along in theory. But even HTML5 is brand new, and very few people are using that. It’ll be at least another generation before developers will be able to code native-equivalent apps in web languages, and that’s assuming that standards development keeps heading in that direction. Which it might not.

Someone’s Going to Have To Solve the UI Problem

Talking about Chrome OS’s interface almost seems like a waste of breath, since your real UI is the internet, which is the very definition of inconsistent. Part of the reason email apps, Twitter apps, IM clients and the like are still so popular is because they offer services that people want in an interface that’s consistent with the rest of their system. Web apps offer no such thing.

Sure, if all you use are Google products, you’re fine: Your life is blue, white, boxy and clean. But what about when you want to jump over to Meebo? Or Aviary? This kind of inconsistency wouldn’t be acceptable in another OS, so it would feel like a compromise here. I suppose you could use tools like Greasemonkey to reformat pages on the client side, but this is hacky and, well, lots of work. We’d need some kind of framework for skins, or something, to make the experience more uniform.

People Will Have To Give Up On Owning Media, an Get Comfortable With Subscription Services

People need their music and videos, and now, most people have collections. That’s sooooooo 2009, am I right? For Chrome OS to work, people are going to have warm up to subscription services and streaming media.

Before you get mad at me, forget about online music stores, and think more about your pay TV company, your ISP or your beloved DVD rental service. These kinds of arrangements are going to have to be extended to all media. Which is possible, but also fraught, since you really won’t own your media.

The Rest of the (Browser) World Has To Be Onboard

During the announcement, Google made the point that the Chrome browser in Chrome OS won’t have any special talents that Chrome elsewhere won’t, and that at present it’s no more able — in terms of what kinds of web apps it can run — than, say, Firefox. Nobody’s going to want to write web apps just for Chrome (that would make them Chrome apps, right?), so it’s vital that other browsers support the same new HTML standards that Chrome need to succeed. Google can go all out supporting the latest, greatest web standards, but unless everyone else does too, nobody — not even Google — is going to write for them.

None of these things are impossible; in fact, most of them sort of feel inevitable, given that they’re all just extrapolations of obvious trends from the last few years. They’re just optimistic, and sit well into the future. Chrome OS can carry out Google’s LET’S ALL LIVE ON THE INTERNET vision when the conditions are right, eventually. But these are long-term bets, measured in years.

That might make sense to a room full of Google engineers. To the rest of us, though? It’s abstract. It’s strange. It seems gimped. It’s largely irrelevant, and it’s not all that exciting. Yet.

Google went to great pains to emphasise that today’s event wasn’t a launch — that’ll come a year from now, apparently, with a public beta still well over the horizon. This is all about seeing the OS for the first time; understanding in real terms how it’s different from what’s out there; figuring out why you might actually want to use it. So! Here’s what we knew going in:

Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks” and “most of the user experience takes place on the web.” That is, it’s “Google Chrome running within a new windowing system on top of a Linux kernel” with the web as the platform. It runs on x86 processors (like your standard Core 2 Duo) and ARM processors (like inside every mobile smartphone). Underneath lies security architecture that’s completely redesigned to be virus-resistant and easy to update.

Like I said, there were plenty of questions. Onwards:

What It Is

• It’s basically just a browser: meaning that it’ll be based around pre-existing web services like Gmail, Google Docs and so on. There are going to be no conventional applications, just web applications — nothing gets installed, updated or whatever. Seriously.

• It only runs web apps: It’s going to integrate web apps into the operating system deeper than we’ve ever seen before, meaning that a) they’ll seem more like native apps than web apps and b) they’ll be able to tap into local resources more than a typical web app in Firefox, for example. They’re web apps in name, but they’ll have native powers.

• How, exactly?: With HTML 5. This is the next version of HTML, which gives the browser more access to local resources like location info, offline storage — the kinds of things you’d normally associate with native apps.

• Chrome is Chrome: The user’s experience with Chrome OS will basically be synonymous with their experience on Chrome Browser. Technically speaking, Chrome OS is a Linux-based OS, but you won’t be installing Linux binaries like you might on Ubuntu or some other Linux distribution. Any “apps” you have will be used within the browser. Chrome OS is effectively a new version of Chrome, that you can’t leave. There are a few reasons Google’s pushing this, which we’ll get to in a bit.

• And as you’ve probably guessed, it’s super-light. It starts up in a matter of seconds and boots straight into the browser. Likewise, the Chrome browser is apparently very, very optimised for Chrome OS, so it should be faster than we’ve ever seen it.

• It won’t support hard drives, just solid state storage. I mean, hard drives are dying, sure, but this is pretty bold. Hardware support sounds like it’ll be pretty slim, because:

• You’ll have to buy a Chrome OS device: You might be able to hack this thing onto your current machine, but you won’t just be able to install it to replace Windows, or opt for it on your next laptop, for example. You’ll have to buy hardware that Google approved, either component by component, or in a whole package. They’re already working on reference designs.

• For now, it’s for netbooks. It’s not intended for desktops, to the point that Google is saying that the first generation of Chrome hardware will be secondary machines.

How It Looks

• It looks like the Chrome browser — specifically, like the leaked shots we saw before. As in a browser, you have tabs — these have to serve as a taskbar as well. To the left of the tabs, you have a sort of start menu, which opens up a panel full of shortcuts. These are your favourites. These are your apps. (Get used to this weird feeling, btw)

• You can peg smaller windows, like chat windows or music players, to sit above your tabs at all times. This feature looks a lot like the GChat feature in Gmail, which is to say, a box in the corner.

• Along with tabs, it’s got its own version of virtual desktops. This means you can have multiple “windows” of Chrome OS to switch between, each of which is a different set of tabs. Think one desktop for work, one for play, one for porn, etc. It’s a bit like using Spaces on Mac, except only with the browser.

When and How It’s Coming

Google’s staying specifics on the exact release date — it’ll be sometime next year — but the source for the project is published now. That doesn’t mean it’s ready, really, but rather that they’re just planning on developing it in the open from here on out. Expect builds to start showing up online, which’ll probably work wonderfully in a virtual machine app like VirtualBox.

The code is available as part of the Chromium OS (the Chromium/Chrome distinction should be familiar to anyone who’s wrestled with the open source Mac version of Chrome) project, posted here.

Why It Matters

With Chrome OS, Google is taking (or in a way, forcing) the operating system to go totally online. As Google’s freshly designated evangelists are eager to tell you, the browser is already the centre of most people’s computing experience. The idea here is to make the browser powerful enough to render the rest of the operating system, and its native apps, moot.

It’s more pure than a lot of people expected: When Google said that Chrome OS would be centred around the web, I think most people just assumed it to be a lightweight Linux distribution with deep integration for Google web services. It’s not that. It’s a browser.

But it’s a browser that runs different processes for each tab, that will have access to local OS resources, and will to some extent work offline. In other words, it’s not really a browser in the sense that we use the word, and the web apps that we’ll be using won’t be like the ones we’re used to now, either. The idea here, it seems, is to replicate most, if not all, of the functionality in a native OS, while keeping the lightweight, ultra-secure framework of a thin client. In other words, Google’s not asking much of its users in terms of changing how they do stuff; they’re trying to change the way the operating system lets you do those things, transparently.

Think of it this way: Now, the buttons in your taskbar or dock are tabs; your email client runs within your browser, but stores stuff offline just like Mail or Outlook; your documents will still open with a few clicks, but they’ll be stored remotely (and locally only if you choose). It’s all the same stuff, given to you in a different way. [Chrome on Giz]