Is Chrome OS the future of home computing?
Google announced its Chrome OS last week, and it’s focused on the cloud. You basically get a browser and web-based applications to replace all the stuff you love. In fact, the OS is so cloud-focused it even resets itself on errors by downloading itself.
Let’s discount the availability of Internet everywhere. Look beyond the fact Google Gears is still flaky and doesn’t work seamlessly with Google’s own products, GMail and Google Calendar. These things can and will get better.
Google’s strategy is to sync everything to the cloud and assume its accessibility everywhere: your laptop at home, your desktop at work, your Android phone, and now, your netbook (or other coming device). The cloud is actually Google’s servers, though, which works out nicely for them.
Compare this to Apple’s 2001 vision of the home Macintosh being a hub for your digital lifestyle. You go home, you use your computer. You plug in your iPod. You plug in your iPhone. You plug in your iTablet. Your home machine has everything, and the peripheral devices work to parcel out the information in the context you need them.
Microsoft is on this side as well, but they’re following a weird disjointed path that focuses on the cool new thing every year: Microsoft Home Server to sync your multiple PCs at home, Windows 7 to catch Mac OS X, Windows Mobile 7 to catch iPhone OS. In an attempt to keep their fingers in every pie, Microsoft acts as if everything needs to work together instead of a subset.
You don’t need everything synced to a cloud: music, email, and calendar are good enough for most people.
Apple has figured this out – that’s why they called it a digital media hub.
Microsoft is close – instead of competing with Apple on a product-by-product basis they should do three things:
- allow XBox360 to store your music and videos locally
- allow synching for Windows Mobile 7 and Zune HD to an XBox360
- bring calendar and email to XBox Dashboard through Windows Live
Google and its Chrome OS, meanwhile, are a different path. I can see why technophiles geek out to this (”I can get my spreadsheet anywhere!”), but I can do that using Dropbox anyway, and I get a nicer UI.
Software doesn’t always win the day, especially when you’re dealing with normal humans who don’t know (or care) what a cloud is.
How Apple’s Approval Process Actually Helps Users
Paul Graham wrote an article on how Apple alienates its iPhone developers. He has a good discussion about developers iterating and needing to get a new product in the hands of their users. In fact, he mentions a developer who says the approved app feels crappy next to the daily builds and betas he hands out.
It’s time for these folks to try my G1. Not because it’s better but because Android will annoy the crap out of you. Every day, I get a notification telling me “N number of apps updated.” And every day, I roll my eyes and clear the notification. Users don’t want to go through this process; it’s annoying when it happens on a desktop every few weeks, so it’s even worse on a daily basis on a phone trying to download over a 3G EDGE connection.
Deciding what constitutes a critical bug is difficult – if you’re a lone developer you think everything is important. Should Apple trust you to self-regulate and update only on critical fixes or major new releases?
Apple has an iron fist when it comes to the iPhone and its ecosystem because its advantage is a tightly knit experience. Getting a daily notification while you sync asking you to update or an in-app pop-up with details lessens the polish.
Ultimately, I think this App Store stuff is a way of throttling developers to ensure the experience is not too painful. More updates make users think, and you want to minimize that.
Subscribe via RSS
Connect on Facebook
Connect on LinkedIn
Follow on Twitter