Thoughts on MobileMe and Apple

As I’ve spent the past 24 hours wiping my Macbook Pro and trying to get back up to speed, I thought I’d give a few thoughts on MobileMe, Apple Mail and Push/Cloud technology.

This is relatively raw as I am much more focused on getting back to work than I am “getting things right” as they say in the journalism business. I’m a user. I’m a tech guy. I’m a Unix guy. I’m an Apple guy. Those are the lenses I see this world through.

MobileMe Saved My Preference Life

MobileMe saved my life in terms of preferences, contacts and calendar. It was absolutely beautiful to watch everything sync beautifully back into place on a fresh install of Leopard.

Apple Mail no Longer Handles TLS/SSL Authentication

Apple Mail no longer wishes to communicate with my mail server running Zimbra. Mind you, the exact same setting exist between a parallel install of Thunderbird, but Apple Mail will not authenticate against a TLS based server. It was mildly flakey before, but it worked. Now it simply will not work no matter what combination of settings I try.

Standardize around Protocols, not Products

If I have to use Thunderbird, it would be nice if I could connect to MobileMe to sync my address book. Others, apparently, feel the same way. Why is MobileMe contacts and calendars not running on a WebDAV server that any client can develop communication prototypes against? If I have to use Thunderbird as opposed to Apple Mail, I lose the selling point of MobileMe.

Likewise, Apple is building for the software on the Windows side with people complaining that you can only use MobileMe with Outlook. What about Outlook Express, Thunderbird, etc?

What about Gmail, Hotmail, Yahoo Mail?

Bad software development always starts with developing against the symptom instead of the root problem. A better concept for MobileMe would be to develop around standard protocols: POP/IMAP/Exchange for Mail, CalDAV for iCal, WebDAV/LDAP for contacts.

Just some thoughts for the Apple Team. There’s probably more I can’t address at this time. What advice would you give the Apple product teams around their products, particularly their productivity products?

Bonus: Why is the Mozilla team not supporting native Mac datastores (Address Book) on their Mac products”?

Published by

Aaron Brazell

Aaron Brazell is a Baltimore, MD-based WordPress developer, a co-founder at WP Engine, WordPress core contributor and author. He wrote the book WordPress Bible and has been publishing on the web since 2000. You can follow him on Twitter, on his personal blog and view his photography at The Aperture Filter.

