For those who have installed the new Chrome app on your iDevices, you now have access to one of the features I really loved when I had an Android phone: Chrome to Mobile. Of course, before Google made Chrome available to users in the iOS universe, the feature was called Chrome to Phone, as was the extension that needed to be installed in your desktop Chrome browser.
If you’ve been clicking the Chrome to Phone button and wondering why your Web pages aren’t popping up on your iPhone or iPad, I’ll save you a little bit of trouble: uninstall the Chrome to Phone extension.
Google decided to (wisely) change the way the extension works and, in the process, also renamed it; a nod to the fact that it also works with devices that aren’t phones. It seems they didn’t really make a point to tell anyone, though. So you’ll have to download the new extension.
After you install the new extension and sync it up with your Google account, you’re pretty much set. If you haven’t already, you’ll need to sign into mobile Chrome using your Google account, and the Chrome to Mobile feature will be enabled automatically. Now, when you visit a site on your desktop and you want to send it to your iPhone or iPad, you can click the tiny mobile phone icon on the right side of Chrome’s address/search box. You’ll be asked which device you’d like to send the page to, and then it’ll be zapped over instantly. See my demo video below for an example.
After testing the iPad in various situations, I decided to sell my MacBook today. Now, before you chastise me for going off the deep end, bear in mind that I also have a desktop computer. That can handle “work” without issue. For everything else, I’m discovering that the iPad holds its own quite well. In fact, I typed this post on it – and I managed to do it without compulsively checking Twitter twenty times. I guess that is one situation where a lack of multitasking comes in handy, eh?
Just in case you’re afraid of missing something on the Twitter, there is a nice iPhone app called Boxcar that also works with the iPad. It’ll send you a push notification if you receive an @reply or DM.
…it had Google Reader. Why not just a feed reader? I’ll explain.
If I had to estimate, I’d say that about two-thirds of the reading I do takes place inside Google Reader. And not just my own subscriptions, but also the content shared by others. I get a lot of value from those shared posts because, let’s face it – I don’t have time to sift through thousands of blog posts a day. This is why a plain feed reader just wouldn’t do. Sure, I’d be able to subscribe to and read blogs, but I’d be missing all the shared content and the sense of community I get inside Google Reader.
The Kindle isn’t built for that, at least not yet. Is it great with books? Absolutely. But the blog reading situation needs to be vastly improved for me to even consider buying one and, unless that happens before April 3, I’ll be purchasing a different product instead.