Reminder+ 2.0 Sales Numbers

Version 2.0 of Reminder+ was released earlier this year, on the 26th August.

Around that time (in Expectations for Reminder+ 2.0) I wrote the following:

OK, so I’ve been working on 2.0 for a while, do I have any expectations for improved downloads/sales?

No, not really.

With the footnote:

Although I left the keywords alone, I did change both the name of the app and the app icon. Whilst these changes could improve performance in the App Store, they could potentially make the situation worse.


Here are the numbers from the three months after the release of v2.0:

  • Days: 92 (3 months)
  • Downloads: 621
  • Downloads / day: 6.75
  • IAPs: 62
  • IAPs / day: 0.67
  • IAP conversion rate: 10%

Compared to the numbers for the previous version, from the first 8 months of 2015:

  • Downloads / day: 6.7
  • IAPs: 223
  • IAPs / day: 0.92
  • IAP conversion rate: 13.8%

As it turns out, the download numbers/App Store performance are ever so slightly better (essentially, the same). This is re-assuring as I figured my App Store changes were positive, making the app more targeted and appealing.

However, the IAP conversion rate has suffered, dropping from 13.8% to 10%.

For me, for this app, the numbers are so low that there’s no consequence to this. That said, a drop from 13.8% to 10% is of interest.

Possible causes?

  • There is (slightly) more going on in the app: the workflow and UI changes could be worse for engagement, use, and ultimately, deciding to try the IAP.
  • The Settings page, specifically, has additional information and options. Previously, there was a single option, the IAP; the extra stuff might be distracting users from finding/exploring/considering the IAP.
  • Version 2.0 added a second IAP: this may confuse the process of ‘buying an upgrade’, it might change the user’s view of the app/the developer, etc. Ultimately, it’s possible the additional IAP is hurting the conversion of the primary upgrade.

Whilst I’m interested in the change to the IAP conversion rate1, I’m more interested in my evolving view of this app: who uses it, how often, the problem(s) it currently solves and what I’ve learnt about why some of the users are using it.

I’ll write about this in the next post…

  1. I’m aware that analytics would be of use here.