Google Sync and the iPad

If you’re like me, you spent way too much time trying to figure out why only your primary Google Calendar would get pushed to your fancy new iPad. It seems to be a bug with Google Sync, but one crafty user discovered a work-around:

On your desktop Mac enable the safari debug menu, set the user agent to iPhone, go to m.google.com/sync

While in preferences, turn off Javascript – this is what is preventing us from selecting multiple calendars!

make sure you’re signed in to your google account, and then visit: http://m.google.com/sync

Works like a charm.

Google to Serve Custom iPad Webpages

Google’s Punit Soni:

While surfing the web on your iPad, we expect many of you will want to check your Gmail. If you go to gmail.com in your browser, you’ll see something different than what you’re used to on the desktop. We’re releasing an experimental user interface for the iPad built on the Gmail for mobile HTML5 web app that we launched last year for the iPhone and Android devices. Those devices have large screens compared to other phones, and tablets like the iPad give us even more room to innovate. To take advantage of the iPad’s large display, we’ve created a two-pane view with your list of conversations on the left and messages to the right.

It looks real, real good.

Google Re-directs Chinese Traffic

Google:

So earlier today we stopped censoring our search services—Google Search, Google News, and Google Images—on Google.cn. Users visiting Google.cn are now being redirected to Google.com.hk, where we are offering uncensored search in simplified Chinese, specifically designed for users in mainland China and delivered via our servers in Hong Kong. Users in Hong Kong will continue to receive their existing uncensored, traditional Chinese service, also from Google.com.hk. Due to the increased load on our Hong Kong servers and the complicated nature of these changes, users may see some slowdown in service or find some products temporarily inaccessible as we switch everything over.

Good for them.

Why I Switched to Android

Background

I am no stranger to the iPhone. I was working as a Mac Genius In-Training when the original iPhone was released. I got my first iPhone 6 weeks after they were released. A year later, I upgraded to the 3G when it was released, and then again to the 3GS last summer. I’ve spent more money than I care to think about in third-party apps. So why did I give it up? Well…

Growing Tired

After owning the 3GS for several months, I started to grow tired of the whole experience. The 3GS is no doubt the best iteration of Apple’s hardware, but it looks and feels like the models before it.

More importantly, the iPhone OS seems … stagnant. OS 3 and OS 1 have more in common than they differ from each other. Even with the addition of push notifications and third-party apps, the iPhone OS hasn’t evolved that much.

On a slightly different front, I was also tired of the endless Update/Jailbreak cycle that I — like many others — had fallen into. Keeping my iPhone the way I wanted to was becoming a hassle.

After almost 3 years, I was ready for a change.

Why the Droid?

When I purchased it in January, the Motorola Droid was the top dog when it came to Android devices. The Nexus One had been announced, but just for T-Mobile, which I wasn’t thrilled about. Don’t get me wrong, the Nexus One is a slick phone, but until it shows up on Verizon, the Droid is their best handset.

My dad has the HTC Hero on Cellular South, and after spending some time with it, I wasn’t a big fan of HTC’s Sense UI. On an older device like the Hero, it seems to slow down over time, and it holds up updates from being pushed out to customers. I’m pretty set against owning a skinned Android device.

When Motorola and Verizon started marketing the Droid, they aimed squarely at geeks. It worked. This phone isn’t pretty, light or sexy. It’s rough, dark and chunky. It’s the phone that Batman would use, without a doubt. I like the hardware keyboard and the design. The Nexus One may be hot, but the Droid looks like it could beat up any other phone on the market.

Why not WebOS?

When I bought my phone, WebOS devices were only on Sprint. I looked at the Palm Pre and I liked what I saw software-wise. While they aren’t a ton of apps out there for WebOS, the core apps I needed were. Palm has a killer mobile OS. The way it multitasks and integrates multiple cloud services is very slick, and it looks downright beautiful.

Sadly, their hardware is lackluster. The Pre is far better than the Pixi, but it still feels cheap and rather breakable.

Now that the Pre Plus is on Verizon, it is a harder choice, but I the Droid still wins in my book. Now, if Palm ever releases a device that is closer to an iPhone, hardware-wise, it would be hard for me to ignore it.

AT&T vs. Verizon

I know that comparing one cellular network to another is a tricky thing to do. And while the general censuses is that Verizon’s network is better and more robust that AT&T’s, I have to agree. While Verizon’s 3G doesn’t seem as fast as AT&T’s (of course, that might be due to differences between the iPhone 3GS and the Droid), I get better coverage with Verizon in the places I visit in the course of a normal day.

As AT&T has highlighted in their ads, Verizon’s network is like AT&T’s older EDGE network, in that browsing isn’t possible while on the phone. I had gotten used to being on the phone and looking information up online with my iPhone 3G and 3GS, and I miss it on the Droid.

