Releasing a version with bug fixes will lower the ranking of the watch face

Garmin has hundreds of watches, and their hardware performance and software versions are different.

Every time I make a new watch face, there always seem to be various bugs. Every time I update a function or fix a BUG, ​​it may cause it to fall out of the rankings.

When I finally achieved high rankings and thousands of downloads, I had to pay a heavy price to fix some bugs that existed on machines 4-6 years ago. What is the purpose of this mechanism?

Is it allowed to release a fixed version without lowering the ranking?

Allow developers to fix bugs as soon as possible instead of being afraid to update due to accumulated rankings.

GARMIN continues to release various resolutions, and various castrated models cover all price ranges. It’s hard for amateur developers to keep up with Garmin.

  • Having less downloads in the cn store has nothing to do with being "off". I think it's just a smaller market in terms of number of Garmin users. Or at least in terms of users who look at apps that are in English.

  • The updates are a bit frequent ,beacuse this is my first watch face.

    During the development process, I gradually learned how to set colors, more options, and conditional expressions. Coupled with new requirements from users, there are many updates. About 40 times, it changed from a dial that could only change the background color to a dial that alternated between day and night, the probability of precipitation would appear as a rainy background, and the stress would be greater than the set value and a volcanic eruption would occur.

    However, because I only supported one resolution at the beginning and had a single function, I missed the exposure stage of the new dial. Later, as the functions were added, some people spontaneously shared it on Chinese social networks. Finally, it achieved a good number of downloads in China and reached the top several times. It also disappeared several times due to updates. So my observation experience of ranking mainly comes from Chinese servers. This is not the same as most people's experience.

    The main server may be OK. Because I have not appeared on the homepage of GARMIN.com.

    I am also currently optimizing the process. avoid mistakes

  • I only see 2 apps of yours that have more than 1000 downloads (and even on the .cn server only one has more than 10k), so I'm not sure what is all the fuss about. In what category is a WF with less than 1000 downloads supposed to be the 1st?

  •  Here is a screenshot I took last week.,

    It’s only 1k+ in a few years, or there are no reviews on the watch face, or a 3.0 rating.

    At present, the cn server is gradually becoming normal. In the past one or two months, as long as it is updated once, it will disappear from the rankings and gradually return in a few days. There may be only 10 popular watch faces downloaded in the top 20. A bunch of watch faces with a 3.0 rating and 100+ downloads from 2018 to date will also occupy the front row.

    But in the past two or three days, these watch faces have finally disappeared. In the Chinese market rank,

    I have only seen watch faces that have been around for more than two years with 100k+ downloads. If those with higher downloads and better watch faces are ranked higher, this is absolutely natural. But sometimes when I can't see my watch face, I scroll down and find many buggy ones with lower downloads.

    I just wonder why this happens. My watch face is back to the front now. But it only takes one update and it disappears again for a few days, or two weeks

    From my perspective, it feels like every update is a huge adventure.。Maybe this time it will disappear completely 

    I have some versions that are only adapted to specific resolutions. If users have problems or make new requests, I will give priority to updating these versions to prevent Major releases from suddenly disappearing from the homepage.

  • Is the App Store ranking system broken? - Discussion - Connect IQ - Garmin Forums   

    Maybe this is the underlying design of the server, someone reported this 8 years ago. I'm not sure if the mechanism has changed now? Or only Garmin China still uses the old design.