Include App Memory and other statistics ALONGSIDE device data such as screen dimensions and touchscreen existence in device listing

Please include the App Memory and other memory-related statistics alongside the device data on https://developer.garmin.com/connect-iq/compatible-devices/ and https://developer.garmin.com/connect-iq/reference-guides/devices-reference/ rather than further down the page with the font info.

I would like the app/datafield memory statistics arranged horizontally next to screen dimensions and the like, rather than vertically as it is currently arranged, further down on the page. As a developer, it is presently difficult to determine the memory footprint available on each device, so a horizontal arrangement would help me to better target difference devices. Currently I have to copy the values to an excel worksheet and spend a half hour fixing it up so I can reference which device has what memory, and if the information was already presented in an easy to export manner it would help save time.

mqbfxw

mqbfxw over 3 years ago in reply to Travis.ConnectIQ

Sorry about the lack of clarity in this request. To answer your last question, no.

I would like the devices listed in column one, and their specifications listed in columns 2, 3, 4, etc. One row per device. If all the data in the two side-by-side tables merged and rearranged horizontally on a single table with the device in the first column, app memory in another column, screen dimensions in a third, that would be ideal. Pretty much like the first table on the page https://developer.garmin.com/connect-iq/reference-guides/devices-reference/ except also including app memory, datafield memory etc, so anyone looking for that data doesn't have to press CTRL+F and search for it in the lower tables.

Ultimately I would like to be able to sort devices by their available app memory, so I can quickly determine which platforms I need to offer reduced functionalities for, and/or which platforms to offer alternate resources for etc. I made this one last night so I can reference it when releasing new upgrades on my current app, www.landnavapp.com/Devices_With_AppMemoryLimit.xls

I'm not familiar with the reasons why the tables are split up, but if there is better logic to keeping them separate, then please carry on with that. Thanks
- Cancel
- Up 0 Down
- More
- Cancel
Travis.ConnectIQ over 3 years ago

The memory limits are currently shown as a table immediately following the device data.

https://developer.garmin.com/connect-iq/reference-guides/devices-reference/#approach%C2%AEs60

Are you suggesting we display the two tables side-by-side?
- Cancel
- Up 0 Down
- More
- Cancel