Wednesday Jun 17, 2009

Configuring CalDAV on iPhone 3.0 for Google Calendar

Today, the iPhone 3.0 software update finally came out and about the first thing I did after upgrading mine was to check out the new CalDAV and LDAP functionalities.

This is how I configured CalDAV for Google Calendar:

  1. Go to Settings > Mail, Contacts, Calendars
  2. Tap "Add Account...", then "Other"
  3. Under Calendars, "Add CalDAV Account"
  4. Enter account information:
    • Server:
    • User Name: [your username]
    • Password: [your password]
    • Description: [e.g. Personal]
  5. Tap "Next"

That's it! Now you can launch the Calendar app, tap "Calendars", then select the CalDAV calendar. Events can be created or modified on the iPhone and they'll be reflected on the server instantly.

Secondary calendars: This only shows the main calendar. To get your other calendars, you'll need to repeat the above for each (with distinct Descriptions otherwise it'll be confusing), then edit that CalDAV account, and under "Advanced Settings" change the "Account URL". You can get this Account URL by clicking the down arrow next to your calendar at and selecting "Calendar Settings". You should find your Calendar ID next to the XML, iCal, HTML links in the Calendar Address section. Insert this Calendar ID into an URL like so: . You can email this to yourself, then leverage the new copy&paste feature of 3.0 to avoid typos. Why is this so cumbersome? Here's a possible explanation.

Offline access: Works in both directions. Changes are sync'd upon network reconnection.

CalDAV or Google Sync? Either way will give you read/write access to your Google Calendar. A major deciding factor is whether you already have an active Exchange account (e.g. for work), since iPhone only allows one Exchange account at any time, and Google Sync uses Exchange ActiveSync protocol.

[Updated per suggestions in the comments]

Friday Aug 29, 2008

Managing Google Calendar from iCal

I use Google Calendar (or GCal as it's often called) at home to share upcoming events such as important dates, weekend plans, medical appointments, travel schedules, etc with my family and this is working quite well. After showing my mom how to use it, she has even eclipsed me to become the biggest calendar user in our family. We subscribe to each other's calendars so we can see who's busy or available at any time. We haven't gotten to the point where we invite each other over calendar though, which is good IMHO, because that's a bit too impersonal. :)

Since I want to see both work calendar and family calendar in one place, I opted to subscribe to them via iCalendar format. This gives me a read-only copy of the calendars in iCal; if I need to create or modify an event, I need to use the web interface. Ideally, I want to be able to manage both work and family calendars directly in iCal.

As if Google heard my wish, they added CalDAV support about a month ago. It was very easy to setup, and has worked fine for me except for a full-day outage about two weeks back. Here's what my iCal looked like before with iCalendar subscription (pic to the left), and here's what iCal looks like after with CalDAV enabled:

Before After

Now I can fully manage my family calendar from iCal. I'm one step closer to my ideal state! My biggest gripe with this setup is that to see my secondary calendars and subscribed calendars, I need to create a separate account for each. It would be much better if they just show up under one account. Is this due to a defect in Apple iCal, Google's implementation, or CalDAV protocol?

For my work calendar to become fully manageable in iCal, I have to wait a bit longer, as CalDAV support is coming to Sun Comm Suite Calendar Server in 2009.

[UPDATE] Here's a more complete list of UX issues with Google Calendar in iCal over CalDAV. Also, the developer of the Google Calendar Provider for Thunderbird/Lightning shared his thoughts.

[UPDATE 2009-06-19] Secondary calendars are indeed accessible if you enable them under the Delegation tab in Preferences > Accounts.

Tuesday Nov 06, 2007

Why Twitter won't delete Email

Because it isn't designed to be Email 2.0.

On a recent debate titled "E-mail Faces Deletion" hosted by BusinessWeek, Robert Scoble suggests that Twitter could overtake Email as the leading business communications tool. I read it a few weeks ago but I wasn't on Twitter so I didn't feel qualified to comment. Since then, I've become more familiar with Twitter and found a few of his arguments flawed.

  1. Knowledge retention. While policy varies from country to country, publicly-traded companies and even SMB who don't host their own Email nowadays typically keep Email on the server side and have retention policies (for compliance reasons) which determine how data of former employees is retained and transferred to replacements.
  2. Spam problem. Twitter doesn't suffer from it because users decide who they wish to follow or unfollow. This method is similar to whitelisting and blacklisting and only works in Twitter because it is a walled communication platform and you don't give out your Twitter username as you would give out Email address (on the last page of your presentation, when you fill out online forms, to merchants and service providers, etc).
  3. What happens in Twitter, stays in Twitter. You can depend on Twitter for as long as it is around. Possibly the best way to explain Twitter to non-technical people is that it is a news broadcasting system in which any member can be a broadcaster. This is very appealing to consumers but not so to corporations. For various reasons, good or bad, internal businesses communication most often flow in a controlled and structured manner rather than a broadcasting model.
  4. Twitter lets you filter what others are saying. For example, when Google launched the Open Handset Alliance yesterday, also known as Android, you can do "track android" in Twitter and it'll automatically direct every Twitter message (called "tweet") containing that keyword to you. The upside is that you get to tap into a global community and track actions and thoughts on that topic in near real-time, but the downside is that the signal-to-noise ratio can be very low because everyone can be a broadcaster.

Furthermore, Twitter has a few design choices that make it unsuitable for business use:

  1. Messages are limited to 160 characters.
  2. No support for attachments.
  3. Can't define scope of distribution.
  4. No verification of status. Companies (especially large ones) may wish to cut its tie with terminated employees and it's not clear how Twitter can handle that.

That being said, is Email perfect as a business communication tool? Absolutely not. It's been around for 25 years and I'm confident it'll stick around for another 25 years, but if its weaknesses are not addressed and improvements are not made in time then I doubt it'll maintain its usefulness. Although it's not fair to compare Email with Twitter, there is a few things Email can learn from Twitter:

  1. Needs stronger sender identification. When an Email claims it was sent by Aunt Betty, it must truly came from her and no one else. Twitter's solution is to require account registration and username/password. Systems such as SPF and DomainKeys go so far as to ensure domain-level authenticity, but we need something that goes farther to sender-level.
  2. Needs an API. Twitter offers an API so that users and other developers can discover new ways to use Twitter. Email doesn't have an API, it has RFCs written by lots of people over many years to ensure interoperability, but its fundamentals are largely unchanged even though the rest of the world has progressed. I say it's time for an update, a rethink on modern and future requirements, similar to what ZFS did to filesystem. Excuse the overuse but we need an "Email 2.0".
  3. Needs Permalink. A permalink is basically a fixed index to a web resource to which others link or respond. The vast majority of Email is either an inquiry for response or a response to another inquiry. If every Email message you write has a permalink, then it's a lot easier to track or search when others respond or add value to it.
  4. Follow & track. Once all of the above are in place, these become trivial. In fact, all kinds of new possibilities open up.

Do you think an old dog can learn new tricks? It's only limited by our imagination and drive. Consider how Google uses Email for project management (it's a rather long story, just search for "project management" when the page loads).


I currently live in San Francisco Bay Area. For the past seven years, I have been designing and building messaging solutions for Sun.


« July 2016