Acknowledged
5 months ago

App Downloads: Please show a more exact number of app downloads in the CIQ store

I have recently made my own watch face and uploaded it to the Connect IQ store, however, it is very difficult (and a little frustrating) as a developer to not be able to see the amount of downloads I have. For a number of days, all I knew about my watch face's progress was that it had "100+" downloads. Then when I checked yesterday, I saw that it was finally "1K+". But that's all we as developers see. A developer who has "100K+" won't know how many downloads they have until they reach "500K+" - and that is a very massive gap that could take months before the developer really finds out a better approximation of how many downloads they have.

I have really enjoyed being able to make this watch face and I am very thankful that Garmin has provided means for independent developers to do so, but it is very difficult to gauge what audiences want if we don't know anywhere near how many people are actually interested in the product. Even just showing "1.2K" or "534K" is better than having to wait tens of thousands or hundreds of thousands of downloads (and many months later) before knowing how many downloads we have.

Please consider adding this feature as it would really make marketing a little easier for independent developers. Thank you!

singularity
Parents
  • 2 months ago

    It would be simple to show the precise number but caveat the value with a statement that this may be subject to change and cannot be replied upon in the calculation of payment due.

    I think the point is to hide the exact number from *people other than the app dev*. Garmin didn't do bc they're worried that the dev of a monetized app will be misled about the number of downloads, they did it so people other than devs will have a tougher time estimating the revenue of such an app. And by doing so, they also hide the number from the devs themselves, which obviously sucks.

    Showing the precise value with a caveat wouldn't accomplish their goals here.

    What they could do is show the precise value, but only to the app dev.

    As I have pointed out elsewhere:

    - the google play store does the exact same kind of "severe rounding" (e.g. 1+, 5+, ..., 10K+, 50K+, ...)

    - the iOS store doesn't even show download numbers, only download ranks

    All my apps are free and  I have declared that they are so during submission so there really is no good reason not to provide this information.

    It's easier for Garmin to apply a blanket policy / implementation rather than carving out special exceptions. What if your app starts out free but becomes paid?

    Again it would be a lot simpler if Garmin were to just provide devs with the same precise stats we had before, but it remains to be seen whether this will happen.

Comment
  • 2 months ago

    It would be simple to show the precise number but caveat the value with a statement that this may be subject to change and cannot be replied upon in the calculation of payment due.

    I think the point is to hide the exact number from *people other than the app dev*. Garmin didn't do bc they're worried that the dev of a monetized app will be misled about the number of downloads, they did it so people other than devs will have a tougher time estimating the revenue of such an app. And by doing so, they also hide the number from the devs themselves, which obviously sucks.

    Showing the precise value with a caveat wouldn't accomplish their goals here.

    What they could do is show the precise value, but only to the app dev.

    As I have pointed out elsewhere:

    - the google play store does the exact same kind of "severe rounding" (e.g. 1+, 5+, ..., 10K+, 50K+, ...)

    - the iOS store doesn't even show download numbers, only download ranks

    All my apps are free and  I have declared that they are so during submission so there really is no good reason not to provide this information.

    It's easier for Garmin to apply a blanket policy / implementation rather than carving out special exceptions. What if your app starts out free but becomes paid?

    Again it would be a lot simpler if Garmin were to just provide devs with the same precise stats we had before, but it remains to be seen whether this will happen.

Children
No Data