
Cooling off after a purchase makes for happier users and devs. Photo by Kyle May.
Yesterday morning, I woke up and – as I do every morning – reached for my iPhone to turn off my alarm. Still in bed (and still on my iPhone), I skimmed Twitter, Facebook, and my email where I found a message that made me want to check something on my notebook. It being the grey, rainy, and horrible day that it was, I didn't want to get up and go downstairs just yet.
"Ah! Wait a second… I don't have to!", I thought.
A while back I had purchased Jaadu VNC for remote controlling my laptop from anywhere. Although it cost me about £15, it was a great app and did exactly what it said on the tin. I just needed to download it again from the App Store and I could laze in bed for as long as I wanted to.
So off I tapped to the App Store, searched for Jaadu, saw the icon and tapped the Buy Now button to download it again.
Mission accomplished? Not quite. Quite the contrary, actually.

The problem, dear Brutus, is that I've already bought this app… or did I?
This brings me to my first issue with the App Store and it is one of basic usability:
Downloading previously-purchased apps is a game of Russian Roulette
There are two usability issues with downloading previously-pruchased apps on the App Store. The first is the following:
- You can't see whether or not you've already purchased the app you're viewing in the store, and
- To download the app, you have to tell the App Store that you want to buy it. Only after you've asked to purchase it does the phone inform you that you've already bought it and can download it again.
So what happens if you mistakenly tap the Buy Now button on an app that you thought you had bought, but which you actually hadn't? You will, of course, end up buying the app for the first time.
But surely that would never happen, right?
I mean, who doesn't remember which app they've bought?
That's right, yours truly!

