ropedrop.net
Online Services Aren't Easy and Disney Does Them Fairly Well — Rope Drop [dot] Net
At 3am Eastern today, I–like many a technology geek–was loading and reloading the Apple Store on my existing iPhone in hopes of securing a new iPhone on next Friday’s launch day. The store was supposed to go live at 3:01am, but at 3:08am I was still getting the “check back soon” message that Apple puts up when it’s updating its store. People on Twitter were–justifiably–complaining about how frustrating things were. When I finally got into the store, I received a generic “unable to complete transaction at this time” error on 6 different attempts before my order went through on my phone (during which time I–unnecessarily–went to my computer as a backup, in case I was doing something wrong on my phone). A basic online order that should have probably been completed by 3:04am wrapped up at 3:37am. When the process was completed, I tweeted about how much the whole experience made me long for Disney’s ADR system. I know there are differences in scale–orders of magnitude differences, probably–but, every day of the year Disney enables its ADR system at exactly 6:00am to allow thousands of people to make their 180-day reservations. Every day. I’ve gone through that process at least 25 times, sometimes making tens of reservations, and it usually works pretty well. The same goes for making new Fastpass+ selections, changing ADRs, and otherwise using My Disney Experience (these days, anyway). Before you start sending me pictures of your Donald Duck error message (or Stitch in the rain), let me be clear: I am not saying Disney is perfect. I’ve had problems–sometimes very annoying and difficult to correct problems–using Disney’s web services, as I am sure many of you have. What I am trying to say, however, is that making web services which have to support the kind of …