This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Why is that page sooooo long and heavy ???

Another surprise from Garmin, and again not in a good way !!!!!

Can someone from Garmin tell me why the page linked below is sooooo long ?

https://developer.garmin.com/connect-iq/reference-guides/devices-reference/

It even makes some of my browsers crash !!!! This is just ridiculous. But that’s not even the point.

It didn’t cross your mind that the detail for each device could be on different pages ? Also because maybe I don’t have to load details for 300 devices while I’m only interested in 2.

Are the Garmin servers limited in pages ?

or you just think that we all have expensive computers and phones ?
Do you even test those pages on different devices ?

Come on again guys, be professional for once !!!

  • There is a change log when new FW for a device is released (in the product forums), and for CIQ, in the top level of a SDK, there is a change log in the README file, for the current version and past ones.

    The README is easy to find with VSC and "View Documentation"

  • The bug report in this case would be about the page being large and slow to load; I consider that a bug, since it's at least unusable to you and probably others. That, from what I can tell, is the main complaint on this thread.

    Regarding change logs, we've got them. The SDK has a change log in the readme distributed with the SDK, and the product firmware has change logs provided by the product teams in the product forums.

    App store filters are a good suggestion—in fact, we used to have a landing page that allowed users to view apps by device, but that list got quite large, and since the common install flow is either through the mobile app or through express, which already limits the app availability to the device to which the apps are installed, we intentionally removed per-device filtering when someone is simply browsing the store. That said, I'll submit a feature request ticket for it along with paid app filtering and see whether the decision-markers would like to do anything there.

    do we need to have a phone call or you guys can start using your products on a daily basis and see the "bugs" by yourself ?

    I'm personally irked by this kind of statement because it's based on a flippant assumption on your part. We do use our products on a daily basis, and we have teams that develop apps for our products, as well. While I can understand your frustration, insult is uncalled for. Thanks for the suggestions—I'll be closing this thread.