Same icon, different app.
Little did I realize, in my freshly-woken state, that I had tapped the Buy Now button on Jaadu Remote Desktop For Windows (i.e., on Jaadu RDP not Jaadu VNC). It gets worse: both apps share the exact same icon and sell for exactly the same price of £14.99. This brings me to my second usability issue:
App icons must be unique.
App icons are the primary visual means by which we identify applications on the iPhone. Apple should not allow two applications to share the same app icon and should, furthermore, keep an eye out for icons that aim to confuse users by appearing too similar to other – potentially more popular – apps.
But what if you did end up purchasing an app by mistake? Surely, there's some avenue for recourse, right? Well, according to the iTunes Store policies, no: All Sales Are Final.
With the iTunes Store, all sales are final. As soon as you click the Buy button (using either 1-Click or the Shopping Cart) your purchases are charged to the credit card on your Apple Account. You cannot cancel a purchase or receive a refund for a purchase.
So, basically, you can try and contact support (like I did, I'm waiting to hear back from them) but unless Apple decide to special case your support request and give you a refund, you're screwed.
Now, as a developer who is anxiously looking forward to having his first app on the App Store before Christmas, I don't like this. It isn't good for users or for developers.
No refunds means that users suffer
Apple's no refunds policy for the App Store, coupled with the usability problems I outlined above, can lead users to make erroneous purchases. This means that users end up getting the short end of the stick.
And what if a user didn't make a purchase by mistake? What if they bought your app, tried it out, and within the first few minutes realized either that they hated it, or that it didn't do what they thought it would or <enter your reason here>? What options do they have? None.
Oh wait, did I say none? I meant they have just one option: to leave a tersely-worded 1-star review for your app on the App Store.
No refunds means that developers suffer
If, for whatever reason, users cannot get a refund for an app that they are unhappy with, they are going to be feeling cheated. Out of anger and frustration they are going to do the only thing they can to get back at the developer for making them feel this way: leave a 1-star review for their app. These 1-star reviews skew the app's ratings down and hurt developers by resulting in lost sales in the future.
But what if users had another option?
After I tweeted about the mistake I made in purchasing Jaadu RPD, Bruno Figueiredo wrote a reply that gave me pause for thought and eventually resulted in me writing this blog post:
@aral that wouldn't be a problem of you were able to undo your purchase within say 7 days.
The App Store needs a cooling off period
Now, I'm not suggesting that the App Store implement a 7-day cooling period. In the face of research that suggests that less that 15% of paid apps are actively used after the first week, suggesting that would be unrealistic. Apple would never agree to something that would so drastically reduce the profitability of the App Store. But how about a much shorter cooling off period that would be just as, if not even more, effective?
How about a 1-hour cooling off period?
A 1-hour cooling off period would benefit users, developers, and Apple.
1-hour cooling off period benefits for users
For users, it would mean that they can easily reverse purchases made in mistake and get refunds for applications that they discover either don't perform as stated or as expected.
It would also allow users to try applications out before having to commit to buying them. That, ironically as it might seem at first thought, brings me to the first of the benefits for developers.
1-hour cooling off period benefits for developers
A 1-hour cooling off period would benefit developers perhaps even more than users.
It would mean that users would not have a basis for leaving 1-star reviews out of anger and frustration. An hour is more than long enough to evaluate whether a mobile application fits your needs. And, as a developer, do you really want to take your user's money if they're not going to use your app for more than an hour or if they bought it by mistake?
Needless to say, a reduction in 1-star reviews will mean that developer's future sales are not negatively impacted.
More than that, it will mean that developers no longer need to invest time and development effort (i.e., money) in maintaining both a full and a "lite" version of their apps. In other words, a 1-hour cooling off period will reduce developer's costs.
But how about Apple? A 1-hour cooling off period would also benefit them.
1-hour cooling off period benefits for Apple
Apple should be looking at its investment in the App Store as a long-term one. Short-term profits are great (and 'a plenty currently) but equally as important is long-term perception and growth. Having the App Store perceived as fair is an important factor in affecting long-term perceptions and future profits. Not having irate customers is good for business: giving them a pressure valve to release their frustrations before they accumulate can only be a good thing in the long run.
Beyond that, having 1-star reviews on apps hurts future sales of those apps. Since Apple gets 30% of those sales, it also hurts Apple's bottom line. And that irate customer may also curtail her app purchases in general, hurting Apple even more.
At the end of the day, 1-star reviews don't benefit anyone: not users (who may get to vent but don't get the actual compensation they were seeking), not developers (who suffer from lost sales), not Apple (who also suffers from lost sales), and not Apple's shareholders (who – although a rather lucky bunch – end up not maximizing their profits.)
To state it plainly: The cure for the 1-star review plague affecting the App Store today is implementing a 1-hour cooling off period.
Finally, as an additional benefit to Apple, a 1-hour cooling off period may have the affect of helping to weed out apps with very little or no value (read: fart apps and their kin) and may help apps with higher and longer-term value to rise to the top of the sales lists, thereby raising the standard of the App Store in the process.
In Summary…
To recap, the App Store currently suffers from several usability issues that make it possible for users to make erroneous purchases. Its current policy of "no refunds" only works to hurt users, developers, and ultimately Apple itself. The solution to all these is for Apple to implement a 1-hour cooling period for app purchases.
I look forward to hearing your comments on this and to hopefully seeing Apple address this issue in the near future.
If you “report a problem” with the application and tell Apple about the mistake you made in buying the app, they’ll most likely give you a refund. They *say* all sales are final, but they still give people refunds. I can only speculate that Apple doesn’t want them to be commonplace and/or abused by less than honest users, but they know that mistakes are made and apps can be buggy.
That being said, us iPhone developers are still out the 30% cut to Apple when they decide to refund a customer, because someone still has to pay for the transaction charges. Not to mention the way refunds work now you may not get updates in the future, but the application will still work for as long as you have it, nothing is disabled.
But ultimately, I don’t disagree with your take. Apple *needs* to come up with a solution to things like that, and I think “mistake purchases” are probably handled as best they can now, but instead of a 1 hour cooling off period, they need to let us do trial apps limited by time and/or features. Not lite apps that otherwise may as well be completely different from the full version, but a trial right smack dab on the same page as a download link next to the full version. Almost like a subset of in-app purchase, but it wouldn’t make your user feel like he/she is being nickel and dimed as (hopefully) it will be clear that a trial was downloaded, not an app they might have thought was a full version but in fact they have to pay some fee they didn’t know of to use.
Just a quick update: I got a nice email from Bryan at Apple telling me that they’ve reversed the charge.
Hey Jane, first off, thank you for your sharing your thoughts. I’m just not sure why having a trial app is superior to having a cooling off period. Why maintain two apps when you can have your app – and every app – default to having a one-hour trial period?
Less work for developers; a consistent experience and expectations for users: win-win! :)
Hi Aral
It occured to me that the App store and all purchases made through it would be classed as Distance selling. As a result, in UK at least, we should by law have a colling off period (7 days IMS).
I doubt Apple are above UK law.
When I wrote this post, I didn’t realize that Google’s Android Market actually has a 24-hour cooling off period where you can get a refund on any app with no questions asked by pressing an “Uninstall & Refund” button.
Talk about getting it right!
So, I guess the title of this post should be, “Apple, follow Google’s lead on mobile app refunds.”
Hi Aral,
You did a perfect usability study and issues of users & Developers on the return policy requirements on Apple Store. Great!
You had faced the problem by yourself and thus the solution and suggestion.
Feel free to contact me.
Thanks,
Srini Centhala
I assume some part of this policy has to do with a present limitation of small-ticket and micropayments: the overhead is a major fixed component.
The credit card industry is not up to speed with digital transactions, in many ways. Refunds on low value transactions are expensive due to how the credit-card system works, and chargebacks even more so. A chargeback on a $2 app purchase can easily cost $15, not counting support time and employee costs if manual intervention is required.
So I think it’s understandable if Apple doesn’t want to get into that mess by bringing up the topic of refunds.
However I agree with the first point – that apps you have already purchased should not have a purchase link displayed if you are logged in. Perhaps it was acceptable with ‘Web 1.0′, but this is 2009.
Great article, and it’s great to see others think about the same minutiae that I do. I’ve often had the same “wince to buy” that you explained.
A friend recommended a camera app, and I couldn’t remember what it was called. I thought it was “PerfectPhoto” or “BestCamera”, but I couldn’t remember the name. Less than a minute after the purchase, I realized I bought a knock-off. Even though it was $2.99 USD, it’s still such a horrible feeling.
The flip-side experience is not wanting to trash these sucky apps even a year later. If Apple can track everything so closely (and quite well), they should have a consignment store for pre-owned apps. Just like Amazon — “buy it used for $x.” :-)