After having their 2.0 update ignored by Apple for nearly two months, Appsfire has pulled their current application from the App Store.
Your app-roval process is full of holes; you have approved Appsfire v1.0 last August and wished you hadn't because almost no one had any real clue about discoverability issues back then - indeed, we were the very first to address this issue in an app. Now you know what's at stake, so you've locked-down every aspect of the SDK ToS. Which is probably why you wouldn't write anything to us for 56 days re: Appsfire v2.0, despite our numerous calls, emails, and high level contacts (period during which you had no problem approving similar apps). Was your intent to shut us down by playing the waiting game until the legal team had caught up? The problem remains, in fact we don't even know what the problem might be since you are not talking to us.
This after Steve Jobs suggested during the WWDC Keynote that the App Store approval process was no where near as bad as the press made it out to be.
Read More
Your app-roval process is full of holes; you have approved Appsfire v1.0 last August and wished you hadn't because almost no one had any real clue about discoverability issues back then - indeed, we were the very first to address this issue in an app. Now you know what's at stake, so you've locked-down every aspect of the SDK ToS. Which is probably why you wouldn't write anything to us for 56 days re: Appsfire v2.0, despite our numerous calls, emails, and high level contacts (period during which you had no problem approving similar apps). Was your intent to shut us down by playing the waiting game until the legal team had caught up? The problem remains, in fact we don't even know what the problem might be since you are not talking to us.
This after Steve Jobs suggested during the WWDC Keynote that the App Store approval process was no where near as bad as the press made it out to be.
Read More