Global email in Gmail. Bad idea.

Gmail blog reports that Google is working on a more global email.  The first step is internationalized email addresses, like this:

internationalized_email_address

As someone who worked in international environments for years, I strongly dislike this idea.  There is a whole array of issues related to this: readability of the email address (yes, read it!), display issues (do you have the font with all the necessary characters?), writing email address (searching through the addressbook, for example), or even copy-pasting an email address (have you tried copy-pasting something English strings from Hebrew or Arabic documents?  Now you’ll be copy-pasting international email addresses from English documents – so much fun!).  On top of that, all the usual things related to SPAM filters, trust issues (is this a company, free email hosting, or a personal domain?), etc.  Can you spell out this email address over a phone?  How about typing it on the mobile phone?  Do you even know in which language it is?

Using non-accented Latin characters is a pain for all those people who don’t speak English.  But it worked nonetheless for the last few decades.  Now we are heading towards the future, where that pain won’t be limited to those who don’t read English, but to everyone.  As you can’t really learn all the languages of the world, or control which language email addresses are making it into your inbox.  Remember, that just because the email address is in a given language, it doesn’t mean that the content of the email is in the same language.

On top of that, we’ve tried that already with the international URLs.  See how well that worked out.  Yeah, some people sure use them.  But try copy-pasting this URL around and I guarantee you’ll end up with a whole bunch of long and cumbersome escaped strings.  The same or similar fate will hit the emails…

Google introduces Gmail API

Google is introducing the new Gmail API:

While IMAP is great at what it was designed for (connecting email clients to email servers in a standard way), it wasn’t really designed to do all of the cool things that you have been working on, which is why this week at Google I/O, we’re launching the beta of the new Gmail API.

This is somewhat expected:

Designed to let you easily deliver Gmail-enabled features, this new API is a standard Google API, which gives RESTful access to a user’s mailbox under OAuth 2.0 authorization. It supports CRUD operations on true Gmail datatypes such as messages, threads, labels and drafts.

As a standard Google API, you make simple HTTPS calls and get your responses in JSON, XML or Google Protobuf formats.

This is a nice bonus:

In contrast to IMAP, which requires access to all of a user’s messages for all operations, the new API gives fine-grained control to a user’s mailbox. For example, if your app only needs to send mail on behalf of a user and does not need to read mail, you can limit your permission request to send-only.

To keep in sync, the API allows you to query the inbox change history, thereby avoiding the need to do “archaeology” to figure out what changed.

They are also saying that it’s fast.  These are very welcome news indeed.