54 thoughts on “Thoughts on MobileMe and Apple”

  1. Sounds like you want the upcoming CardDAV standard for contacts. It will be supported in Snow Leopard (10.6). But if the current situation is any indicator, there will be a CardDAV server in Snow Leopard server but MobileMe won’t offer a CardDAV server (which I agree is a big problem).I’m not sure how good LDAP is for allowing people to write their own contacts. I usually think of LDAP being used in situations where there is a single authoritative database (such as at a company). CardDAV allows you to manage your own set of contacts. You can imagine you could have Note field on a contact which may have a different value than a Note field for the same contact in someone else’s CardDAV-backed address book. I’m not sure you could do that in LDAP.

  2. Sounds like you want the upcoming CardDAV standard for contacts. It will be supported in Snow Leopard (10.6). But if the current situation is any indicator, there will be a CardDAV server in Snow Leopard server but MobileMe won’t offer a CardDAV server (which I agree is a big problem).I’m not sure how good LDAP is for allowing people to write their own contacts. I usually think of LDAP being used in situations where there is a single authoritative database (such as at a company). CardDAV allows you to manage your own set of contacts. You can imagine you could have Note field on a contact which may have a different value than a Note field for the same contact in someone else’s CardDAV-backed address book. I’m not sure you could do that in LDAP.

  3. Sounds like you want the upcoming CardDAV standard for contacts. It will be supported in Snow Leopard (10.6). But if the current situation is any indicator, there will be a CardDAV server in Snow Leopard server but MobileMe won’t offer a CardDAV server (which I agree is a big problem).I’m not sure how good LDAP is for allowing people to write their own contacts. I usually think of LDAP being used in situations where there is a single authoritative database (such as at a company). CardDAV allows you to manage your own set of contacts. You can imagine you could have Note field on a contact which may have a different value than a Note field for the same contact in someone else’s CardDAV-backed address book. I’m not sure you could do that in LDAP.

  4. Sounds like you want the upcoming CardDAV standard for contacts. It will be supported in Snow Leopard (10.6). But if the current situation is any indicator, there will be a CardDAV server in Snow Leopard server but MobileMe won’t offer a CardDAV server (which I agree is a big problem).I’m not sure how good LDAP is for allowing people to write their own contacts. I usually think of LDAP being used in situations where there is a single authoritative database (such as at a company). CardDAV allows you to manage your own set of contacts. You can imagine you could have Note field on a contact which may have a different value than a Note field for the same contact in someone else’s CardDAV-backed address book. I’m not sure you could do that in LDAP.

  5. Sounds like you want the upcoming CardDAV standard for contacts. It will be supported in Snow Leopard (10.6). But if the current situation is any indicator, there will be a CardDAV server in Snow Leopard server but MobileMe won’t offer a CardDAV server (which I agree is a big problem).I’m not sure how good LDAP is for allowing people to write their own contacts. I usually think of LDAP being used in situations where there is a single authoritative database (such as at a company). CardDAV allows you to manage your own set of contacts. You can imagine you could have Note field on a contact which may have a different value than a Note field for the same contact in someone else’s CardDAV-backed address book. I’m not sure you could do that in LDAP.

  6. Sounds like you want the upcoming CardDAV standard for contacts. It will be supported in Snow Leopard (10.6). But if the current situation is any indicator, there will be a CardDAV server in Snow Leopard server but MobileMe won’t offer a CardDAV server (which I agree is a big problem).I’m not sure how good LDAP is for allowing people to write their own contacts. I usually think of LDAP being used in situations where there is a single authoritative database (such as at a company). CardDAV allows you to manage your own set of contacts. You can imagine you could have Note field on a contact which may have a different value than a Note field for the same contact in someone else’s CardDAV-backed address book. I’m not sure you could do that in LDAP.

  7. Sounds like you want the upcoming CardDAV standard for contacts. It will be supported in Snow Leopard (10.6). But if the current situation is any indicator, there will be a CardDAV server in Snow Leopard server but MobileMe won’t offer a CardDAV server (which I agree is a big problem).I’m not sure how good LDAP is for allowing people to write their own contacts. I usually think of LDAP being used in situations where there is a single authoritative database (such as at a company). CardDAV allows you to manage your own set of contacts. You can imagine you could have Note field on a contact which may have a different value than a Note field for the same contact in someone else’s CardDAV-backed address book. I’m not sure you could do that in LDAP.

  8. Sounds like you want the upcoming CardDAV standard for contacts. It will be supported in Snow Leopard (10.6). But if the current situation is any indicator, there will be a CardDAV server in Snow Leopard server but MobileMe won’t offer a CardDAV server (which I agree is a big problem).I’m not sure how good LDAP is for allowing people to write their own contacts. I usually think of LDAP being used in situations where there is a single authoritative database (such as at a company). CardDAV allows you to manage your own set of contacts. You can imagine you could have Note field on a contact which may have a different value than a Note field for the same contact in someone else’s CardDAV-backed address book. I’m not sure you could do that in LDAP.

  9. Sounds like you want the upcoming CardDAV standard for contacts. It will be supported in Snow Leopard (10.6). But if the current situation is any indicator, there will be a CardDAV server in Snow Leopard server but MobileMe won’t offer a CardDAV server (which I agree is a big problem).I’m not sure how good LDAP is for allowing people to write their own contacts. I usually think of LDAP being used in situations where there is a single authoritative database (such as at a company). CardDAV allows you to manage your own set of contacts. You can imagine you could have Note field on a contact which may have a different value than a Note field for the same contact in someone else’s CardDAV-backed address book. I’m not sure you could do that in LDAP.

  10. Aaron,Not sure what’s up with your mail.app vs. Zimbra issue, I don’t think we haven’t experienced that issue running Zimbra 5.0.2 on up through 5.0.8 on any of the systems we manage, and all of them use 256-bit SSL public certs. Not that it’s related, and curious if you are using the Zimbra Mobile license?With respect to CardDAV, it’s on the horizon with Zimbra, too.Best. 01.com

  11. Aaron,Not sure what’s up with your mail.app vs. Zimbra issue, I don’t think we haven’t experienced that issue running Zimbra 5.0.2 on up through 5.0.8 on any of the systems we manage, and all of them use 256-bit SSL public certs. Not that it’s related, and curious if you are using the Zimbra Mobile license?With respect to CardDAV, it’s on the horizon with Zimbra, too.Best. 01.com

  12. Aaron,Not sure what’s up with your mail.app vs. Zimbra issue, I don’t think we haven’t experienced that issue running Zimbra 5.0.2 on up through 5.0.8 on any of the systems we manage, and all of them use 256-bit SSL public certs. Not that it’s related, and curious if you are using the Zimbra Mobile license?With respect to CardDAV, it’s on the horizon with Zimbra, too.Best. 01.com

  13. Aaron,Not sure what’s up with your mail.app vs. Zimbra issue, I don’t think we haven’t experienced that issue running Zimbra 5.0.2 on up through 5.0.8 on any of the systems we manage, and all of them use 256-bit SSL public certs. Not that it’s related, and curious if you are using the Zimbra Mobile license?With respect to CardDAV, it’s on the horizon with Zimbra, too.Best. 01.com

  14. Aaron,Not sure what’s up with your mail.app vs. Zimbra issue, I don’t think we haven’t experienced that issue running Zimbra 5.0.2 on up through 5.0.8 on any of the systems we manage, and all of them use 256-bit SSL public certs. Not that it’s related, and curious if you are using the Zimbra Mobile license?With respect to CardDAV, it’s on the horizon with Zimbra, too.Best. 01.com

  15. Aaron,Not sure what’s up with your mail.app vs. Zimbra issue, I don’t think we haven’t experienced that issue running Zimbra 5.0.2 on up through 5.0.8 on any of the systems we manage, and all of them use 256-bit SSL public certs. Not that it’s related, and curious if you are using the Zimbra Mobile license?With respect to CardDAV, it’s on the horizon with Zimbra, too.Best. 01.com

  16. Aaron,Not sure what’s up with your mail.app vs. Zimbra issue, I don’t think we haven’t experienced that issue running Zimbra 5.0.2 on up through 5.0.8 on any of the systems we manage, and all of them use 256-bit SSL public certs. Not that it’s related, and curious if you are using the Zimbra Mobile license?With respect to CardDAV, it’s on the horizon with Zimbra, too.Best. 01.com

  17. Aaron,Not sure what’s up with your mail.app vs. Zimbra issue, I don’t think we haven’t experienced that issue running Zimbra 5.0.2 on up through 5.0.8 on any of the systems we manage, and all of them use 256-bit SSL public certs. Not that it’s related, and curious if you are using the Zimbra Mobile license?With respect to CardDAV, it’s on the horizon with Zimbra, too.Best. 01.com

  18. Aaron,Not sure what’s up with your mail.app vs. Zimbra issue, I don’t think we haven’t experienced that issue running Zimbra 5.0.2 on up through 5.0.8 on any of the systems we manage, and all of them use 256-bit SSL public certs. Not that it’s related, and curious if you are using the Zimbra Mobile license?With respect to CardDAV, it’s on the horizon with Zimbra, too.Best. 01.com

Comments are closed.