AppStore app release date doesn't make sense

Is anyone else annoyed with Apple’s policy for listing one’s app with wrong release date? Quote from iTunes Connect FAQ:

“Does the “Released” date displayed for my application in the App Store have an effect on my application?  The "Released" date is listed as part of basic app information displayed on the App Store.
The "Released" date is currently determined by the date of the app's approval by Apple and the availability date that the developer has listed within iTunes Connect,
whichever is earlier. “

"Whichever is earlier"?! Really?! Why? Let’s see...
I was thinking they supposedly had a bug in their system the first time I encountered this with one of our apps. The date set by us was earlier than the date Apple approved the app so it was listed with this earlier date on 3rd or 4th page in iTunes latest apps list. At the time I was unaware I could change the release date.

Shortly after, we submitted the new app knowing that Apple will probably take about 2 weeks to review it so we set the release date to 16 days after our submission which would give us more-less 2 days after the app is approved to go live. And we hoped with the correct release date. Well, we should have read the FAQ since they listed the earlier date - the date of the app approval listing our app on 3rd page in iTunes without any chances of correcting the date.

We learned on our mistakes, so I guess the correct way is to set a very early release date and when the app gets approved and listed with that early date we would simply change it. Read on some blogs this is possible so I’m going to try that.

Similar mess happens for the updates except when you release the update the date won’t change at all. You’ll need to change it by yourself on iTunes Connect.

To sum up, I can’t believe Apple is doing this. I can’t seem to find any logical reason, if someone knows please let us know. Seeing that they’ve put up a FAQ for this mess, I believe they don’t intend to change it and it certainly isn’t a bug as I previously thought. Well... one more surprise from Apple, I’ll just stick to this workarounds for the time being.
0 Comments