In case it is useful to anybody else: searchable device database for SDK 3.18

You'll also find details here:

https://developer.garmin.com/connect-iq/compatible-devices/

Not the memory limits, but width/height/colors/CIQ version.  It's only ROW devices and not APAC.

Very nice! thanks!

Just uploaded an update that includes a few more bits and pieces.

G

Really useful, thank you!

Just added "BPP" istouch and wifi_exclusions for each device.

OK, so now the Excel has been merged with all the data from https://developer.garmin.com/connect-iq/compatible-devices/

The first tab is devices.xml and the second tab is compatible devices.

Use "filter" searches to find what you need. Both sheets have XML generators to paste straight into manifest.xml

But remember, in manifest.xml it says:

<!-- This is a generated file. It is highly recommended that you DO NOT edit this file. -->

It's really add to set targets/permissions/etc with Eclipse, so this may not be something for beginners

Fair enough point, but I’d still beat you finding every device with a given capability with the spreadsheet than with compatible devices link!

It was nightmarish trying to hone my list based on clicking countless blue circles and hoping I saw the entry for what I needed... 

Quite why Garmin can’t provide a better compendium of their own products beggars belief. 

They _clearly_ not only have the data but (in the background) have it in a useful form. 

What I did back in 2005, was throw together a simple app that told me all I needs for a given device, where a huge amount of "has" statement, and it's things like does a device support SensorHistory, but also, which histories.  It displays all the standard font and indicates white space above/below, etc. I'm at about 10 screens of info right now.

A new target comes out, I just add it and run in the sim.

The problem with a spread sheet is is becomes a maintenance issue when a new SDK comes out, and you get into issues with beta SDKs (as happened with 3.0.0 and 3.1.0) when there's a time where there are 2 active SDKS with different features.

The only reason this is a spreadsheet is that Garmin haven’t put their existing, well maintained, searchable, complete and accurate data into a similarly accessible form. 

So I had to locate the JSON and parse it into Excel. Likewise, for devices xml  

However, this is standard info that is essential for a lot of design purposes and absolutely _should_ be available to developers in a coherent and searchable form rather than the poxy Mickey-mouse clicker of compatible devices derived from it. 

Compatible devices is laden with valuable info that I cannot obtain elsewhere but, frankly, it was less work to build a parser to make it readable than to click through the page that supplied the data for it. 

This is unfortunately another case of marketing and style overcoming useful.