Absence of proper Clock/App rating and installation statistics

[Guy_]

With the addition of more watches to the Fitbit line up, the absence of statistics "by watch" is penalizing developers, because they have no way of knowing whether a good or poor rate refers to a success or problem on any particular watch type, which may require further investigation without knowing where.

A good statistics is all the more important since some clock faces have been ported possibly without developer knowledge to the more recent watches and without having been verified by the developer first.

This can lead to getting worse [or no] ratings where the developer has no means of knowing what is happening, where or why.

We need the number of ratings, downloads and currently active states, by watch type, for each app and clock that has been published. This has already been requested many times before.

How can we urgently get the proper statistics by watch, NOW, to help improve the situation for developers? It would certainly at least show that Fitbit thanks them for their efforts and encourage them to do further development.

[Guy_]

There is an alternative to Fitbit providing good statistics and that is for each developer to do it themselves by using an Internet permission and/or payment system to get the information.

However this will discourage some users who take security seriously from installing such clocks or apps which request an open Internet connection, so developers employing those methods have a lot more work to do and may get considerably less users for their efforts.