Wednesday, 3 October 2012

May be it's not that difficult to get an iPhone 5?

I read quite a few not-so-nice news about iPhone 5 recently (e.g. see here, here, and over heating and battery issue) and was a bit reluctant to order one delivered as it would be hard to argue/explain if it's been delivered and found any problem (plus the hassle of bringing it to a shop to swap), vs opening it from box inside an Apple store. Was also struggling if should wait for "iPhone 5 version 1.01", as first version of most new IT products were always full of bugs (rushed to meet deadline?)...

Walked past the Sydney Apple city store last Friday and was told they are out of stock and need to make a reservation between 7am and 3pm on this special link, and will receive a response before 9pm if stock is available in the shop I selected.

I tried once yesterday around 1pm, of course, nothing received. Then tried again around 8am this morning, and I got this email around 8:54pm! Wow, I thought there was a stock shortage of iPhone 5 and everyone has to wait until end of October or something like that??

Actually I never expect to get it straight away and tomorrow morning I might not even be able to make it due to other commitments at work... I have cancelled my reservation, and my apology to those who reserved today but didn't get it because of my "test" reservation, please try again tomorrow :-)...

So despite all the news and marketing hype, looks like it's not that difficult to get an iPhone 5 - only a few weeks after it's announcement - at least in Sydney?

Still working on changing my 2 games for iOS6 and iPhone 5, seriously, base on all these, I might just wait for iPhone 5 version 1.01...

2 comments:

  1. There are devices that are truly worth the wait. It may mean taking some time for enthusiasts to wait for iPhone 5 but I guess, it is the user experience that will matter most.

    ReplyDelete
  2. You are right that first product is always full of bugs. To get the bugs free product we have to wait . Thanks for sharing this post.

    ReplyDelete