Verizon’s plans are usually a little bit more expensive than AT&T’s, but I love the flexibility they offer. I can go online and add or remove features from my plan, without adding time to my contract.

The Good, the Bad & the Ugly

The flexibility of Android is amazing. It’s really what drew me to the platform more than anything. Don’t like the software keyboard? You can replace it. Don’t like the home screen? Use another program to arrange your icons. Every nook and cranny of the OS can be tinkered with.

Of course, when people compare the iPhone to Android, two things are always mentioned: the openness of Android, and the ability to run apps in the background.

Indeed, the ability to run 3rd party apps is great, but comes with a price. I’ve found it’s pretty easy to blow up my Droid while playing with system-level applications.

It’s the same story when it comes to running applications in the background. It’s nice when I want it, but things can get out of hand. But the ability to run PDANet, listen to music and check email at the same time is pretty slick.

But that’s the beauty of Android: the developers leave it up the end user. If I want to burn through my battery in three hours by having 14 apps running at once, I can. It’s up to me — and that’s very appealing.

I do suffer iPhone withdraws from time to time. Android is rough. It does some things in weird, awkward ways. For example, copy and paste simply sucks on the Droid. Text-correcting is painful without sliding open the keyboard and using the D-Pad. The apps aren’t as polished, and there aren’t as many apps. And don’t even get my started on the awful, awful camera on this thing. It’s useless.

Fragmentation is a huge problem with Android. Right now, the Droid is the #2 phone in the Android universe, so I don’t run into issues. But as my phone ages, I expect to be left out of more and more features. Hopefully the rumor that all phones will get upgraded to 2.1 will ease these concerns. The update has been due “soon” for the Droid for months now.

In Closing

Despite the issues, I love my Droid. I like that I don’t carry the same phone 90% of people my age carry. I like exploring the Internet for third-party apps I can install without jailbreaking my phone. I like that PDANet is available on the App Market — no shady business required. The notification system is quietly brilliant. All-in-all, Android is a very capable platform with a bright future. While time will tell what I do when my current contract ends, for now, I’m really happy with the Droid.

Google Testing Android Hardware

Google Mobile Blog:

We recently came up with the concept of a mobile lab, which is a device that combines innovative hardware from a partner with software that runs on Android to experiment with new mobile features and capabilities, and we shared this device with Google employees across the globe. This means they get to test out a new technology and help improve it.

‘Just Good Enough’

Wayne Lau for Ars Technica:

Overall, I like the Droid. The hardware design is merely par for the course; it’s well-made but has some rough edges. The hardware specs, however, combined with Android 2.0, makes this a good enough device to be a solid competitor to the iPhone 3GS. This is the hardware that Android should have shipped with. In some areas it is better, in some areas on par, and some areas slightly worse than the iPhone or other high end smartphones. But all of it is “just good enough.” It all depends on your preferences in phone features. If multitasking matters, the Pre and the Droid are your only choices. Droid lets you play music on Pandora, navigate, and check Twitter all at the same time, with no lag and no delays. If you’re looking for a media player phone or a camera phone, on the other hand, you might check elsewhere. It just comes down to the feature set you’re looking for.

I think the second revision of the Droid will improve on the hardware complaints, and by then Android will be beyond version 2.0. While the Droid is good, it’s just the beginning.

Things Apple Can Learn From Android: Notifications That Don’t Suck

The Need for Notifications

Back in the day, cell phones did one thing — make calls. Since they were so simple, the only time they needed to alert their owners was with a ringtone.

Obviously, phones do a few more things these days. They can send and receive emails, SMS and MMS messages, surf the Internet, give turn-by-turn directions and much, much more. One of the core problems with smart phones is how to handle all of this incoming information and present it to the user in bite-sized chunks.

The iPhone handles notifications in one of three ways: Sounds, Alerts/Pop-ups and Home Screen Badges. Each of these is flawed.

The Problem with Audible Alerts

I think the shortfalls of using sounds for alerts are pretty obvious. First, they aren’t persistent — they are a one-time event that if is missed is missed forever. If I leave my iPhone in my car and it sounds an alert, then when I remember to go get it two hours later, I have no idea it went off. Not to mention an audible alert can be missed by something as simple as too much background noise. When it comes to getting the user’s attention, this isn’t the way to go.

The Problem With Alerts

Alerts are used by Apple for SMS and MMS messages, and by many third party applications. Alerts are much more flexible than other alerts, as they include content.

Alerts are the easiest way on an iPhone to get the users’ attention. That said, interrupting what the user is doing and forcing the user to address the alert (and leave what app they are in at the time) or ignore is quite annoying. They also suffer the same flaw of persistence that audible alerts do — if the user taps “Ignore” the alert goes away.

