Adapting Your Connect IQ App to LTE

The ability for Connect IQ to make REST requests to the cloud has greatly expanded since Connect IQ was introduced. In Connect IQ 1.0, all REST requests had to be done through a tethered connection through Garmin Connect Mobile. Connect IQ 3.0 introduced the audio content provider app type, and with that introduced the ability to download media content over Wi-Fi.

The newest Connect IQ compatible wearable, the vívoactive® 3 Music for Verizon, welcomes LTE into the mix. The LTE connection brings a new level of autonomy to Garmin wearables, as the user can now leave their phone at home and still have access to phone-free safety features, music downloads, and texting .

This autonomy has been extended to Connect IQ as well. The wearable will default to using the phone connection for REST requests when the Bluetooth Smart connection is available but will enable the LTE connection when the user is away from the phone. You can ensure your app is ready for this new level of autonomy with a few additions.

In Connect IQ 1.0 the phoneConnected API could be used to detect if an app could make a REST request using makeWebRequest. In Connect IQ   the new connectionAvailable and connectionInfo APIs were introduced. connectionAvailable is used to see if any connection across any pipe is available, and connectionInfo gives the current status of all communication pipes.

A few things to remember about these calls:

For example, if you wanted to check if your app can make a web request for all devices you can use this function:

[1] Monthly Verizon service plan required.

This function will work regardless if the watch is connected via Bluetooth Smart, Wi-Fi, or LTE.

Adapting your Connect IQ app to LTE requires only a minor amount of work and adds a new level of autonomy. Get the SDK and bring your make your app LTE ready.