Saturday, February 19, 2011

iTunesConnect Frustration: Give it Some Time

Today I encountered a frustration with iTunesConnect. I was uploading an update to Heads Tails ver. 1.9.0 (http://itunes.apple.com/us/app/heads-tails/id303183201?mt=8) and I had to cancel the upload. It seemed straight forward, I hit the cancel button in Application Loader. When I attempted to re-upload the update I found that it was no longer an option. I assumed I needed to go back into iTunesConnect and reject the latest binary, but the app was flagged as "Upload Received". In that state the binary cannot be rejected. I waited a few minutes but it remained like that for a while. I was frustrated because I could not upload the correct binary. After a couple emails to tech support and going for a run I came back to find the status had changed to "Waiting for Review". I was then able to reject the binary and upload the latest update without any problems. The lesson learned...give it some time.

As is the case with many problems patience was the best tool. If you encounter a problem like the one above send an email if you feel strongly about it, but often waiting for a little while is all you need to do.

Thursday, February 17, 2011

App Review Process in iTunes

I would like to see several changes to the way Apple handles reviews in the App Store.

1. Feedback
If a user leaves great, neutral, or harsh feedback there is no way to respond. As a responsive developer I am quick to listen to my users and respond with words and action. In the case of the App Store I can only act by changing the app if there is a problem, but then I have no way to inform the user that this change was made. I don't need to know the user beyond their temporary screen name, but I would very much like to respond directly to them. To thank them when they are positive or offer a rebuttal when they are harsh. Its frustrating because I know I could reclaim users if I could only let them know I had made changes based on their direct feedback.

2. iOS App Store Interface
The iOS App Store Interface makes it hard for users to go to the actual website of the app or company. Its displayed along with the company name, but the link is not active. By refining this interface just a little users could be encouraged to communicate more openly with the developers thereby improving the experience for everyone without the need for feedback flames. If they do have a valid complaint or suggestion often their review comment is too vague and requires clarification, which as described in the previous point cannot happen.

3. Old Reviews
A number of my apps have been in the store prior to Apple changing the review policy of prompting the user for a review when they delete an app. The reviews go back several years and many versions. I would like to see a better break down of reviews over the previous versions and dropping off entirely for reviews that are over 18 months old. This would give users a more accurate evaluation of the current and most recent versions of an app.

4. iOS Dominating
By far the majority of traffic to my web site is by iOS devices. I suspect this is also the case when users purchase apps. They are more likely using the mobile App Store over the desktop. Refining the mobile iTunes experience with the suggestions above would make the process of purchasing (consumer) and maintaining (developer) the apps much easier.

I love developing for the iOs platform, and with a few changes like those described above it can be even better, for users and developers!

Richard de los Santos

Tuesday, February 8, 2011

House iAds

A short term solution to the iAd fill-rate problem is to allow developers to enable house ads. Simply fill the iAds with ads for our other apps. This will generate profit for Apple and developers while at the same time giving developers a chance to promote their apps. Unfilled iAd requests serves no one.

I can understand that Apple wants to have some control over the ads, but since they already approved the apps there is no other oversight required. Auto-generate a banner from the icon or screen shot and fill those unfilled banners.

This would also give Apple a way to block out other advertising networks since many developers roll over to back-up advertising networks when iAds fail to load. House iAds would keep developers in-house with regards to ads and revenue.

At the very least Apple should fill the empty requests with ads for their own products (iWork, Apple Store, Remote, etc...) and give developers an incentive to ignore other networks.