The upside is that alerts — when ignored — become Badges.

The Problem with Badges

Badges are also used by Apple — mainly for incoming SMS and MMS messages and emails. Badges are usually used to show how many unread or new items are ready for the user.

Badges are far superior than Sounds of Alerts, but are vague — they don’t give any indication about what they’re notifying the user about. A obvious example of this is Mail. If I get an email, I can’t tell if it’s in my personal Gmail account, my ForkBombr account or my work account. Likewise, if Mint has a badge, I don’t know if we bounced a check or I got paid without opening the app.

The downside of the Badge system is that is tied to the app’s icon. For example, I have Mint on my third page of apps, and unless I scroll over to that page, I don’t see that there’s a notification.

What Android Gets Right

Android groups all of its notifications in the menu bar across the top of the display. The menu bar shows several icons, including separate ones for different email accounts. For more info, the user simply taps the menu bar and drags their finger to the bottom of the screen, revealing additional details.

In many ways, Android’s solution is like the solution Microsoft uses in the Windows task bar — put icons there when needed, but don’t annoy the user about them.

This solves all the issues raised with Apple’s solutions — Android’s notifications are specific, persistent, can be seen from any screen in the UI and don’t interrupt the user.

In Closing

I hope iPhone OS 4.0 adds some additional flexibility when it comes to notifications. Before OS 3.0, only a few of Apple’s built-in apps used them, so the shortfalls weren’t that big of a deal. But now that many third-party apps use push notifications, Apple has to figure out a way to make notifications more powerful and better at informing the user with a simple glance.

‘I Have to Get Rid of It’

Stewart Alsop on the Droid:

The hardware (which is Motorola’s) mostly works. The keyboard is horrible and I’ve never used it, which means that it is a real design flaw given how much weight and mechanical operation it adds to the device. (The software keyboard works well enough that I’ve found it adequate but the other problems with the software make it barely useable.) The camera button on my Droid doesn’t work and never has, so I call up the camera from the home screen. The on-off button is poorly placed for one-handed operation and requires real force to actuate. But this is just version 1.0 issues that Motorola will likely fix next time out.

The software (Google’s Android plus apps both from Google and from other developers) doesn’t work and is unacceptable on a mobile device. First, the operating system doesn’t work well enough to be considered a mobile OS. A mobile phone needs to have an OS that is really tied down and ready to perform at all times, like for receiving phone calls. This one isn’t. The process management in the OS stinks. Press on an app icon; maybe it will come up and maybe the phone will just not respond. Who’s to know why? Try pressing on the phone icon at 70 mph and have it not respond. Then try pressing again. And then get a message something like: “Activity Home (in process android.process.acore) is not responding.” Force Quit or Wait. Oops! I just drove into the guy in front of me when he slowed down and now I’m dead!

Things Apple Can Learn From Android: Better Tie-in with the Cloud

Being built by Google, it’s no surprise that Android integrates with Google’s suite of online services seamlessly. Gmail, Google Contacts and Google Calendar are synced over-the-air to Android handsets with little setup. On the other end, Google’s web apps can be used from any computer, regardless of OS, giving users their data anytime, anywhere.

Apple offers MobileMe as a similar service, but with an emphasis on syncing with rich desktop applications, not web-based services. MobileMe works well, but at $100/year, is pricey for what it does. Like Google Sync, MobileMe pushes customers’ data over the air.

iPhone customers can use Google Sync to have their Gmail, Google Contacts and Google Calendar pushed to their phones just like Android handsets. The problem is Google Sync for the iPhone uses Exchange, meaning corporate types — myself included — can’t use Google Sync and MobileMe at the same time, effectively locking people into MobileMe.

In short, Apple needs to offer customers options. There’s no reason the iPhone can’t have Google Sync built-in. There’s no reason the iPhone should be limited to just “grown-up” contact sources — Android devices can also hook into Facebook for contacts. As more things move to the cloud, iPhone customers want options. Options that the iPhone doesn’t offer in its present state. Cloud computing is the future, and Google’s services kick Apple’s services’ collective cloud asses. MobileMe is mediocre at best, and way too expensive. It simply can’t compete with Google’s offerings. Apple needs to embrace that.

Developers Hesitant About Android Market?

Reuters:

“We have significantly cut our investment in Android platform, just like … many others,” Gameloft finance director Alexandre de Rochefort said at an investor conference.

Rochefort said the company has cut back on investment mostly due to weaknesses of Android’s application store.

“It 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,” Rochefort said.

Of course the iPhone’s App Store makes more money than Android Market. If anyone is surprised by this, they’ve been living under a rock. I think the money is what keeps most developers from leaving the platform over Apple’s stifling policies.