• State Verified Answer
  • Replies 4 replies
  • Subscribers 18 subscribers
  • Views 245 views
  • Users 0 members are here
Options
Related

isWearable? has :steps?

flocsy🤠
2 months ago

My app is only useful on devices that count steps. I don't see any api or field related to steps that is not available on edge or gpsmap devices. Is there a better way to know from simulator.json or compiler.json whether a device is a wearable or whether it supports step counting other than whether the device name starts with "edge" or "gpsmap"?

  • +1 2 months ago

    Check for has ActivityMonitor as it's not just steps  Also, you wont find SensorHistory on Edge, etc

    You can also just not include non-watches for your target devices, which is the easiest

  • 0 2 months ago in reply to jim_m_58

    That's exactly what I needed. I generate monkey.jungle with a script that uses filters to only have the relevant devices AND it also warns me in case new devices were added (and downloaded in SDK manager) but I forgot to add them to the manifest.

  • 0 2 months ago
    flocsy🤠 said:
     Is there a better way to know from simulator.json or compiler.json whether a device is a wearable or whether it supports step counting other than whether the device name starts with "edge" or "gpsmap"?

    Although you already have the answer you need, note that there are non-wearables whose names don't start with "edge" or "gpsmap": montana7xx, oregon7xx, and rino7xx.

    And not that you need another solution, but here's some other approaches that would also work:

    - check compiler.json for the presence of appTypes.type == "watchFace" (only watches support this app type)

    - check compiler.json for deviceGroup == "Watches/Wearables" (note that deviceGroup corresponds to the 3 device categories in the SDK Manager's devices tab: "Edge", "Outdoor Handhelds", "Watches/Wearables")

  • 0 2 months ago in reply to flocsy🤠

    The safest way is still to only support devices you can support.  On some older devices (and even things the the I2), the available memory could be too small for your app. 

    And there are other variables, like if there's a baro altimeter (the va5 doesn't have one for example) and there are things like floors that aren't available.